Date: Thu, 3 Apr 2014 11:01:03 +0300 From: "Sergey V. Dyatko" <sergey.dyatko@gmail.com> To: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: Spamd Message-ID: <20140403110103.0b51d9fc@laptop.minsk.domain> In-Reply-To: <533D1366.7030607@webrz.net> References: <533D1366.7030607@webrz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
В Thu, 03 Apr 2014 09:53:10 +0200 Jos Chrispijn <ports@webrz.net> пишет: > Since my last Spamd port update I get this error when I try to start > spamd: > spamd not running? (check /var/run/spamd/spamd.pid). > Starting spamd. > server socket setup failed, retry 1: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 2: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 3: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 4: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 5: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 6: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 7: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 8: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > server socket setup failed, retry 9: spamd: could not create > IO::Socket::IP socket on [127.0.0.1]:783: Address already in use > spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: > Address already in use > ./sa-spamd: WARNING: failed to start spamd > SpamAssassin version 3.4.0 > running on Perl version 5.16.3 > nmap -v localhost: use `sockstat -l4 -p783` instead. It show you what user-command-pid listen that port > Starting Nmap 6.40 ( [1]http://nmap.org ) at 2014-04-03 09:44 CEST > Initiating SYN Stealth Scan at 09:44 > Scanning localhost (127.0.0.1) [1000 ports] > Discovered open port 25/tcp on 127.0.0.1 > Discovered open port 587/tcp on 127.0.0.1 > Discovered open port 993/tcp on 127.0.0.1 > Discovered open port 995/tcp on 127.0.0.1 > Increasing send delay for 127.0.0.1 from 0 to 5 due to 11 out of 21 > dropped probes since last increase. > Discovered open port 143/tcp on 127.0.0.1 > Discovered open port 3306/tcp on 127.0.0.1 > Discovered open port 110/tcp on 127.0.0.1 > >> Discovered open port 783/tcp on 127.0.0.1 << > Increasing send delay for 127.0.0.1 from 5 to 10 due to 43 out of 142 > dropped probes since last increase. > Increasing send delay for 127.0.0.1 from 10 to 20 due to > max_successful_tryno increase to 4 > --- cut --- > /letc/services file no port 783 reserved: > multiling-http 777/tcp #Multiling HTTP > multiling-http 777/udp #Multiling HTTP > wpgs 780/tcp > wpgs 780/udp > mdbs_daemon 800/tcp > mdbs_daemon 800/udp > Can you tell me if this is a ports issue or how I could solve this? > Thanks! > Jos > > References > > 1. http://nmap.org/ > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- wbr, tiger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140403110103.0b51d9fc>