Hi again,
I looked further and notice not the syslogd was the cause but somehow
spamd died while talking to a server. Could something in the body screw
up spamd?
here are my logs on that:
- the spamd log file part
Oct 21 20:24:54 heimdal spamd[46664]: 60.167.119.193: disconnected after
42
Hi there,
spamd just died silently again tonight. whats the best way to approach
the debugging of this kind of behaviour. As I looked at my logs it seems
that Syslogd causes this because so here is my syslog.conf entry:
!!spamd
daemon.err;daemon.warn;daemon.info;daemon.debug /var/log/
Op Fri, 06 Oct 2017 10:49:39 +0200 schreef rosjat :
[...]
Is there some way to get a more verbose autput when the process is
daemonized? the -v switch only seems to aplay to the foreground mode.
Depends on your syslog.conf; I have:
!!spamd
daemon.err;daemon.warn;daemon.info;daemon.debug
Hi there,
it seems spamd daemon is siliently and randomly dying on a OpenBSd 6.1
machine. The logs show nothingĀ that would give some hint and If my
script for bgp-spamd wouldn tell me it cant connect to spamd I would
even notice it till the next daily job that tells me that spamlogd
should
4 matches
Mail list logo