A little more data. I ran strace on the startup script. The failure seems to arise from trying to open a socket connection to /dev/log. See below. I verified that /dev/log is world writable. And lsof and netstat report that syslogd has the socket open. [pid 22357] close(3) = 0 [pid 22357] socket(PF_UNIX, SOCK_STREAM, 0) = 3 [pid 22357] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 [pid 22357] connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 10) = -1 EPROTOTYPE (Protocol wrong type for socket) [pid 22357] send(5, "<9>z2[22357]: Startup exception "..., 81, 0) = 81 [pid 22357] close(3) = 0 Dave --- Dave Still <davestill@yahoo.com> wrote:

Hello, I just obtained the latest Python & Zope RPMs and installed them on two different linux boxes. Both installations are exhibiting the same exact startup problem, even though they the Linux versions are very different.

Running '/etc/rc.d/init.d/zope start' results in the following syslog output:

Sep 19 12:01:07 wwwin-irv-tmp zope: zserver.sh startup succeeded Sep 19 12:01:10 wwwin-irv-tmp z2[21050]: Startup exception : error: (91, 'Protocol wrong type for socket')

Status check:

# /etc/rc.d/init.d/zope status zwatchdog dead but pid file exists zserver is stopped

The RPM packages I used are:

python2-devel-2.1.1-3 python2-2.1.1-3 Zope-2.4.1-1 Zope-zserver-2.4.1-1

Does anyone have any idea what's wrong? There are a couple of folks posting the newsgroup with this very same issue.

Dave

__________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information

http://dailynews.yahoo.com/fc/US/Emergency_Information/

__________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/