I think it probably was running after the first time you invoked it. The message is only informative, meaning that zopectl died unexpectly the last time it was run (without cleaning up after itself). It's not a fatal error or at least hasn't been whenever I've seen it.

On Nov 22, 2005, at 10:57 AM, michael nt milne wrote:

Yes, I noticed that the deamon wasn't running and so re-started it. It started up fine but that was the message I received. Just wondered what happened etc..

On 11/22/05, Chris McDonough <[EMAIL PROTECTED]> wrote: Note that Zope likely started. Did it? Did you try zopectl stop and
zopectl start again?  If so, did it work?

- C

On Nov 22, 2005, at 9:52 AM, michael nt milne wrote:

> Hi
>
> My zopeinstance went down and I was getting an 'upstream server'
> unknown message from apache. On restarting zope from ./zopectl this
> was the message I got.....
>
> unlinking stale socket
> /home/zopeinstance/var/zopectl/sock,sleep/
> No handlers could be found for logger 'root'
>
> Does anyone have any idea on how to prevent this at all, or what
> happened here?
>
> Thanks
>
> Michael
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )



_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to