Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #11 (permalink)  
Old 12-20-2008, 11:46 AM
Junior Member
 
Posts: 5
Default Killing all pending perl processes

Hi everyone,

for me it helped to kill all perl processes after stopping Zimbra. Seems there where a lot of lost processes making trouble.

Maybe this helps others
Reply With Quote
  #12 (permalink)  
Old 04-06-2009, 08:16 PM
Starter Member
 
Posts: 1
Default

Killing the perl processes helped me too. A simple 'zmlogswatchctl restart' didn't work; after going to the server status webpage, the service would die with the OP's error message.

$ ps auxwww|grep [/]zmlogger # list all zmlogger processes
$ ps auxwww|grep [/]zmlogger | awk '{ print $2; }' | xargs kill # kill all zmlogger processes
$ zmlogswatchctl restart # restart zmlogger
$ zmlogswatchctl status # get status
Reply With Quote
  #13 (permalink)  
Old 05-19-2009, 11:07 AM
Zimbra Employee
 
Posts: 515
Default

Several bugs were filed for this problem; it was fixed for 5.0.12 through Bug 33604.

You can work around it by killing the existing zmlogger processes (which are occupying the mysql connections).
__________________
Search the Forums - Bugzilla - Wiki - Downloads
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.