SAC - Could not login

[ulvheim]

Hi!

I'm having a hard time solving this one. So please, does anyone have any idea on how to fix this?:

I deleted a user due to inconsistencies in her mailbox, removing her from the LDAP database which is the backend to the scalix server.
I ran the omldapsync-command and logged onto SAC to verify that the user had been deleted.
When I saw that she was still showing up in SAC i deleted the user manually from the list. The pop-up box showing "Deleting user" was up for a while, and then my browser crashed.

After this, I have been unable to log into SAC, which gives me the following reason why:

"Could Not Login
Could not fetch configuration information.
Possible problem with administration server"

When running a omshowu-command, for any user, it comes up blank.

The omldapsync-command now exits with this:

scalix:/var/opt/scalix/sx/tomcat/logs # omldapsync -S -u new
2007-12-10 19:25:36 STATUS: LDAP dir sync import new started ###############
--------> Sending SOAP Request to Ubermanager@http://scalix.domain.com/caa/ for method:GetMailNodesList
SOAP part:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<scalix-caa:CAARequestMessage xmlns:scalix-caa="http://www.scalix.com/caa">
<ServiceType>scalix.res</ServiceType>
<FunctionName>GetMailNodesList</FunctionName>
<Credentials id="12345">
<Identity name="scalix.replicator@domain.com" passwd="xxxxxxxx"/>
</Credentials>
<ScalixServers/>
<GetMailNodesListParameters/>
</scalix-caa:CAARequestMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--------> Received SOAP Response from Ubermanager@http://scalix.domain.com/caa/
SOAP part:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>CAA Service Error</faultstring>
<detail>
<scalix-caa:fault-details xmlns:scalix-caa="http://www.scalix.com/caa">
<message>Failed to obtain mailnodes from all the registered servers. Please check the Administration server logs</message>
<errorcode>UM-1029</errorcode>
</scalix-caa:fault-details>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
error: Response contains failure report
2007-12-10 19:26:37 ERROR: failed to run omldapagent
2007-12-10 19:26:37 STATUS: LDAP dir sync import failed, error=2 ###########
2007-12-10 19:26:37 STATUS: LDAP dir sync export new started ###############
2007-12-10 19:26:37 INFO: agreement type 13 only supports import operation
2007-12-10 19:26:37 STATUS: LDAP dir sync export new completed #############

And the scalix-caa.log gives me the following output:
2007-12-10 19:57:46,561 ERROR [RESServiceHandler.GetMailNodesList:960] Server scalix.domain.com terminated with status FAILED:3
2007-12-10 19:57:46,561 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server scalix.domain.com. No document received!

I am clueless as to why it's acting ut the way it is, so any help will be appreciated!

PS. The webmail still seems to work, but I guess that it will be a matter of moments before this fails too (if it cannot authenticate against the LDAP).

[dannyt]

Hi,

From the info supplied I can only guess that you have an external LDAP implementation where the Scalix users are defined, then omldapsync is used to create and maintain the mailbox in Scalix ...

Since omldapsync shares the same processing engine as SAC, the primary error appears to be that SAC is no longer working. One thing to try is to running the Scalix installer again to reconfigure SAC. Once SAC is working again, try rerunning omldapsync as before.

Alternatively, try adding a test user using SAC (bypass external LDAP directory and omldapsync). Also worth checking the log files (/var/opt/scalix/XYZ/tomcat/logs for scalix-caa.log and scalix-res.log) for error messages.

Regards,
Danny

[kanderson]

if you do a "ps aux|grep omdel" it's possible that the browser crashed but that SAC is still trying to do the delete in the background. Can you check that?

If that's the case, kill the process and delete them again.

Kev.