Re: ./postconf: fatal: socket: Protocol not supported
On Tue, 2011-11-15 at 20:41:08 -0500, Wietse Venema wrote: > Sahil Tandon: > > This error was reported to me by a FreeBSD user, but I cannot reproduce > > it on any of my development machines. It occurs during build (sorry for > > line wraps): > > > > rm -f ../../conf/main.cf.default > > cp postconf ../../bin > > (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE"; > > echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX."; > > echo "#"; ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) ' > > >../../conf/main.cf.default > > ./postconf: fatal: socket: Protocol not supported [ .. ] > Postconf opens a socket to determine the mynetworks value (it > determines the local interfaces and their netmasks). > > I have heard about bizarre errors on FreeBSD (jail) systems where the > user-land library was out of sync with kernel-land, resulting in data > structure mis-matches and system calls returning nonsensical results. Thanks for the quick reply. -- Sahil Tandon
Re: ./postconf: fatal: socket: Protocol not supported
Sahil Tandon: > This error was reported to me by a FreeBSD user, but I cannot reproduce > it on any of my development machines. It occurs during build (sorry for > line wraps): > > rm -f ../../conf/main.cf.default > cp postconf ../../bin > (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE"; > echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX."; > echo "#"; ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) ' > >../../conf/main.cf.default > ./postconf: fatal: socket: Protocol not supported > > ... the full log is also available[1]. This is snapshot 20111012. > FWIW, this issue was recently discussed[2] on a FreeBSD mailing list. > There is something particular about the machine (to which I do not have > access) on which the build fails. Has anyone seen similar socket errors > via postconf? My next step is to solicit access to the problematic > machine and troubleshoot further. > > [1] > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.2003071512/postfix-current-2.9.20111012,4.log > [2] http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html Postconf opens a socket to determine the mynetworks value (it determines the local interfaces and their netmasks). I have heard about bizarre errors on FreeBSD (jail) systems where the user-land library was out of sync with kernel-land, resulting in data structure mis-matches and system calls returning nonsensical results. Wietse
./postconf: fatal: socket: Protocol not supported
This error was reported to me by a FreeBSD user, but I cannot reproduce it on any of my development machines. It occurs during build (sorry for line wraps): rm -f ../../conf/main.cf.default cp postconf ../../bin (echo "# DO NOT EDIT THIS FILE. EDIT THE MAIN.CF FILE INSTEAD. THE"; echo "# TEXT HERE JUST SHOWS DEFAULT SETTINGS BUILT INTO POSTFIX."; echo "#"; ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) ' >../../conf/main.cf.default ./postconf: fatal: socket: Protocol not supported ... the full log is also available[1]. This is snapshot 20111012. FWIW, this issue was recently discussed[2] on a FreeBSD mailing list. There is something particular about the machine (to which I do not have access) on which the build fails. Has anyone seen similar socket errors via postconf? My next step is to solicit access to the problematic machine and troubleshoot further. [1] http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.2003071512/postfix-current-2.9.20111012,4.log [2] http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html -- Sahil Tandon
