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
420 seconds.
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: From: "Valgosocks"
<osze...@sobainon.co.ua>
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: To:
<sb.gorb...@awo-sonnenstein.de>
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Subject:
=?utf-8?B?ZmFjaG3DpG5uaXNjaGUga29ycmVrdHVyIGRlcyBoYWxsdXggdmFsZ3VzIGFtIGZ1c3M=?=
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body: This is a
multi-part message in MIME format.
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body:
------=_NextPart_000_0006_01D349CD.8A885470
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body: Content-Type:
multipart/alternative;
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body:
boundary="----=_NextPart_000_0007_01D349CD.8A885470"
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body:
------=_NextPart_000_0007_01D349CD.8A885470
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body: Content-Type:
text/plain;
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Body:
charset="windows-1251"
2017-10-22T06:00:01.101Z heimdal newsyslog[25423]: logfile turned over
- and the daemon log part
Oct 21 20:24:54 heimdal spamd[46664]: 60.167.119.193: disconnected after
420 seconds.
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: From: "Valgosocks"
<osze...@sobainon.co.ua>
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: To:
<sb.gorb...@awo-sonnenstein.de>
Oct 21 20:24:56 heimdal spamd[46664]: 217.12.203.2: Subject:
=?utf-8?B?ZmFjaG3DpG5uaXNjaGUga29ycmVrdHVyIGRlcyBoYWxsdXggdmFsZ3VzIGFtIGZ1c3M=?=
Am 22.10.2017 um 12:59 schrieb Markus Rosjat:
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/spamd
but in my opinion this shouldnt cause trouble at all.
If I can produce more verbose output in anyway give me a hint I'll do :)
Regards
Markus
Am 06.10.2017 um 10:49 schrieb rosjat:
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 run but isnt.
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.
here is my spamd setting
spamd_class=daemon
spamd_flags=-v -G10:12:864 -B 50 -c 100 -s 10
spamd_rtable=0
spamd_timeout=30
spamd_user=root
and spamlogd
spamlogd_class=daemon
spamlogd_flags=-l pflog3
spamlogd_rtable=0
spamlogd_timeout=30
spamlogd_user=root
If someone had the same issue and could resolve it Iwould be nice to
here. In the end I can always make a cron job that checks if spamd is
running and if not just restart it but this isnt really a solution ...
regards
--
Markus Rosjat fon: +49 351 8107223 mail: ros...@ghweb.de
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before
you print it, think about your responsibility and commitment to the
ENVIRONMENT
