Java defunct

[molliver]

Hi,

I have just installed zimbra on a new server which is running CentOs4.2. It seams to have come up ok and I can create a/c's and send and recieve mail. However I notice there are java defunct processes being created is there a reson for this and a way to stop it?

Also can anyone tell me how i turn on logging for postfix and spam/virus checking and where I look for the logs.

The system looks good though.

Thanks

Mark

[KevinH]

Hi,

I have just installed zimbra on a new server which is running CentOs4.2. It seams to have come up ok and I can create a/c's and send and recieve mail. However I notice there are java defunct processes being created is there a reson for this and a way to stop it?

Also can anyone tell me how i turn on logging for postfix and spam/virus checking and where I look for the logs.

The system looks good though.

Thanks

Mark

The defunct procs should go away in the new build. postfix log is in /var/log/zimbra.log

[molliver]

Hi,

You say the defunct processes should go away in the new build, do you know when this will be ready?

I am currently using zcs-3.0.M1_21-src.tgz

Also if i create a local.cf in /opt/zimbra/conf/spamassassin is zimbra configured to respect this?


Thanks

Mark

[bjared]

EDIT: We're using ZCS NE 4.5.5 on Centos 4.2

[root@zimbra1 ~]# ps auxw| grep Z | grep -v ZIMB | wc -l
586

nrpe (a service for nagios) and sshd often die when this happens.

How do I determine why this is happening?

I see some of these lines in /var/log/zimbra.log:

Jun 1 07:53:12 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
Jun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
Jun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
Jun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
Jun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)


I see this in /opt/zimbra/log/mailbox.log:

java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuf fer(OutputRecord.java:283)
at com.sun.net.ssl.internal.ssl.OutputRecord.write(Ou tputRecord.java:272)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:666)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
at com.zimbra.cs.pop3.Pop3Handler.sendMessage(Pop3Han dler.java:434)
at com.zimbra.cs.pop3.Pop3Handler.doRETR(Pop3Handler. java:625)
at com.zimbra.cs.pop3.Pop3Handler.processCommandInter nal(Pop3Handler.java:257)
at com.zimbra.cs.pop3.Pop3Handler.processCommand(Pop3 Handler.java:141)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:231)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:198)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)

I'm doing a 'zmcontrol stop' and I don't see any more zombie processes.

Now doing a 'zmcontrol start' ... things look good for now. This is the second time this has happened. Last time I was dealing with this was on the 29th of May. Actually, I see one defunct process already. I tried grepping for its PID in the logs, and couldn't find anything. Any ideas?

20 minutes later:
zimbra 28106 0.3 0.0 0 0 pts/1 Z 08:08 0:03 [java]
zimbra 28341 0.4 0.0 0 0 pts/1 Z 08:09 0:03 [java]
zimbra 28854 0.6 0.0 0 0 pts/1 Z 08:13 0:03 [java]
zimbra 29015 0.8 0.0 0 0 pts/1 Z 08:14 0:03 [java]
zimbra 29145 0.9 0.0 0 0 pts/1 Z 08:15 0:03 [java]
zimbra 30483 2.4 0.0 0 0 pts/1 Z 08:19 0:03 [java]
zimbra 30912 6.5 0.0 0 0 pts/1 Z 08:20 0:03 [java]


--Brian

[djve]

The messages:

Sun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)

comes from OpenLDAP when there is no index on an attribute that is being referenced. A bit of a pain as not all items need an index.

I'd wait for a new release of Zimbra and see if developers address this. They may not as you don't want an index on all attributes. This is a problem with OpenLDAP not Zimbra as such. I'm running OpenLDAP at work so I'm familiar with the many error messages about indecies.

If you really need to fix it yourself all you need to do is edit the slapd.conf file and add a line for each attribute: "index attribute type" i.e.
index zimbraMailStatus eq
The OpenLDAP project is the best place for info on OpenLDAP. The slapd.conf man page has a little on index usage.

[phoenix]

The messages:

Sun 1 07:53:23 zimbra1 slapd[12176]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)

comes from OpenLDAP when there is no index on an attribute that is being referenced. A bit of a pain as not all items need an index.

I'd wait for a new release of Zimbra and see if developers address this. They may not as you don't want an index on all attributes. This is a problem with OpenLDAP not Zimbra as such. I'm running OpenLDAP at work so I'm familiar with the many error messages about indecies.

If you really need to fix it yourself all you need to do is edit the slapd.conf file and add a line for each attribute: "index attribute type" i.e.
index zimbraMailStatus eq
The OpenLDAP project is the best place for info on OpenLDAP. The slapd.conf man page has a little on index usage.

Under no circumstances do we recommend those fields be indexed, if the logging is a problem it should be disabled as mentioned in another thread on the forum.

[djve]

Just checked out:
http://www.zimbra.com/forums/adminis...3-4-5-4-a.html

It goes into how to set LDAP logging to 0 (turn it off).

This should help the original poster if he doesn't want the messages appearing in the logs.

I've left logging as Zimbra distrbuted it as the messages are nothing to worry about.