Re: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

2014-11-26 Thread Thomas Schulz
Thanks, that explains how we get to 'Address already in use'. This opens up a couple of questions: - creating a socket listening on '::' apparently does work (it is tested in the BEGIN phase, and reported by 'have PF_INET6'), but creating a socket listening on '::1' (i.e. a loopback

Re: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

2014-11-24 Thread Mark Martinec
Tom Schulz wrote: Here is my debug output. It looks like the socket is created for 127.0.0.1 and then an attempt is also made for ::1. That fails as expected. But in my case that failure causes a retry that includes retrying for 127.0.0.1. This now fails because the port has already been created

Re: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

2014-11-21 Thread Thomas Schulz
Tom Schulz wrote: I am not sure if this is a bug or a usage problem. I have been running spamd on Solaris 10 and Perl v5.8.9 for years, starting it with the command: spamd -d -c -m 18 --min-spare=1 --max-spare=4 --syslog-socket=inet I upgraded Perl to v5.20.1 and installed the current

could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

2014-11-20 Thread Thomas Schulz
: Address already in use spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use And spamd does not start. If I add '-4' to the above command then I get only the error: setlogsock(): type='tcp': TCP service unavailable at /opt/local/lib/perl5/site_perl/5.20.1/Mail

Re: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

2014-11-20 Thread Mark Martinec
Tom Schulz wrote: I am not sure if this is a bug or a usage problem. I have been running spamd on Solaris 10 and Perl v5.8.9 for years, starting it with the command: spamd -d -c -m 18 --min-spare=1 --max-spare=4 --syslog-socket=inet I upgraded Perl to v5.20.1 and installed the current