Scalix Forums

I´m testing Scalix Entreprise on Centos 5.2, installation went smooth and trouble free. Everything seems to be working OK except the management console.

If I logon as an admin, the first time works OK, but if I logoff and try to login again the server responds:

Could not login
Could not fetch server list

And this appears in scalix-caa.log:

2009-04-30 10:25:18,352 FATAL [RESTransformer.createSOAPResponseMessage:60] Exception thrown
java.lang.NullPointerException
at com.scalix.sac.ubermgr.transformers.GetServersList.buildResponseMessage(GetServersList.java:63)
at com.scalix.sac.ubermgr.caa.MessageRequestFactory.createMessage(MessageRequestFactory.java:37)
at com.scalix.sac.ubermgr.caa.RESTransformer.createSOAPResponseMessage(RESTransformer.java:58)
at com.scalix.caa.soap.SOAPDispatcherServlet.onMessage(SOAPDispatcherServlet.java:276)
at com.scalix.caa.soap.SAAJServlet.doPost(SAAJServlet.java:123)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Unknown Source)
2009-04-30 10:25:18,356 FATAL [SOAPDispatcherServlet.onMessage:279] Response message could not be transformed: 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>
<Credentials id="undefined">
<Identity
name="USER@DOMAIN" passwd="PASSWORD"/>
</Credentials>
<FunctionName>GetServersList</FunctionName>
<GetServersListParameters/>
</scalix-caa:CAARequestMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

(edited USER, DOMAIN and PASSWORD)

Any ideas??

Hello,

I am experiencing the same "Could not fetch server list" error when attempting to log into the SAC front-end.

This Scalix Community Edition was installed a couple of months back for testing (on a fresh CentOS5 box). All was ok, until today when I came to continue testing. I was having a problem with SWA ("An unexpected communication error occurred between the SWA servlet and the Scalix Server resulting in the failure of the previous action"); and Google searches implied that I ran sx_clearimap, to clear my IMAP cache.

This worked, but since then I can no longer log into the SAC area. I have a feeling that sx_clearimap has screwed something up but I'm not sure what!

I have also investigated my scalix-caa.log file, but there are no references to the error, oddly.

Forum searches for the "Could not fetch server list" error produces many results, some solutions being 'uninstall and re-install'! This is obviously a drastic measure, and if this was live certainly wouldn't be an option. Other solutions seem extremely involving, as though the result of a major change (ie: server upgrade), so I have been reluctant to follow them, potentially causing more damage. I am expecting the reason for my "Could not fetch server list" issue to be more straight forward.

My /etc/opt/scalix/instance.cfg looks fine.

Can anyone offer any advice which may help dougsanfu or myself?

Hmm ok, I found simply rebooting the Scalix box appeared to correct my issue. Won't be the solution for a production environment, but it may be worth noting for now.

And scratch that! It allowed me to login once, but exiting the browser, then attempting to login again produces the same "Could not fetch server list" result! Grrrrr!

Have you solved the problem? I got the same problem since few days...and no post i found works fine...

I have the same problem ;it says "Cannot fetch configuration information..." when logging into SAC with sxadmin and the correct passwort.

Additional info: After rebooting the server, I can log into SAC without problems. When trying again about an hour later I'm getting the above error again.

Can anyone confirm this? Did anyone find a solution for this??

Thanks & Regards,
Devendra

I am having the same problem and didn't find a solution yet. Except for restarting Scalix but that is not a real solution.

I did however update the CentOS 5.3 server this morning. From that moment I find these errors, maybe they are related:

Check which updates were installed:


Check Scalix logs:


What else can I do to troubleshoot the problem? Is it only the SAC module that is having problems, or should I also have to worry about service outages for my users?

@ Devendra: are you also using redhat or centos 5 and did you update your system before the erros started?

Regards,
Joost.

Hi dougsanfu,

Did you ever find a solution to this problem?

Hey there,

i found a solution for

Could not login
Could not fetch server list

you need to edit the following line in your "ubermanager.properties"

# The IP address or hostname on which the notification listener will listen for
RES heartbeats and events.
# Commenting out, or using the value '*', means to listen on all addresses.
ubermanager.notification.listener.address=127.0.0.2 <----- BEFORE
#ubermanager.notification.listener.address=127.0.0.2 <----- BEFORE

After i commented this line everything is working fine.

Hope that helps

Ups there is a little typing mistake


# The IP address or hostname on which the notification listener will listen for
RES heartbeats and events.
# Commenting out, or using the value '*', means to listen on all addresses.

ubermanager.notification.listener.address=127.0.0.2 <----- BEFORE

#ubermanager.notification.listener.address=127.0.0.2 <----- AFTER