graylog snap not listening on any port

Bug #1800208 reported by james beedy on 2018-10-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MongoDB Charm
Undecided
Drew Freiberger
graylog-snap
Undecided
Unassigned

Bug Description

Pretty sure the graylog charm/snap are borked to some degree

Deploy this bundle here to replicate [0]

Tested in a myriad environments, series, channels, can't seem to get the graylog snap to listen on any port, see [1]

[0] https://paste.ubuntu.com/p/Gyn4W85VcT/
[1] https://paste.ubuntu.com/p/g2YHMwVDQX/

Drew Freiberger (afreiberger) wrote :

We were able to replicate this issue. Mongodb charm has a bug that fails to configure the listening IP when bind_ip is set to the standard "all".

Workaround is to 'juju config mongodb bind_ip=0.0.0.0'.

Drew Freiberger (afreiberger) wrote :

as further explanation, the graylog logs in /var/snap/graylog/common/logs show mongodb connectivity failures which causes it to not open listener ports.

Changed in graylog-snap:
status: New → Invalid
Drew Freiberger (afreiberger) wrote :

If mongodb charm has both replicaset_master = auto and bind_ip = all, the fix for lp#1748214 does not get invoked.

I've submitted a fix for review at:
https://code.launchpad.net/~afreiberger/mongodb-charm/+git/mongodb-charm/+merge/358133

Changed in mongodb-charm:
status: New → Fix Committed
assignee: nobody → Drew Freiberger (afreiberger)
Xav Paice (xavpaice) on 2018-10-31
Changed in mongodb-charm:
status: Fix Committed → Fix Released
james beedy (jamesbeedy) on 2018-11-14
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers