Syslog message. What...

[Bill Brock]

does this mean???

Jul 10 14:30:37 webmail slapd[5422]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute
Jul 10 14:30:37 webmail slapd[5422]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute
Jul 10 14:30:38 webmail slapd[5422]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute
Jul 10 14:30:38 webmail slapd[5422]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
Jul 10 14:30:38 webmail slapd[5422]: <= bdb_equality_candidates: (zimbraServiceEnabled) index_param failed (18)
Jul 10 14:30:38 webmail slapd[5422]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute

[mmorse]

Probably this:

Originally Posted by Abak

and some lines that repeat in /var/log/zimbra.log

Originally Posted by phoenix

You can ignore the errors in /var/log/zimbra.log - they're only a warning about a missing index (no, it shouldn't be indexed).

[Bill Brock]

When opening the admin console, sometimes the server status is there and sometimes it tells me the logger service must be installed. It is installed and works part of the time. I thought these messages may be related to the server status problem. If not, do you know why the status may show up sometimes and not at other times? It seems like I may have to restart the server to get it to come back.

I running on SuSE 10 and everything appears to be working. At least I'm sending and receiving mail.

[mmorse]

what version? (zmcontrol -v) -while your at it you might update your profile to display it when you post

some related:
Server status data is not available
Bug 16377 - admin>server status: 'logger service is not installed' message is displayed
Bug 7904 - logger fails when ZCS installed on Suse10.1

[Bill Brock]

4.5.4_GA_763.SuSE10_20070418140902 SuSE10 FOSS EDITION

[Bill Brock]

Without doing anything, I check the server status from the admin console and it shows back up.

Even though the admin console refuses to show the status at times, if I view the system logs directly, the logs are working. It seems the admin console just has trouble from time to time.

[mmorse]

It's been a while, but I think I remember that some of the 'logger service must be installed' issues were solved in 4.5.5 and 4.5.6 -you might consider upgrading

If logger actually quits occasionally - upgrade to 4.5.6: Bug 14945 - logger intermittently stops without warning after pruning
Help us fix Bug 14945 :)