Difference between revisions of "CentOS 8.x Zimbra all service status showing down on Zimbra admin interface"

From Notes_Wiki
(Created page with "<yambe:breadcrumb self="All service status showing down on Zimbra admin interface">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb> =CentOS 8.x Zimbra all service status showing do...")
 
m
 
Line 1: Line 1:
<yambe:breadcrumb self="All service status showing down on Zimbra admin interface">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x email servers]] > [[CentOS 8.x Zimbra]] > [[CentOS 8.x Zimbra all service status showing down on Zimbra admin interface]]
=CentOS 8.x Zimbra all service status showing down on Zimbra admin interface=


It is possible that all services are showing as running in output of below commands:
It is possible that all services are showing as running in output of below commands:
Line 53: Line 52:




<yambe:breadcrumb self="All service status showing down on Zimbra admin interface">CentOS 8.x Zimbra|Zimbra</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x email servers]] > [[CentOS 8.x Zimbra]] > [[CentOS 8.x Zimbra all service status showing down on Zimbra admin interface]]

Latest revision as of 03:33, 30 March 2022

Home > CentOS > CentOS 8.x > CentOS 8.x email servers > CentOS 8.x Zimbra > CentOS 8.x Zimbra all service status showing down on Zimbra admin interface

It is possible that all services are showing as running in output of below commands:

su - zimbra
zmcontrol status

while on admin interface they appear as down.

To fix it follow below steps:

  1. Check the permissions of /var/spool/cron/zimbra file. It should be owned by zimbra and should be 600. If not please run as root user:
    /opt/zimbra/libexec/zmfixperms
    chown zimbra:zimbra /var/spool/cron/zimbra
    chmod 600 /var/spool/cron/zimbra
    Note that running /opt/zimbra/libexec/zmfixperms ( https://wiki.zimbra.com/wiki/Fix_the_Zimbra_Collaboration_Permissions ) does not fixes ownership of zimbra cron file. Hence manually running chown / chmod is required
  2. Validate 'zmstatuslog' is configured to run as part of cron using as zimbra user:
    crontab -l | grep zmstatuslog
    There should be a crontab entry executing '/opt/zimbra/libexec/zmstatuslog' every two minutes
  3. Restart zimbra stat service using as zimbra user:
    zmstatctl restart
    zmloggerctl restart
  4. Look at '/opt/zimbra/log/zmlogswatch.out' file for errors similar to 'illegal attempt to update using time <EpocTime> when last update time is <EpocTime>
    grep -i illegal /opt/zimbra/log/zmlogswatch.out
    1. In case there are illegal attempt related entries in above file use;
      zmloggerctl stop #Or zmcontrol stop if downtime is available
      mkdir /opt/zimbra/logger/db/data/rrds/old
      mv /opt/zimbra/logger/db/data/rrds/*.rrd /opt/zimbra/logger/db/data/rrds/old/
      zmloggerctl start #Or zmcontrol start
  5. Executed below 3-4 times in continuous succession to get faster updation of service status on admin dashboard as zimbra user:
    /opt/zimbra/libexec/zmstatuslog
    /opt/zimbra/libexec/zmstatuslog
    /opt/zimbra/libexec/zmstatuslog


Refer:



Home > CentOS > CentOS 8.x > CentOS 8.x email servers > CentOS 8.x Zimbra > CentOS 8.x Zimbra all service status showing down on Zimbra admin interface