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:
Code:
loglevel @@ldap_log_level@@
I was able to get past the problem by changing it to:
Code:
#loglevel @@ldap_log_level@@
loglevel 256
which generates the following in the slapd.conf file:
Code:
#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.