Page MenuHomePhabricator

[OPS] udp2log prevents udp2log-mw from starting
Closed, DeclinedPublic


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

Version: unspecified
Severity: normal
See Also:



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:54 AM
bzimport set Reference to bz38995.
bzimport added a subscriber: Unknown Object (MLST).

udp2log now runs on deployment-bastion and seems to start with no issues.

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.

hashar claimed this task.

udp2log is gone, at least from bastion.