SAC Keeps Losing Ability To Log In

[thejoker101]

Seemingly every day or so I will lose the ability to log into the SAC.

When I try, I get this error:

Could Not Login
Could not fetch configuration information.
Possible problem with the admiinistraton server.

So, I reboot and it fixes it for a while. What's the deal?

[BigJoe]

next time before you reboot do an>
omstat -a

and see what the status of LDAP is. If it is off just run>
omon LDAP

--Joe

[thejoker101]

Here is the output of omstat -a:

scalix:/home/jasher # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 09.21.05
Notification Server Started 09.21.05 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped
Database Monitor Started 09.21.05
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 09.21.05
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 09.21.05
SMTP Relay Started 09.21.05
Mime Browser Controller Started 09.21.05


I believe this means that LDAP is on. However, I am still receiving the error. So I restarted LDAP and I still get the same error.

[julio]

Can you check the tomcat.home/logs/caa.log to see what are the error messages or fatal exceptions?

Secondly, what login ID are you using to log into?

[thejoker101]

These are the errors created when I try and log in to the SAC:

2005-09-23 14:33:09,427 FATAL [RESServiceHandler.executeRESCommand:1404] java.lang.reflect.InvocationTargetException
2005-09-23 14:33:09,428 FATAL [RESServiceHandler.executeRESCommand:1412] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2005-09-23 14:33:09,433 WARN [GetServerNameGenerationRules.createSOAPResponseMessage:102] Skipping server scalix.xteconline.com no document received.
2005-09-23 14:33:09,504 FATAL [RESServiceHandler.executeRESCommand:1404] java.lang.reflect.InvocationTargetException
2005-09-23 14:33:09,505 FATAL [RESServiceHandler.executeRESCommand:1412] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2005-09-23 14:33:09,510 WARN [GetServerMailAddressGenerationRules.createSOAPResponseMessage:96] Skipping server scalix.xteconline.com no document received.
2005-09-23 14:33:09,580 FATAL [RESServiceHandler.GetMailNodesList:555] java.lang.reflect.InvocationTargetException:scalix.xteconline.com
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.scalix.sac.ubermgr.res.LocalServiceHandler.service(LocalServiceHandler.java:100)
at com.scalix.sac.ubermgr.res.RESServiceHandler.GetMailNodesList(RESServiceHandler.java:514)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.scalix.sac.ubermgr.caa.RESService.doRequest(RESService.java:108)
at com.scalix.caa.soap.SOAPDispatcherServlet.onMessage(SOAPDispatcherServlet.java:267)
at com.scalix.caa.soap.SAAJServlet.doPost(SAAJServlet.java:123)
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 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: java.io.IOException: Cannot allocate memory
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at com.scalix.sac.res.util.CmdExecution.executeCmd(CmdExecution.java:99)
at com.scalix.sac.res.handlers.Omshowrt.execute(Omshowrt.java:27)
... 39 more
2005-09-23 14:33:09,584 ERROR [GetMailNodesList.buildResponseMessage:101] Skipping server scalix.xteconline.com. No document received!

I'm using the administrator login id.

[ScalixSupport]

Can you ensure that tomcat is run as the root user and also that /opt/scalix/bin is in its path.

The tomcat init.d script in the admin_resource_kit/ directory should address both those issues.

Cheers

Dave

[julio]

From the log I see couple of things wrong:

1. I see that you running out of memory when system (RES plus Ubermanager) is attempting to execute omshowrt.
2. Ensure that /opt/sca/bin and /opt/scalix/diag are in the path, and also ensure that tomcat runs as root.

[kali]

I started getting this exact same error!! Very frustrating, as it's very difficult to debug what is happening with the Scalix architecture.

In the end - so please try this - it is an LDAP connection issue (that has been said in prior threads). My cause - I believe - was the addition of a "Full Administrator" to a user which did not have the same domain as the Scalix server (it handles a couple).

The fix - or at least it worked for me - was to blank out the line in the ubermanager.properties which states "ubermanager.console.localDomains="

It had added the domain of the user which was given rights... but seems to have messed up the ability of the original sxadmin "user" to login to the sac.

Other thoughts and ideas welcome - and definitely if this works for others, then the handling of the domain of admins needs some attention.

[julio]

From looking at the stack trace, it appears that you are running out of memory when one of the commands is being executed.

Do one of the following:

1. Shut down tomcat
2. cd /etc/opt/scaliix/caa/config
3. edit the log4.propertiesfile
4. replace INFO with DEBUG
4. remove tomcat.catalina.home/work and tomcat.catalina.home/webapps/caa
5. restart tomcat again
6. cd tomcat.catalina.home/logs
7. tail -f caa.log

This will show you exactly what is going on and where it is failing. The log will show what calls are being made to the ubermanager. A good way to debug.
Please do not change ubermanager.properties at will.

If you are not getting authentication errors from the LDAP, then more than likely the problem is elsewhwere, lile the trace below inidacated -- memory allocation errors.