2008/6/11 Martijn Pieters <[EMAIL PROTECTED]>:
> On Wed, Jun 11, 2008 at 3:28 PM, Peter Bengtsson <[EMAIL PROTECTED]> wrote:
>> This happens from time to time and I've never really understood how it
>> ends up like this.
>> There's no zopeinstance/var/zopectlsock socket which means that
>> zopectl
On Wed, Jun 11, 2008 at 4:34 PM, Martijn Pieters <[EMAIL PROTECTED]> wrote:
> If this in a buildout, then you you ran bin/buildout which nuked your
> parts/instance directory with the socket. This is a bug in
> zope2instance where it sets the CLIENT_HOME to parts/instance instead
> of a part-specif
On Wed, Jun 11, 2008 at 3:28 PM, Peter Bengtsson <[EMAIL PROTECTED]> wrote:
> This happens from time to time and I've never really understood how it
> ends up like this.
> There's no zopeinstance/var/zopectlsock socket which means that
> zopectl stop|restart|start just spits out "daemon manager not
This happens from time to time and I've never really understood how it
ends up like this.
There's no zopeinstance/var/zopectlsock socket which means that
zopectl stop|restart|start just spits out "daemon manager not running"
When in fact, Zope is running. It's there when you run `netstat -nptl`
and
