On Vr, 2011-09-09 at 08:52 -0700, floseries wrote: <snip>
> Well this was strange indeed, because it said that it could not be > started because of a socket error: > > Traceback (most recent call last): > File > "/home/fritz/Plone/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/run.py", > line 56, in ? > run() > File > "/home/fritz/Plone/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/run.py", > line 21, in run > starter.prepare() > File > "/home/fritz/Plone/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/__init__.py", > line 96, in prepare > self.setupServers() > File > "/home/fritz/Plone/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/__init__.py", > line 229, in setupServers > raise ZConfig.ConfigurationError(socket_err > ZConfig.ConfigurationError: There was a problem starting a server of > type "HTTPServer". > This may mean that your user does not have permission to bind to the > port which the server is trying to use or the port may already be in > use by another application. (Address already in use) > Thought that plonectl will stop zope, too. > Plone is running under normal user, not a special user or root. Is > here maybe the problem ? I don't use plonectl, (I guess it comes with the universal installer?), but usually when this error message appears, it means that the Zope/Plone instance is already running somewhere else or in the background. On a Unix system, you can find the process number of the running instance with "ps aux | grep Zope" and then just kill it. Regards JC _______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-setup
