Troubleshooting Zeo Server Buildout

Wiki Tools

Login to see more wiki tools

Print Article

Created on: Apr 08, 2009

Revision: 1 (public)
Rev Published: Aug 31, 2009

Articles at this level:

• Silva Buildout
• Deploy Silva Instance using Buildout
• Adding Products to Buildout
• Troubleshooting Zeo Server Buildout *
• Temporary Buildout Modifications
• Update Zope Nodes after buildout / deployment
• How to build Silva on Mac OSX

New & Updated (3)

• Office Migration May 22, 2012
• Who works on web content? May 18, 2012
• Academics Migration Process May 14, 2012

Error starting zeoserver

When starting the zeoserver, ( > bin/zeoserver start ) you get the following error message:

• daemon manager not running

This error usually point to a port conflict.  Run netstat -nl to determine what is using the port that has been designated for the zeoserver.
You will need a unique zeo-address in the in the config file and a unique http-address in the base config

This error may also be caused by trying to start a zeoserver when one is already running on the designated port.  running netstat -nl will show if that is the case.  If that is the case, simple start an instance of the server in the foreground to verify that it will start (bin/instance fg).  The zope server should start up.