Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Motherboard burned

  1. #11
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    1) You need to see why zmconfigd won't start
    2) Then you can see why other things won't start

    Start with /opt/zimbra/log/zmconfigd.log
    zmconfigd is the process that re-writes the configuration files for the various services, so if it can't start, the startup files will not be adjusted (if necessary) for any data changes.

    You can also look at /opt/zimbra/log/mailbox.log for why the mailbox server won't start, but it is probably related to zmconfigd not running.

    --Quanah
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  2. #12
    francisco.costa is offline Trained Alumni
    Join Date
    Jun 2011
    Posts
    12
    Rep Power
    4

    Default

    I can send logs zmconfigd and mailbox for you to take a look? Maybe so I save time in troubleshooting. I'm under a lot of pressure to get the server running again. My job is at risk. Thank you.
    Attached Files Attached Files

  3. #13
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    I see the problem.

    As zimbra:
    zmcontrol stop

    As root:
    cd /opt/zimbra/zimbramon/pylibs
    rm -f *.class

    As zimbra:
    zmcontrol start

    That will at least get zmconfigd up and running

    --Quanah
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  4. #14
    francisco.costa is offline Trained Alumni
    Join Date
    Jun 2011
    Posts
    12
    Rep Power
    4

    Default

    Thanks for the reply. Worked with configd.log. The problem this time is with zmmailboxctl not starting. Follows the log.

    Sorry problems. But really need help from experts.

    zimbra@zimbra:/root$ zmcontrol status
    Host zimbra.rra2.local
    convertd Running
    ldap Running
    logger Running
    mailbox Stopped
    zmmailboxdctl is not running.
    mta Running
    snmp Running
    spell Running
    stats Running
    zmconfigd Running
    zimbra@zimbra:/root$

    zimbra@zimbra:/root$ zmcontrol status
    Host zimbra.rra2.local
    convertd Running
    ldap Running
    logger Running
    mailbox Stopped
    zmmailboxdctl is not running.
    mta Running
    snmp Running
    spell Running
    stats Running
    zmconfigd Running
    zimbra@zimbra:/root$

    root@zimbra:~# tail -f /var/log/mail.log
    Jun 13 10:20:05 zimbra zmmailboxdmgr[4310]: assuming no other instance is running
    Jun 13 10:20:05 zimbra zmmailboxdmgr[4310]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:20:05 zimbra zmmailboxdmgr[4310]: assuming no other instance is running
    Jun 13 10:20:05 zimbra zmmailboxdmgr[4310]: no manager process is running
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: status requested
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: stale pid 3116 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: assuming no other instance is running
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: assuming no other instance is running
    Jun 13 10:22:04 zimbra zmmailboxdmgr[4725]: no manager process is running
    Jun 13 10:22:50 zimbra postfix/postfix-script[4996]: stopping the Postfix mail system
    Jun 13 10:22:50 zimbra postfix/master[1652]: terminating on signal 15
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: status requested
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: stale pid 3116 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: assuming no other instance is running
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: assuming no other instance is running
    Jun 13 10:22:53 zimbra zmmailboxdmgr[5159]: no manager process is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: status requested
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: stale pid 3116 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: assuming no other instance is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: assuming no other instance is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5978]: no manager process is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: start requested
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: checking if another instance of manager is already running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: stale pid 3116 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: assuming no other instance is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5988]: assuming no other instance is running
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5989]: wrote manager pid 5989 to /opt/zimbra/log/zmmailboxd_manager.pid
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5989]: manager started mailboxd/JVM with pid 5990
    Jun 13 10:23:59 zimbra zmmailboxdmgr[5990]: wrote java pid 5990 to /opt/zimbra/log/zmmailboxd_java.pid
    Jun 13 10:24:00 zimbra zmmailboxdmgr[5989]: manager woke up from wait on mailboxd/JVM with pid 5990
    Jun 13 10:24:00 zimbra zmmailboxdmgr[5989]: manager started mailboxd/JVM with pid 6108
    Jun 13 10:24:00 zimbra zmmailboxdmgr[6108]: wrote java pid 6108 to /opt/zimbra/log/zmmailboxd_java.pid
    Jun 13 10:24:01 zimbra zmmailboxdmgr[5989]: manager woke up from wait on mailboxd/JVM with pid 6108
    Jun 13 10:24:01 zimbra zmmailboxdmgr[5989]: mailboxd/JVM exited twice in 1 seconds (tolerance=60)
    Jun 13 10:24:01 zimbra postfix/postfix-script[6183]: warning: not owned by root: /opt/zimbra/postfix-2.7.8.3z/conf/main.cf
    Jun 13 10:24:01 zimbra postfix/postfix-script[6187]: warning: not owned by root: /opt/zimbra/postfix-2.7.8.3z/conf/master.cf
    Jun 13 10:24:01 zimbra postfix/postfix-script[6190]: warning: not owned by root: /opt/zimbra/postfix-2.7.8.3z/conf/master.cf.in
    Jun 13 10:24:01 zimbra postfix/postfix-script[6207]: starting the Postfix mail system
    Jun 13 10:24:01 zimbra postfix/master[6208]: daemon started -- version 2.7.8, configuration /opt/zimbra/postfix-2.7.8.3z/conf
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: status requested
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: stale pid 5989 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: assuming no other instance is running
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: assuming no other instance is running
    Jun 13 10:24:07 zimbra zmmailboxdmgr[6981]: no manager process is running

    mailbox.log

  5. #15
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    Mailboxd cannot talk to mysql:

    2013-06-10 09:53:57,316 WARN [main] [] misc - Could not establish a connection to the database. Retrying in 5 seconds.
    com.zimbra.common.service.ServiceException: system failure: getting database connection
    ExceptionId:main:1370868837316:90c174a3dde6f311
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 313)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 277)
    at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.jav a:199)
    at com.zimbra.cs.db.DbPool.startup(DbPool.java:190)
    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:157)
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  6. #16
    francisco.costa is offline Trained Alumni
    Join Date
    Jun 2011
    Posts
    12
    Rep Power
    4

    Default

    Thank you. I'll check the wiki to try to solve.

  7. #17
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    Usually, zimbra is configured to talk to mysql over "localhost" or "127.0.0.1" or "::1" depending on the system. It is possible that one of those is not configured correctly in /etc/hosts on the server. Check your localconfig values for the mysql host/port settings, and then see if you can telnet to the defined host & port.
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  8. #18
    cyber7 is offline Special Member
    Join Date
    May 2010
    Location
    Cape Town; South Africa
    Posts
    102
    Rep Power
    5

    Default

    I wrote a full article on migration here:
    Migrating Zimbra 7 from CentOS 5 to Zimbra 8 on CentOS 6 – The definitive guide. | cyber7
    This is basically the same as a disaster recovery. (I know it is a lot to read...)

    BUT: One thing that I have to mention is that what fixed ALL my errors when doing the last migration/recovery (You know, mail servers keep growing!) was, once I finished recovering everything, I ran the installation again and chose "UPGRADE".

    It sounds silly, but it worked for me, every-time...

    So, run your installation again once completed.

    Just my 10c...
    Code:
    Never trust a fart...
    Release 8.0.0_GA_5434.RHEL6_64_20120907144743 CentOS6_64 NETWORK edition.

  9. #19
    francisco.costa is offline Trained Alumni
    Join Date
    Jun 2011
    Posts
    12
    Rep Power
    4

    Default

    Thanks for the reply. Last night I began the process of importing the messages that were in the store folder to a new server that I made. Just get well. No other attempt was successful. My backups were already being made ​​with the corrupted database. Why not recover at all. The process is time consuming but it is working.

    Quote Originally Posted by cyber7 View Post
    I wrote a full article on migration here:
    Migrating Zimbra 7 from CentOS 5 to Zimbra 8 on CentOS 6 – The definitive guide. | cyber7
    This is basically the same as a disaster recovery. (I know it is a lot to read...)

    BUT: One thing that I have to mention is that what fixed ALL my errors when doing the last migration/recovery (You know, mail servers keep growing!) was, once I finished recovering everything, I ran the installation again and chose "UPGRADE".

    It sounds silly, but it worked for me, every-time...

    So, run your installation again once completed.

    Just my 10c...

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Server Burned
    By babyporch in forum Administrators
    Replies: 0
    Last Post: 05-04-2011, 10:25 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
  •