Last modified: 2014-10-29 23:01:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40995, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38995 - [OPS] udp2log prevents udp2log-mw from starting
[OPS] udp2log prevents udp2log-mw from starting
Status: REOPENED
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
: ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-03 08:45 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-10-29 23:01 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2012-08-03 08:45:07 UTC
deployment-dbdump is the main udp2log receiver. The udplog package has a udp2log service listening on port 8420 which prevents the custom udp2log-mw from running.

Whenever the box boot, we have to manually issue:

/etc/init.d/udp2log stop && /etc/init.d/udp2log-mw start
Comment 1 Antoine "hashar" Musso (WMF) 2013-02-14 15:17:06 UTC
ops issue.
Comment 2 Bryan Davis 2014-05-23 17:43:54 UTC
udp2log now runs on deployment-bastion and seems to start with no issues.
Comment 3 Antoine "hashar" Musso (WMF) 2014-05-27 15:03:19 UTC
It happens when the instance boot.  The udp2log service is started up on port 8420.  Then udp2log-mw attempt to start using the same port and bails out because of the port already being listened to.

I / others manually stop udp2log and start udp2log-mw whenever the instance reboot.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links