We have a standard build procedure that produces an RPM for AOLserver
3.4.2, which we're using in production. This RPM were built on a Redhat
Advanced Server 2.1 server (32-bit). When we take the 32-bit RPM and
install it on a 64-bit Redhat Enterprise Linux 4 server, it works
perfectly.
But if we rebuild the RPM in 64-bit mode on the RHEL4 server, the build is
successful, but then the web servers produce the following messages at
runtime:
[20/Jun/2005:15:50:34][25835.-1782325504][-main-] Fatal: binder: sendmsg()
failed: 'Invalid argument'
The web servers actually continue running despite this message, but they
do *not* bind to their standard ports--e.g., there's nothing listening on
ports 80 or 443.
Any ideas what's going on here? I can see the code in question in
nsd/binder.c, but it's not clear to me why it would fail on a 64-bit
system.
Generally speaking, is AOLserver 3.4.2 64-bit clean? Is anyone
successfully running it on a 64-bit system?
- John
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
