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
  #1 (permalink)  
Old 12-03-2008, 02:49 AM
Moderator
 
Posts: 1,147
Default /tmp/.swatch_script.nnnn file not closing

Just upgraded to 5.0.11 and have ran into one problem so far. On restarting the services I ran into this issue:
Code:
zimbra@email:~$ zmcontrol status
Host email.pyxislab.com
        antispam                Running
        antivirus               Running
        ldap                    Running
        logger                  Running
        mailbox                 Stopped
                zmmailboxdctl is not running.
        mta                     Running
        snmp                    Running
        spell                   Running
        stats                   Running
zimbra@email:~$ zmcontrol stop
Host email.pyxislab.com
        Stopping stats...Done
        Stopping mta...Done
        Stopping spell...Done
        Stopping snmp...Done
        Stopping archiving...Done
        Stopping antivirus...Done
        Stopping antispam...Done
        Stopping imapproxy...Done
        Stopping mailbox...Done
        Stopping logger...Done
        Stopping ldap...Done
zimbra@email:~$ exit
logout
root@email:~# ps -ef | grep zimbra
zimbra    5274     1  0 02:01 ?        00:00:00 /usr/bin/perl /tmp/.swatch_script.5155
zimbra    5357  5274  0 02:01 ?        00:00:00 /usr/bin/perl /opt/zimbra/libexec/zmlogger
root      9636  4754  0 02:05 pts/0    00:00:00 grep zimbra
Upon killing the perl script running the /tmp/.swatch_script.* the other one dies and Zimbra will then start up fine.

Here is the script that is left running: swatch_script.txt

Anybody have an idea what is going on here? As far as I can tell from the log files there is nothing relevant in them.
Reply With Quote
  #2 (permalink)  
Old 12-03-2008, 03:06 AM
Moderator
 
Posts: 7,928
Default

Check permissions on /var/log/zimbra.log that it is owned by zimbra:zimbra.
__________________
Reply With Quote
  #3 (permalink)  
Old 12-03-2008, 09:09 AM
Moderator
 
Posts: 1,147
Default

Ah thank you very much, I also ran system updates at the same time and it looks like the logger got updated and changed pretty much all the logs to syslog:adm.

Edit: Will test tonight to verify that this fixed it but seems likely that it has.
Reply With Quote
  #4 (permalink)  
Old 12-05-2008, 08:36 AM
Active Member
 
Posts: 28
Default It sounds like this might be your problem

I'm pretty sure this problem is the same one described here ZMLogger Fails to Stop
Reply With Quote
  #5 (permalink)  
Old 12-05-2008, 08:41 AM
Moderator
 
Posts: 1,147
Default

Thanks for the input, haven't yet gotten a chance to test this to see if it was permissions or not. I will try to get on that tonight.
Reply With Quote
  #6 (permalink)  
Old 12-05-2008, 08:55 AM
Moderator
 
Posts: 1,027
Default

Quote:
Originally Posted by jsnapp View Post
I'm pretty sure this problem is the same one described here ZMLogger Fails to Stop
Yup. Same thing
__________________
Cheers,

Dan
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.