[Sshguard-users] Spurious sshguard shutdowns at boot time with "sshguard[#]: Got exit signal" logged

[Richard J. <rjt...@sa...>]

On OpenBSD 5.6, I'm seeing sshguard 1.5.0 stopping nearly immediately upon
start at boot time.  Typical log entries:

Feb 15 16:17:46 host sshguard[765]: Started successfully [(a,p,s)=(40, 420, 1200)], now ready to scan.
Feb 15 16:17:47 host sshguard[765]: Got exit signal, flushing blocked addresses and exiting...

And sshguard is indeed no longer running.  A later manual start of sshguard
succeeds.

This matches with reported 2012 FreeBSD experience:
https://forums.freebsd.org/threads/at-boot-rc-script-runs-but-service-immediately-exits.29623/

However, in my case, even putting in a 60 second delay on the start of
sshguard is not enough for sshguard to remain running on the system I'm
using for testing.  The start is delayed, but then sshguard quits 1-2
seconds later with the 'Go exit signal' message showing in the log.

I do not know at present whether there's actually an exit signal
sent/received, or whether that message is triggered by something else.

Is this known and fixed yet in the dev repository, or has the cause not yet
been run down?


Richard

-------
/etc/rc.d/sshguard:
-------
#!/bin/sh
#
# $OpenBSD: sshguard.rc,v 1.1 2011/03/07 17:44:16 rpointel Exp $

daemon="/usr/local/sbin/sshguard"
daemon_flags="-l /var/log/authlog"

. /etc/rc.d/rc.subr

rc_bg=YES
rc_reload=NO

rc_cmd $1
-------