Package: mon Version: 1.2.0-9 Severity: normal Apr 18 13:10:22 myserver systemd[1]: Stopped LSB: monitor hosts/services/whatever and alert about problems. Apr 18 13:10:22 myserver systemd[1]: Starting LSB: monitor hosts/services/whatever and alert about problems... Apr 18 13:10:22 myserver mon[2800]: fatal, could not bind TCP server port 2583: Address already in use Apr 18 13:10:22 myserver mon[2787]: Starting mon daemon : mon failed! Apr 18 13:10:22 myserver systemd[1]: mon.service: Control process exited, code=exited status=1
When running "/etc/init.d/mon restart" I often get the above result, it seems that the restart happens too quickly for the kernel to release the port. Would a delay in the restart operation be the appropriate solution for this? -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mon depends on: ii adduser 3.113+nmu3 ii libc6 2.19-18+deb8u4 ii libtime-period-perl 1.20-8 ii mon-client 1.2.0-2 Versions of packages mon recommends: pn fping <none> pn libauthen-pam-perl <none> pn libcrypt-ssleay-perl <none> pn libfilesys-diskspace-perl <none> pn libnet-dns-perl <none> pn libnet-ldap-perl <none> pn libnet-telnet-perl <none> pn libsnmp-perl <none> pn libstatistics-descriptive-perl <none> pn libtime-parsedate-perl <none> ii perl-modules [libnet-perl] 5.20.2-3+deb8u4 Versions of packages mon suggests: ii mon-contrib 1.0+dfsg-3 -- no debconf information
