Date: Thu, 03 Apr 2014 15:49:47 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-ports@freebsd.org Subject: Re: Spamd Message-ID: <533D750B.2030209@infracaninophile.co.uk> In-Reply-To: <533D5AA9.4000904@webrz.net> References: <533D1366.7030607@webrz.net> <20140403110103.0b51d9fc@laptop.minsk.domain> <533D5AA9.4000904@webrz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --M86p5E39vVJ6ACHoEloiBIirmXiVuldhH Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 04/03/14 13:57, Jos Chrispijn wrote: > Sergey V. Dyatko: >> use `sockstat -l4 -p783` instead. It show you what user-command-pid >> listen that port >=20 > I killed process 1402 and started Spamd. That did the trick, thanks! >=20 > I am very curious: >=20 > a. why Perl occupied that port. > Tried to retrieve this information from logfiles in /var/log but no > success. May that be an inward traffic issue on port 783 that triggered= > Perl and kept it occupied for Spamd? >=20 > b. Is it unsafe or possible to let spamd use another port if 783 is > occupied. May that be a security risk? Assuming 'spamd' here is part of spamassassin then it is a daemon written in perl, and the command name will show up as perl in sockstat listings. In my experience, it is quite common for this daemon to end up running under a different PID than the one recorded under /var/run -- so the system initialization scripts 'sa-spamd' think it isn't running, and then you get the fight over access to port 783 the OP saw. Killing the processes using port 783 and restarting spamd should work. The situation is complicated by the /other/ spamd -- which is an OpenBSD thing which works via pf to implement greylisting, teergrube and various other anti-spam things. Meaning the SpamAssassin 'sa-spamd' startup script can't simply kill anything called spamd. Cheers, Matthew --M86p5E39vVJ6ACHoEloiBIirmXiVuldhH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJTPXUTXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnaaQP+waCrYDspK2vLCqrW3gT9yio nW0E73XFqCfb8eF2mLPlHvUHVuBw1yDetmIYYr2jVTXdj4fxkqwFO81LoG2sCxqC RtlfzmWD7IVof0Io75Qlr1hTT5JEMp/WW33wIP55YU2qYuGx0OvCqvYxBFW6ijva bzRsxvgBMrAu2rCYky4p/Ayt3p5qwpd6BOVZlKAPSL7dSDli2RDQ9Qfq6uqhbOau Uorn0mNU1+GOlaq22dH10Kp0h9yFzqa6px0RsYMWkPs/z58l+hCVRXPHb+M5O2Uw GVsjsEDCgJwRTn9TfLismHqtUEqUKqMtKFBPULAM+b41ZRkLEh+5uarfn3DxNnb5 i9LeXjITwYgeMu2rX5UEFZHlKR8PtD0Fvukk7d4ayiJNSmPcLXloVzFXERszs0L6 uL3lTJzznFiMAbjfe9o9fXqGhQcr/b/Ct+1rro6bHDdh5rAkrWykTZYATvlKwoFu st6Xa+wRE1YSsTbdqzP0Wjexy6A1mimZhBa/szFIX4taGFHe6ax39fl0jVIYU+SH 95Gg9NtRqgbowF0huOllXuxRPpYR5b3REjjsHPco/VcHbmAD41ZTZ6N1KE26w+YO tsEu6PtArhlfcyg0n6Pc6CBfRt2hzqJ5pQ+a03ivSu52bzXH1ioNAhRkqqizMJyW R4gooVUVk1LeWb+xHmkC =k2rf -----END PGP SIGNATURE----- --M86p5E39vVJ6ACHoEloiBIirmXiVuldhH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?533D750B.2030209>