No web access to either sac or swa - ldap error?

[joaster]

Hi,

After a succesfull install of a Scalix 10.0.1 server on FC4 (still working) it tried to install Scalix 10.0.1 onto another PC. This PC is a FC5-Xen 3.0.1 virtualization server on which FC4 is installed in a guest domain. Installing Scalix 10.0.1 into that FC4 domain went smootly (I had to use the text installer, but no warnings or errors were displaged).

Now I am ready to configure Scalix but it does not allow web access to either sac or swa. The error messages I get are:

[root@server-em1 ~]# tail -80 /opt/scalix-tomcat/logs/caa.log
.nl/res/RESDispatcher|LISTEN|300|server-em1|server-em1.webnetworks.nl|10.0.1 from host:server-em1.webnetworks.nl
2006-08-02 15:22:00,890 ERROR [LDAPHelperUtils.getTargetHost:362] javax.naming.NamingException: [LDAP: error code 1 - [OM.LDAP 1001]: directory

engine died on write]
2006-08-02 15:22:11,963 ERROR [RbacAuthorizationHelper.authenticateUser:87] Exception:
javax.naming.NamingException: [LDAP: error code 1 - [OM.LDAP 1000]: directory engine died on read]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
etc.

root@server-em1 ~]# tail -100 /opt/scalix-tomcat/logs/scalix-swa_log.2006-08-02.txt
2006-08-02 15:30:19 StandardContext[/webmail]ip: 192.168.100.210; username: sxadmin@webnetworks.nl; message:

<SOAP-ENV:Fault><faultcode>SOAP-ENV:SERVER.Error</faultcode><faultstring>Cannot connect to the mail server at server-em1.webnetworks.nl!

The mail server on server-em1.webnetworks.nl appears to be down.

</faultstring><detail><e:Error xmlns:e="http://scalix.com/errors"><message>Cannot connect to the mail server at server-em1.webnetworks.nl!

The mail server on server-em1.webnetworks.nl appears to be down.

</message><debug>java.lang.Error: Cannot connect to the mail server at server-em1.webnetworks.nl!

The mail server on server-em1.webnetworks.nl appears to be down.
at com.scalix.swa.service.MailServices.authenticate(MailServices.java:271)
at com.oddpost.server.partner.Authenticate.init(Authenticate.java:155)
at com.oddpost.server.partner.PartnerImplementations.createAuthenticate(PartnerImplementations.java:287)
at com.oddpost.server.SoapAuth.isAuthenticated(SoapAuth.java:159)
at com.oddpost.server.HttpRequestHandler.handleRequest(HttpRequestHandler.java:209)
at com.oddpost.server.SoapServlet.doPost(SoapServlet.java:50)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at com.oddpost.server.filter.HttpConfFilter.doFilter(HttpConfFilter.java:182)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
... skipping the last 25 lines as irrelevant...
Caused by: javax.mail.MessagingException: Connection refused;
nested exception is:
java.net.ConnectException: Connection refused
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:335)
at javax.mail.Service.connect(Service.java:233)
at com.scalix.swa.service.MailServices.authenticate(MailServices.java:255)
... 36 more
</debug></e:Error></detail></SOAP-ENV:Fault>


I thought of a LDAP problem so I ran the following two commands:

[root@server-em1 ~]# lsof -i :ldap
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
omslapd 1084 root 8u IPv4 2603 TCP *:ldap (LISTEN)

[root@server-em1 ~]# lsof -i :8009
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
java 1153 root 22u IPv4 3436 TCP localhost.localdomain:8009 (LISTEN)
java 1153 root 25u IPv4 6214 TCP localhost.localdomain:8009->localhost.localdomain:39966 (ESTABLISHED)
java 1153 root 26u IPv4 19782 TCP localhost.localdomain:8009->localhost.localdomain:32924 (ESTABLISHED)
java 1153 root 27u IPv4 16938 TCP localhost.localdomain:8009->localhost.localdomain:32922 (ESTABLISHED)
java 1153 root 28u IPv4 19809 TCP localhost.localdomain:8009->localhost.localdomain:32929 (ESTABLISHED)
java 1153 root 29u IPv4 19779 TCP localhost.localdomain:8009->localhost.localdomain:32923 (ESTABLISHED)
java 1153 root 32u IPv4 19800 TCP localhost.localdomain:8009->localhost.localdomain:32926 (ESTABLISHED)
java 1153 root 33u IPv4 19797 TCP localhost.localdomain:8009->localhost.localdomain:32925 (ESTABLISHED)
java 1153 root 34u IPv4 19803 TCP localhost.localdomain:8009->localhost.localdomain:32927 (ESTABLISHED)
java 1153 root 35u IPv4 19807 TCP localhost.localdomain:8009->localhost.localdomain:32928 (ESTABLISHED)
httpd 1186 apache 16u IPv4 16937 TCP localhost.localdomain:39966->localhost.localdomain:8009 (ESTABLISHED)
httpd 1187 apache 16u IPv4 19796 TCP localhost.localdomain:32924->localhost.localdomain:8009 (ESTABLISHED)
httpd 1188 apache 16u IPv4 19778 TCP localhost.localdomain:32922->localhost.localdomain:8009 (ESTABLISHED)
httpd 1192 apache 16u IPv4 19808 TCP localhost.localdomain:32928->localhost.localdomain:8009 (ESTABLISHED)
httpd 1193 apache 16u IPv4 19781 TCP localhost.localdomain:32923->localhost.localdomain:8009 (ESTABLISHED)
httpd 1194 apache 16u IPv4 19811 TCP localhost.localdomain:32929->localhost.localdomain:8009 (ESTABLISHED)
httpd 1195 apache 16u IPv4 19806 TCP localhost.localdomain:32927->localhost.localdomain:8009 (ESTABLISHED)
httpd 1197 apache 16u IPv4 19802 TCP localhost.localdomain:32926->localhost.localdomain:8009 (ESTABLISHED)
httpd 1347 apache 16u IPv4 19799 TCP localhost.localdomain:32925->localhost.localdomain:8009 (ESTABLISHED)

The first seems fine to me, but the second is only connected to the local host. Is this correct?

I have been wrestling with this problem the whole day now and i can't get it fixed. Can somebody please help me on this one?

Regards,
Joost.

[dkelly]

Please check the Scalix fatal file as this indicates the LDAP server had a problem rather than the Admin console.

Cheers

Dave

[joaster]

Dave,

The /var/opt/scalix/logs/fatal file is empty, so no fatal errors in Scalix I assume.

I agree there's something wrong with the LDAP server, the command 'omldapsearch' returns an error.

[root@server-em1 ~]# omldapsearch -D cn=sxqueryadmin,o=scalix -w passwd cn=*
ldap_bind: Operations error
ldap_bind: additional info: [OM.LDAP 1000]: directory engine died on read

Any idea how to solve this?

Joost.