Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: [SOLVED] weird error in zimbra

  1. #1
    Join Date
    Oct 2009
    Location
    Malaysia
    Posts
    39
    Rep Power
    6

    Unhappy [SOLVED] weird error in zimbra

    Hi gurus of zimbra,

    Im having a weird error on my zimbra. Previously it was running well, send and receiving emails is almost in real time and fast. But after i have rebooted the server, the zmcontrol status is giving me this error :

    Host mail.nha2u.com.my
    antispam Stopped
    zmmtaconfigctl is not running
    zmamavisdctl is not running
    antivirus Stopped
    zmmtaconfigctl is not running
    zmamavisdctl is not running
    zmclamdctl is not running
    ldap Stopped
    logger Stopped
    logmysql.server is not running
    zmlogswatchctl is not running
    mailbox Stopped
    zmmtaconfigctl is not running
    mysql.server is not running
    tomcat is not running
    mta Stopped
    zmmtaconfigctl is not running
    postfix is not running
    zmsaslauthdctl is not running
    snmp Stopped
    swatch is not running
    spell Stopped
    zmapachectl is not running
    stats Stopped

    and when i do zmcontrol start/stop, this is what i get :

    [zimbra@mail ~]$ zmcontrol start
    no connection to syslog available
    - /dev/log is not a socket at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 41


    Can anyone help me about this please ?

    Thank you.

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by getridoff View Post
    [zimbra@mail ~]$ zmcontrol start
    no connection to syslog available
    - /dev/log is not a socket at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 41


    Can anyone help me about this please ?
    That would appear to be a problem with syslog, have you tried restarting it then restarting Zimbra?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Oct 2009
    Location
    Malaysia
    Posts
    39
    Rep Power
    6

    Unhappy

    Hai Phoenix,

    Thanks for the quick reply! by the way i have restarted the syslog as you guide but it appears to be something weird again. The result as below :

    [root@mail ~]# /etc/init.d/syslog stop ; /etc/init.d/syslog start
    Shutting down kernel logger: [FAILED]
    Shutting down system logger: [FAILED]
    Starting system logger: syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    [FAILED]
    Starting kernel logger: klogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    [FAILED]


    Im totally confused here by this errors. Could you please kindly help me out, as this is the 1st time im encountering this ?

    Thank you.

  4. #4
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Have you done an operating system update recently? You seem to be missing some glibc libraries, what does the output of the following show:

    Code:
    yum provides libc.so.6
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    Join Date
    Oct 2009
    Location
    Malaysia
    Posts
    39
    Rep Power
    6

    Unhappy

    Hi Phoenix,

    Wow that was 'super fast'...ok i have followed your guide and below is the output :

    [root@mail ~]# yum provides libc.so.6
    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
    * addons: centos.maulvi.net
    * base: centos.maulvi.net
    * extras: centos.maulvi.net
    * updates: centos.maulvi.net
    glibc-2.5-42.i686 : The GNU libc libraries.
    Repo : base
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.i386 : The GNU libc libraries.
    Repo : base
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.el5_4.3.i686 : The GNU libc libraries.
    Repo : updates
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.el5_4.3.i386 : The GNU libc libraries.
    Repo : updates
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.el5_4.2.i686 : The GNU libc libraries.
    Repo : updates
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.el5_4.2.i386 : The GNU libc libraries.
    Repo : updates
    Matched from:
    Other : libc.so.6



    glibc-2.5-42.el5_4.3.i686 : The GNU libc libraries.
    Repo : installed
    Matched from:
    Other : Provides-match: libc.so.6


    For your info, i have update the OS with all the packages till last week. This errors only appears yesterday, after a reboot.

  6. #6
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Stop syslog (or kill it) again and run the following command then restart syslog:

    Code:
    syslogd -p /dev/log
    Does that do anything?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    Join Date
    Oct 2009
    Location
    Malaysia
    Posts
    39
    Rep Power
    6

    Default

    Hi Phoenix,

    I have followed your guide and this is what i get :

    [root@mail ~]# /etc/init.d/syslog stop
    Shutting down kernel logger: [FAILED]
    Shutting down system logger: [FAILED]
    [root@mail ~]# syslogd -p /dev/log
    syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

    is there any steps that i missed out ?

    Thank you Phoenix.

  8. #8
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    What does your syslog.conf file contain (are you up-tp CentOS 5.4?), this is the contents of my file:

    Code:
    cat /etc/syslog.conf
    # Log all kernel messages to the console.
    # Logging much else clutters up the screen.
    #kern.*                                                 /dev/console
    
    # Log anything (except mail) of level info or higher.
    # Don't log private authentication messages!
    *.info;mail.none;authpriv.none;cron.none                /var/log/messages
    
    # The authpriv file has restricted access.
    authpriv.*                                              /var/log/secure
    
    # Log all the mail messages in one place.
    mail.*                                                  -/var/log/maillog
    
    
    # Log cron stuff
    cron.*                                                  /var/log/cron
    
    # Everybody gets emergency messages
    *.emerg                                                 *
    
    # Save news errors of level crit and higher in a special file.
    uucp,news.crit                                          /var/log/spooler
    
    # Save boot messages also to boot.log
    local7.*                                                /var/log/boot.log
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  9. #9
    Join Date
    Oct 2009
    Location
    Malaysia
    Posts
    39
    Rep Power
    6

    Default

    Hi Phoenix,

    here is my post :

    [root@mail ~]# cat /etc/syslog.conf
    # Log all kernel messages to the console.
    # Logging much else clutters up the screen.
    #kern.* /dev/console

    # Log anything (except mail) of level info or higher.
    # Don't log private authentication messages!
    *.info;mail.none;news.none;authpriv.none;cron.none /var/log/messages

    # The authpriv file has restricted access.
    authpriv.* /var/log/secure

    # Log all the mail messages in one place.
    mail.* -/var/log/maillog


    # Log cron stuff
    cron.* /var/log/cron

    # Everybody gets emergency messages
    *.emerg *

    # Save news errors of level crit and higher in a special file.
    uucp,news.crit /var/log/spooler

    # Save boot messages also to boot.log
    local7.* /var/log/boot.log

    #
    # INN
    #
    news.=crit /var/log/news/news.crit
    news.=err /var/log/news/news.err
    news.notice /var/log/news/news.notice
    local0.* -/var/log/zimbra.log
    auth.* -/var/log/zimbra.log
    mail.* -/var/log/zimbra.log
    [root@mail ~]#

  10. #10
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Sorry, I gave you the wrong syslog.conf file earlier (it was from a test machine) and it should look like this:

    Code:
    cat /etc/syslog.conf                 
    # Log all kernel messages to the console.             
    # Logging much else clutters up the screen.           
    #kern.*                                                 /dev/console
    
    # Log anything (except mail) of level info or higher.
    # Don't log private authentication messages!         
    *.info;local0.none;local1.none;auth.none;mail.none;authpriv.none;cron.none         /var/log/messages
    
    # The authpriv file has restricted access.
    authpriv.*                                              /var/log/secure
    
    # Log all the mail messages in one place.
    mail.*                                                  -/var/log/maillog
    
    
    # Log cron stuff
    cron.*                                                  /var/log/cron
    
    # Everybody gets emergency messages
    *.emerg                                                 *
    
    # Save news errors of level crit and higher in a special file.
    uucp,news.crit                                          /var/log/spooler
    
    # Save boot messages also to boot.log
    local7.*                                                /var/log/boot.log
    local0.*                -/var/log/zimbra.log
    local1.*                -/var/log/zimbra-stats.log
    auth.*                  -/var/log/zimbra.log
    mail.*                -/var/log/zimbra.log
    Make sure that syslog is not running and kill it if necessary then add the information that's missing from your file and try a restart of syslog. Do you have a backup file of syslog.conf? What does this show:

    Code:
    ls -l /etc/syslog*
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Similar Threads

  1. Replies: 22
    Last Post: 12-02-2007, 05:05 PM
  2. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 09:55 AM
  3. Can't start Zimbra!
    By zibra in forum Administrators
    Replies: 5
    Last Post: 03-22-2007, 12:34 PM
  4. zmtlsctl give LDAP error
    By sourcehound in forum Administrators
    Replies: 5
    Last Post: 03-11-2007, 04:48 PM
  5. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM

Posting Permissions

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