Results 1 to 10 of 10

Thread: Unexpected message in the log after zimbra restarting

  1. #1
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Cool Unexpected message in the log after zimbra restarting

    Hello,

    I ran this script:
    Code:
    #!/bin/bash
    
    # General settings
    sudo -u zimbra /opt/zimbra/bin/zmcontrol -v
    sudo mkdir -p /opt/backup/tmp
    sudo rm -rf /opt/backup/tmp/zimbra
    
    # Stopping zimbra services
    sudo -u zimbra /opt/zimbra/bin/zmcontrol stop
    sleep 20
    
    # Getting zimbra processes
    sudo ps aux | grep zimbra
    
    # Killing zimbra procecees
    sudo kill -9 $(ps -u zimbra -o "pid=")
    
    # Gold syncing to backup folder
    sudo rsync -avr /opt/zimbra/ /opt/backup/tmp/zimbra
    
    # Compressing backup for space reduction
    sudo tar -zcvf $local_backup_dir/01/$backup_full_file_name -C /opt/backup/tmp zimbra
    
    # Zimbra services starting
    sudo -u zimbra /opt/zimbra/bin/zmcontrol start
    sleep 20
    
    # Zimbra services status
    sudo -u zimbra /opt/zimbra/bin/zmcontrol status
    This is the status for zmcontrol status
    Code:
    Host mail.domain.com
    	antispam                Running
    	antivirus               Running
    	ldap                    Running
    	logger                  Stopped
    		zmlogswatchctl is not running
    	mailbox                 Running
    	mta                     Running
    	snmp                    Stopped
    		zmswatch is not running.
    	spell                   Running
    	stats                   Running
    and this is the services status from the log when the script was done

    Code:
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: antispam: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: antivirus: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: ldap: Running 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: logger: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: mailbox: Running 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: mta: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: snmp: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: spell: Stopped 
    Jan 25 18:12:05 mail zimbramon[11706]: 11706:info: 2009-01-25 18:12:01, STATUS: mail.domain.com: stats: Stopped
    Any help please?

    Cheers,
    Last edited by snake_eyes; 01-25-2009 at 09:02 AM.

  2. #2
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Default

    Hello,

    Any help gentleman about this matter, I'm tired with this error

    Cheers,

  3. #3
    Join Date
    Sep 2008
    Location
    Russia Federation, Novosibirsk
    Posts
    32
    Rep Power
    7

    Default

    Please attach messages from

    /opt/zimbra/log/mysql_error.log
    /opt/zimbra/log/mailbox.log
    /opt/zimbra/log/logger_mysql_error.log

  4. #4
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Default

    Kindly check the log files of each one as per your request:

    This is the exact time of backup script 18:00

    /opt/zimbra/log/mysql_error.log
    Code:
    090126 18:02:29 [Note] /opt/zimbra/mysql/libexec/mysqld: Normal shutdown
    
    090126 18:02:29  InnoDB: Starting shutdown...
    090126 18:02:31  InnoDB: Shutdown completed; log sequence number 0 82535611
    090126 18:02:31 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete
    
    090126 18:02:31  mysqld ended
    
    090126 18:13:04  mysqld started
    090126 18:13:05  InnoDB: Started; log sequence number 0 82535611
    090126 18:13:05 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
    Version: '5.0.51a-log'  socket: '/opt/zimbra/db/mysql.sock'  port: 7306  Source distribution
    /opt/zimbra/log/mailbox.log
    When I try to open it, it gives that couldn't specify the characters encoding, couldn't open it

    /opt/zimbra/log/logger_mysql_error.log
    Code:
    090126 18:02:33 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Normal shutdown
    
    090126 18:02:35  InnoDB: Starting shutdown...
    090126 18:02:36  InnoDB: Shutdown completed; log sequence number 0 43655
    090126 18:02:36 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: Shutdown complete
    
    STOPPING server from pid file /opt/zimbra/logger/db/mysql.pid
    090126 18:02:36  mysqld ended
    090126 18:02:36  mysqld ended
    
    
    Starting mysqld daemon with databases from /opt/zimbra/logger/db/data
    090126 18:13:03  mysqld started
    090126 18:13:04  InnoDB: Started; log sequence number 0 43655
    090126 18:13:04 [Note] /opt/zimbra/logger/mysql/libexec/mysqld: ready for connections.

  5. #5
    Join Date
    Sep 2008
    Location
    Russia Federation, Novosibirsk
    Posts
    32
    Rep Power
    7

    Default

    Logger - Zimbra ::Wiki
    It is recommended to checkout this link first. May be it could help to solve your problem.

  6. #6
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Default

    I've searched the whole forums, found solutions, tried them... but, nothing seems to work
    could you please check my script carefully, is there something wrong with it? specially the Zimbra shutting down and starting.

    Cheers,

  7. #7
    Join Date
    Sep 2008
    Location
    Russia Federation, Novosibirsk
    Posts
    32
    Rep Power
    7

    Default

    It seems that some kind of pid files problems exists.

    sudo kill -9 $(ps -u zimbra -o "pid=")

    Make sure that after this command there are no processes and pid files associated with killed services remain in the system. Especially mysql pid.

  8. #8
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Default

    Great,

    1. What's you suggestion with this command, Is there another way to kill the left over processes?

    2. What about this:
    Code:
    PROX=(`ps -u zimbra | awk '{print $1}' | grep -v PID`)
    if [ "$PROX" ]
    then
     ps -u zimbra | awk '{print $1}' | grep -v PID | xargs kill -s 15
    else
     echo "Nothing to kill"
    fi
    Waiting your feedback, and thanks in advance...

    Cheers,

  9. #9
    Join Date
    Sep 2008
    Location
    Russia Federation, Novosibirsk
    Posts
    32
    Rep Power
    7

    Default

    Second piece of code looks more complicated It should work perfectly.
    Second phase is to kill remaining pid files if any other. Are there any pid files in /opt/zimbra/ after executing this code?
    Some kind of
    find /opt/zimbra -name *.pid

    We have similar problems with logger and it were assiciated with pid files problems
    With best regards,

  10. #10
    Join Date
    Nov 2008
    Posts
    237
    Rep Power
    6

    Default

    Actually I don't recognize, while the script is working the cron.

    Look I ran this command from my script above:
    Code:
    sudo ps aux | grep zimbra
    it show me more than 6 PID

    and this also from my script above:
    Code:
    sudo kill -9 $(ps -u zimbra -o "pid=")
    It gives noting, that means no PID remaining, all were killed

    Unlike when it executed from the cron

    Cheers,

Similar Threads

  1. Upgrade to ZCS 5.10
    By blozancic in forum Installation
    Replies: 0
    Last Post: 10-21-2008, 08:03 AM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. Replies: 12
    Last Post: 02-25-2008, 06:28 PM
  4. Major Issue - 5.0RC2 NE to 5.0GA NE failed
    By DougWare in forum Installation
    Replies: 7
    Last Post: 01-06-2008, 08:56 PM
  5. Replies: 22
    Last Post: 12-02-2007, 04:05 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •