=^.^=

Zimbra "Some Services Are Not Running" Even Though They Are

karma

If you have logged in to your Zimbra administration interface and been told that "Some services are not running" despite what zmcontrol status is telling you there may be a problem with the cron scripts.

You can force a manual update by running:

# sudo -u zimbra /opt/zimbra/libexec/zmstatuslog

To re-load the cron settings perform the following:

# cd /opt/zimbra/zimbramon/crontabs
# cat * > crontab.zimbra
# sudo -u zimbra crontab crontab.zimbra

Catastrophic Zimbra Meltdown Over Dinky Missing Log Files

karma

Upon restarting a Zimbra instance this morning:

        Starting ldap...Done.
        Starting zmconfigd...Done.
        Starting logger...Failed.
Starting logswatch...failed.


        Starting mailbox...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.

It was worse than that.

# su - zimbra
$ zmcontrol status
Host mx.drlogick.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
        zmconfigd               Running

It took me some time and frustration to find these and figure it out:

$ cat /opt/zimbra/log/zmswatch.out
Error opening /var/log/zimbra.log: No such file or directory at /opt/zimbra/data/tmp/.swatch_script.6212 line 98.

$ cat /opt/zimbra/log/zmlogswatch.out
Error opening /var/log/zimbra-stats.log: No such file or directory at /opt/zimbra/data/tmp/.swatch_script.5784 line 92.

Substitute with zcat, if like in my situation these lines are actually hidden in a logrotated file.

The problem is that I had cleared out my /var/log as the available root fs space dwindled. Apparently Zimbra can't survive without these two log files. Re-create them then restart zimbra:

# touch /var/log/zimbra-stats.log
# touch /var/log/zimbra.log
# chown zimbra: /var/log/zimbra-stats.log
# chown zimbra: /var/log/zimbra.log

Failed to Load Module "glx" Module Does Not Exist, libglx.so is Missing

karma

If you recently un-installed fglrx then switched back to the open source radeon driver you may be left with a couple of broken links to a missing libglx.so and no OpenGL support in X:

[ 65311.851] (II) LoadModule: "glx"
[ 65311.851] (WW) Warning, couldn't open module glx
[ 65311.851] (II) UnloadModule: "glx"
[ 65311.851] (II) Unloading glx
[ 65311.851] (EE) Failed to load module "glx" (module does not exist, 0)

It is necessary to rebuild/reinstall xorg-server:

# emerge xorg-server

Lecture for Lunch: Greg Palast and RFK Jr. in NYC - MayDay 2007

karma

Legendary investigavtive journalist Greg Palast and RFK Jr. deliver a talk about how the news media have failed democracy and we have failed the medium by allowing it to become a consolidated, information-starved wasteland.

It's not you - the audio is out of sync for about half of it. I found it worth watching anyway.

Documentary for Dinner: Prisoner X (2013)

karma

Journeyman Pictures presents Trevor Bormann's ABC documentary on Ben Zygier, an Israeli-Australian intelligence operative who committed suicide in 2010 after being held in secretive detention for over a year.