LDAP error when trying to login to either sac or swa.

[joaster]

Hi,

After a clean install (v10.0.1) on FC4 I tried to configure the system. The problem is that sxadmin is not allowed to login to either sac or swa, it end with the following errors:

[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]

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.

It has to do with the LDAP service, so I tried the following:

[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

However these errors are not seen by Scalix as fatal errors since the /var/opt/scalix/logs/fatal file is empty.

I would really like to know how to go from here, because right now I can't do anything with te system (not even the configuration).

Regards,
Joost.

[ScalixSupport]

I think there is something else going on here other than ldap issues. The swa error says it cannot connect to the mail server. It is worth doing an:

omstat -s

and

omstat -a

but I'm guessing all the services are started.

I suspect that there is a host/dns configuration issue that is causing you this grief. For the purposes of installation please edit your /etc/hosts file to contain only the localhost and host name of the server as follows:

Code: Select all

127.0.0.1       localhost.localdomain   localhost
x.x.x.x    server-em1.webnetworks.nl server-em

Then uninstall and reinstall everything.

Thanks,
Don

[joaster]

Thanks for the reply,

The /etc/hosts file was exactly like you described but I found out that some other services were not running either (IMAP for example), although the installer did not give me any errors.
Therefore I decided to reinstalled my XEN server with CentOS 4.3. And the result is wonderfull, all seems to work perfectly.

I have one question though. When I run omstat -a as you proposed in your email, I see that the ISS is not running: Item Structure Server Stopped.

What does this service do and how do I get it running (if necessary).

Regards,
Joost.

[Valerion]

I have one question though. When I run omstat -a as you proposed in your email, I see that the ISS is not running: Item Structure Server Stopped.

What does this service do and how do I get it running (if necessary).

You can get it running with

Code: Select all

omsetsvc -a iss y
omon -w iss

The ISS is responsible for tracking changes in the mailstore, used for single-user mailbox restores. Unless you need that functionality (and it's not the most intuitive to get working the first time), you don't need it.

Check out the document named Corruption/Recovery, ISDB, and SUR in the Knowledge Base for more info.

[joaster]

Thanks, for the answer.