Zimbra won't start: slapd loglevel wildness

[blackpuma]

I have had Zimbra running for a week or so in a VMware virtual machine. I shut the machine down, bumped the RAM up, and can't get zimbra to start.

/var/log/zimbra contents are last.

I pull up /opt/zimbra/conf/slapd.conf in vim and see that the offending line 34 says:

loglevel ^[%@32768

In other words, there's an <ESC> character, %@32768. If I change this or comment it out, it always gets replaced when I do

su - zimbra
zmcontrol start

What is causing this? How do I fix this? Our e-mail is completely down until I can get this running again.

Thank you very much!

Dec 29 20:10:08 mail zimbramon[15716]: 15716:info: 2007-12-29 20:10:02, STATUS: mail.inn0vate.com: stats: Stopped 
Dec 29 20:10:43 mail zimbramon[16326]: 16326:info: Starting services 
Dec 29 20:10:44 mail slapd[16500]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:10:44 mail slapd[16500]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:10:44 mail slapd[16500]: slapd stopped. 
Dec 29 20:10:44 mail slapd[16500]: connections_destroy: nothing to destroy. 
Dec 29 20:10:49 mail slapd[16505]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:10:49 mail slapd[16505]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:10:49 mail slapd[16505]: slapd stopped. 
Dec 29 20:10:49 mail slapd[16505]: connections_destroy: nothing to destroy. 
Dec 29 20:10:55 mail slapd[16535]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:10:55 mail slapd[16535]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:10:55 mail slapd[16535]: slapd stopped. 
Dec 29 20:10:55 mail slapd[16535]: connections_destroy: nothing to destroy. 
Dec 29 20:11:00 mail slapd[16565]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:11:00 mail slapd[16565]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:11:00 mail slapd[16565]: slapd stopped. 
Dec 29 20:11:00 mail slapd[16565]: connections_destroy: nothing to destroy. 
Dec 29 20:11:05 mail slapd[16596]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:11:05 mail slapd[16596]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:11:05 mail slapd[16596]: slapd stopped. 
Dec 29 20:11:05 mail slapd[16596]: connections_destroy: nothing to destroy. 
Dec 29 20:11:10 mail slapd[16626]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:11:10 mail slapd[16626]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:11:10 mail slapd[16626]: slapd stopped. 
Dec 29 20:11:10 mail slapd[16626]: connections_destroy: nothing to destroy. 
Dec 29 20:11:15 mail slapd[16656]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:11:15 mail slapd[16656]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:11:15 mail slapd[16656]: slapd stopped. 
Dec 29 20:11:15 mail slapd[16656]: connections_destroy: nothing to destroy. 
Dec 29 20:11:21 mail slapd[16686]: @(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:48:12) $ 	build@build10.re.zimbra.com:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd 
Dec 29 20:11:21 mail slapd[16686]: /opt/zimbra/conf/slapd.conf: line 34: <loglevel> unknown level "@32768" 
Dec 29 20:11:21 mail slapd[16686]: slapd stopped. 
Dec 29 20:11:21 mail slapd[16686]: connections_destroy: nothing to destroy. 
Dec 29 20:12:04 mail zmtomcatmgr[17131]: status requested
Dec 29 20:12:04 mail zmtomcatmgr[17131]: file /opt/zimbra/log/zmtomcatmgr.pid does not exist
Dec 29 20:12:04 mail zmtomcatmgr[17131]: assuming no other instance is running
Dec 29 20:12:04 mail zmtomcatmgr[17131]: no manager process is running
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: antispam: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: antivirus: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: ldap: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: logger: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: mailbox: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: mta: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: snmp: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: spell: Stopped 
Dec 29 20:12:05 mail zimbramon[16917]: 16917:info: 2007-12-29 20:12:01, STATUS: mail.inn0vate.com: stats: Stopped

[blackpuma]

I got things running, but the core problem still exists.

After poking around in /opt/zimbra/conf, I noticed that there is the file:

slapd.conf.in

it appears to be something that the startup processes and uses to create slapd.conf.

Line 34 of slapd.conf.in says:

loglevel @@ldap_log_level@@

I was able to get past the problem by changing it to:

#loglevel @@ldap_log_level@@
loglevel 256

which generates the following in the slapd.conf file:

#loglevel ^[%@32768
loglevel 256

As you can see, the problem is still there in the comments.

So while I'm up and running again, it doesn't address the core question of why this line, which seems to have been working before, suddenly is freaking out with the ^[%@32768 value.

[todd_dsm]

As a curious mind, I'd like to know the answer too.

[mmorse]

Old thread, but based on the @@ldap_log_level@@ keep getting replaced in the sldap.conf/sldap.conf.in I'd say examine:
zmlocalconfig | grep ldap_log_level

zmlocalconfig -e ldap_log_level=32768
zmcontrol stop/start

This on 5.0.10 or are you still running 5.0.5? (profile)

[todd_dsm]

Originally Posted by mmorse

This on 5.0.10 or are you still running 5.0.5? (profile)

Sorry it took so long getting back to you on this. I'm using 5.0.11.

[todd_dsm]

I started seeing this during the walk-through for UNIX and Windows Accounts in Zimbra LDAP and Zimbra Admin UI

$ /opt/zimbra/openldap-2.3.43.5z/sbin/slapindex -v -f /opt/zimbra/conf/slapd.conf.in
/opt/zimbra/conf/slapd.conf.in: line 36: <loglevel> unknown level "@@ldap_log_level@@"
slapindex: bad configuration file!

Then, per the suggestion, ran with this:

$ zmlocalconfig | grep ldap_log_level
ldap_log_level = 49152

$ zmlocalconfig -e ldap_log_level=32768

$ zmcontrol stop
$ zmcontrol start

$ zmlocalconfig | grep ldap_log_level
ldap_log_level = 32768

Went to re-attempt the index:

$ zmcontrol stop
$ /opt/zimbra/openldap-2.3.43.5z/sbin/slapindex -v -f /opt/zimbra/conf/slapd.conf.in
/opt/zimbra/conf/slapd.conf.in: line 36: <loglevel> unknown level "@@ldap_log_level@@"
slapindex: bad configuration file!

The loglevel did change but the error persists.

[todd_dsm]

OK, I found this answer in the #zimbra irc room:

1) $vi /opt/zimbra/conf/slapd.conf.in
2) Comment out the "@@ldap_log_level@@" and enter on the next line
3) loglevel 256 (or whatever)

slapindex does not appear to be parsing this variable correctly. Just set it to a static value.