Results 1 to 8 of 8

Thread: "Some services are not running" message after migrating to new server

  1. #1
    Join Date
    Jun 2012
    Posts
    5
    Rep Power
    3

    Question "Some services are not running" message after migrating to new server

    Hi everybody. My Zimbra version is Zimbra 8.0.2_GA_5569 (build 20121210115059).

    I'm using Zimbra since a few months and I really love it.

    I just relocated installation to a new server using rsync to a centos6.3 server, keeping same hostname and ip.

    After setting permissions, all services start and the system can receive and send emails.

    If I enter zmcontrol status it shows all services as running but in the zimbra administration console I have the "Some services are not running" message.

    I think it's related to .ssh directory (maybe zimbra can't login with ssh).
    I disabled selinux and enabled notty login with visudo.

    I have rsyslog installed because syslog is deprecated in centos.

    Any suggestions?

    Are there any checks I can do to ensure the server migration went really alright?

    Thank you very much for your support.

    edit:
    The stats in Admin Panel are OLD. They don't update like files can't be read. zimbra.log gets entries.

    UPDATE: I found empty dir /var/spool/cron/ - maybe I need to recreate zimbra cron tab but I don't know how.
    Last edited by kaioh; 02-11-2013 at 03:05 PM. Reason: additional infos

  2. #2
    Join Date
    Jun 2012
    Posts
    5
    Rep Power
    3

    Default

    I restored crontab from a backup from old server and now admin console shows all services running.

  3. #3
    Join Date
    Jun 2012
    Posts
    5
    Rep Power
    3

    Default

    OK I was wrong, after some minutes it turned back again to "Some services not running".
    Also reinstalled zimbra and resynced but none changed

  4. #4
    Join Date
    Nov 2011
    Posts
    2
    Rep Power
    4

    Default

    I had the same problem,

    I found it was due to the absence of zimbra crontab who launch an regulary interval the process /opt/zimbra/libexec/zmstatuslog responsible of the server status reporting in the administration console.

    My installation is Zimbra 8.0.3 on Ubuntu 12.04 LTS 64 bits

    I don't know why this crontab was not created during the installation, but here is what I do to correct it :

    1. give access to zimbra user to the /opt/zimbra/zimbramon/crontabs folder :

    sudo chown -R zimbra:zimbra /opt/zimbra/zimbramon/crontabs
    2. log as zimbra user

    sudo su - zimbra
    3. Concatenate all files in this folder

    cat crontab >> crontab.zimbra
    cat crontab.ldap >> crontab.zimbra
    cat crontab.logger >> crontab.zimbra
    cat crontab.mta >> crontab.zimbra
    cat crontab.store >> crontab.zimbra
    4. create the zimbra crontab

    crontab crontab.zimbra
    Once it's done the command crontab -l will give somethink like that :

    # ZIMBRASTART -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZIMBRAEND
    #
    # Log pruning
    #
    30 2 * * * find /opt/zimbra/log/ -type f -name \*.log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
    35 2 * * * find /opt/zimbra/log/ -type f -name \*.out.???????????? -mtime +8 -exec rm {} \; > /dev/null 2>&1
    #
    # compress logs manually to avoid application pauses when
    # handled through the log4j thread
    #
    50 2 * * * /opt/zimbra/libexec/zmcompresslogs > /dev/null 2>&1
    #
    # tmp dir cleaning
    #
    40 2 * * * /opt/zimbra/libexec/zmcleantmp
    #
    # Status logging
    #
    */2 * * * * /opt/zimbra/libexec/zmstatuslog > /dev/null 2>&1
    #*/10 * * * * /opt/zimbra/libexec/zmdisklog > /dev/null 2>&1
    #
    # SSL Certificate Expiration Checks
    #
    0 0 1 * * /opt/zimbra/libexec/zmcheckexpiredcerts -days 30 -email
    #
    # Backups
    #
    # BACKUP BEGIN
    # BACKUP END
    #
    # crontab.ldap
    #
    #
    #
    # crontab.logger
    #
    # process logs
    #
    00,10,20,30,40,50 * * * * /opt/zimbra/libexec/zmlogprocess > /tmp/logprocess.out 2>&1
    #
    # Graph generation
    #
    #10 * * * * /opt/zimbra/libexec/zmgengraphs >> /tmp/gengraphs.out 2>&1
    #
    # Daily reports
    #
    30 23 * * * /opt/zimbra/libexec/zmdailyreport -m
    #
    # crontab.mta
    #
    #
    # Queue logging
    #
    0,10,20,30,40,50 * * * * /opt/zimbra/libexec/zmqueuelog
    #
    # Spam training
    #
    0 23 * * * /opt/zimbra/bin/zmtrainsa >> /opt/zimbra/log/spamtrain.log 2>&1
    #
    # Spam training cleanup
    #
    45 23 * * * /opt/zimbra/bin/zmtrainsa --cleanup >> /opt/zimbra/log/spamtrain.log 2>&1
    #
    # Dspam cleanup
    #
    0 1 * * * [ -d /opt/zimbra/data/dspam/data/z/i/zimbra/zimbra.sig ] && find /opt/zimbra/data/dspam/data/z/i/zimbra/zimbra.sig/ -type f -name \*sig -mtime +7 -exec rm {} \; > /dev/null 2>&1
    8 4 * * * [ -f /opt/zimbra/data/dspam/system.log ] && /opt/zimbra/dspam/bin/dspam_logrotate -a 60 -l /opt/zimbra/data/dspam/system.log
    8 8 * * * [ -f /opt/zimbra/data/dspam/data/z/i/zimbra/zimbra.log ] && /opt/zimbra/dspam/bin/dspam_logrotate -a 60 -l /opt/zimbra/data/dspam/data/z/i/zimbra/zimbra.log
    #
    # Spam Bayes auto-expiry
    #
    20 23 * * * /opt/zimbra/libexec/sa-learn -p /opt/zimbra/conf/salocal.cf --dbpath /opt/zimbra/data/amavisd/.spamassassin --siteconfigpath /opt/zimbra/conf/spamassassin --force-expire --sync > /dev/null 2>&1
    #
    # Clean up amavisd/tmp
    #
    15 5,20 * * * find /opt/zimbra/data/amavisd/tmp -maxdepth 1 -type d -name 'amavis-*' -mtime +1 -exec rm -rf {} \; > /dev/null 2>&1

    #
    # crontab.store
    #
    # Log pruning
    #
    30 2 * * * find /opt/zimbra/mailboxd/logs/ -type f -name \*log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
    30 2 * * * find /opt/zimbra/log/ -type f -name stacktrace.\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
    #
    # Report on any database inconsistencies
    #
    0 23 * * 7 /opt/zimbra/libexec/zmdbintegrityreport -m
    #
    # Monitor for multiple mysqld to prevent corruption
    #
    #*/5 * * * * /opt/zimbra/libexec/zmcheckduplicatemysqld -e > /dev/null 2>&1
    #
    # Check zimbraVersionCheckURL for new update.
    # Only runs if this server matches zimbraVersionCheckServer
    # Only executes on zimbraVersionCheckInterval. min 2h interval
    #
    18 */2 * * * /opt/zimbra/libexec/zmcheckversion -c >> /dev/null 2>&1
    #
    # Invoke "ComputeAggregateQuotaUsageRequest" periodically
    #
    15 2 * * * /opt/zimbra/libexec/zmcomputequotausage > /dev/null 2>&1
    #
    # Invoke "client_usage_report.py" periodically to process /opt/zimbra/log/access_log* files
    #
    55 1 * * * /opt/zimbra/libexec/client_usage_report.py > /dev/null 2>&1
    #
    # Run zmgsaupdate util to trickeSync galsync accounts
    #
    49 0 * * 7 /opt/zimbra/libexec/zmgsaupdate > /dev/null 2>&1
    Once it's done, your server status will be update after some times ...

  5. #5
    Join Date
    Jun 2012
    Posts
    5
    Rep Power
    3

    Default Thanks

    Thank you for your reply, I reinstalled Zimbra and created new crontab (problem was missing crontab) after posting the last infos.

    Now I'm working on a online backup script for open source version, maybe best thing is to use vmware-ha and take virtual machine snapshots. At the moment I only have physical machines but in the next weeks I'll reconfigure everything

  6. #6
    Join Date
    Feb 2012
    Posts
    17
    Rep Power
    3

    Default

    I upgraded to 8.03 and and upgrade was fine all the stats where working in the web interface.
    This morning whene I arrived the web interface showed services failed.

    I checked the status from command prompt as followed.
    Release 8.0.3_GA_5664.RHEL6_64_20130305090204 CentOS6_64 FOSS edition
    zmcontrol status
    Host XXXXXXXX.XXX
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Running
    mta Running
    snmp Running
    spell Running
    stats Running
    zmconfigd Running
    I went ahead and rebooted server still the same problem.
    I tried the steps above to fix the problem but did not work.

    chown -R zimbra:zimbra /opt/zimbra/zimbramon/crontabs
    cat crontab >> crontab.zimbra
    bash: crontab.zimbra: Permission denied

    This is the error that I am getting.
    Can someone help me figure this out?

    Thanks
    Sam

  7. #7
    Join Date
    Jun 2012
    Posts
    5
    Rep Power
    3

    Default Try reinstalling

    Hello,

    try installing a new instance of zimbra, then check crontab to see if it's populated (crontab -e to edit)

    Then, stop zimbra and overwrite install with previous data

    After starting zimbra let crontab execute scripts for the first time (approx 15 min)

  8. #8
    Join Date
    Jun 2014
    Posts
    1
    Rep Power
    1

    Thumbs up change the permission

    I hope u sloved ur problem, I have today the same problem, so I changed the permission of /tmp/crontab.zimbra (chown and chmod).

    I have reinstalled crontab.
    I rebboot my server and all service are ok, only MTA, so I removed postfix and it's seems to be ok


    Thanks
    hedi
    we are dwarfs on the shoulders of giants

Similar Threads

  1. Replies: 0
    Last Post: 12-09-2012, 10:47 PM
  2. Replies: 1
    Last Post: 09-20-2011, 07:54 AM
  3. Replies: 1
    Last Post: 09-12-2010, 01:47 PM
  4. "NO APPEND failed" message when migrating mails
    By tkrag@mostlyharmless.dk in forum Administrators
    Replies: 8
    Last Post: 05-18-2007, 07:25 AM
  5. Replies: 3
    Last Post: 05-25-2006, 02:16 PM

Tags for this Thread

Posting Permissions

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