Page 1 of 1
FATAL [RESServiceHandler.GetMailNode
Posted: Thu Mar 16, 2006 11:22 am
by rudi
Hi,
I can't login into sac. When I start scalix-tomcat, I get the follwing FATAL Error in caa.log:
2006-03-16 16:16:23,802 FATAL [RESServiceHandler.GetMailNodesList:827] java.net.ConnectException: Connection refused:server.domain.com
I have read all community postings about "Can't login into sac", but nothing helps. The Scalix Version is 10.0.0.354.
Thanks for help!!
Posted: Thu Mar 16, 2006 12:14 pm
by santo
Seems like this is becoming a popular problem.
see
http://www.scalix.com/community/viewtopic.php?p=7935
Are you also running Scalix v10 ?
On which platform ?
Maybe it's a SUSE only problem...
Posted: Thu Mar 16, 2006 12:16 pm
by rudi
Yes, I run SuSE SLES 9 and the new Scalix 10 Version.
Please help ...
Posted: Thu Mar 16, 2006 2:10 pm
by rudi
Here is the caa log file:
2006-03-16 19:07:11,430 INFO [RESInitializer.terminate:250] Shutting down UberManager and all its threads...
2006-03-16 19:07:11,431 INFO [RESMonitor.halt:157] RESMonitor-thread Thread shutting down
2006-03-16 19:07:11,432 INFO [NotificationEventListener.cleanup:267] NotificationEventListener-Thread closing UDP socket...
2006-03-16 19:07:11,433 INFO [NotificationEventListener$WorkerThread.halt:119] com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-0 Thread shutting down...
2006-03-16 19:07:11,434 ERROR [NotificationEventListener.run:232] java.net.SocketException: Socket closed
2006-03-16 19:07:11,434 INFO [NotificationEventListener$WorkerThread.halt:119] com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-1 Thread shutting down...
2006-03-16 19:07:11,436 INFO [GuidToServerCache$CleanupThread.stopThread:54] com.scalix.sac.ubermgr.data.GuidToServerCache$CleanupThread-thread Shutting down...
2006-03-16 19:07:15,002 INFO [SOAPDispatcherServlet.init:76] ====> CAA is starting up, standby <====
2006-03-16 19:07:15,044 WARN [CAAConfigLoader.parseConfigDocument:224] No services are configured in this config file
2006-03-16 19:07:15,049 ERROR [CAAConfigLoader.parseComponentNode:244] Service scalix.res, Component disabled has no class defined!
2006-03-16 19:07:15,088 INFO [GuidToServerCache$CleanupThread.run:39] Guid2Server cache is empty. Skipping cleanup
2006-03-16 19:07:15,098 INFO [NotificationEventListener.launch:242] Main Notification Event Listener thread launched...
2006-03-16 19:07:15,100 INFO [NotificationEventListener.launch:245] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-0 launched...
2006-03-16 19:07:15,102 INFO [NotificationEventListener.launch:245] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-1 launched...
2006-03-16 19:07:15,106 INFO [RESInitializer.initNotificationListener:214] RESMonitor-thread Thread launched...
2006-03-16 19:07:15,117 INFO [SOAPDispatcherServlet.init:118] ====> CAA started, you may fire when ready <====
2006-03-16 19:07:15,374 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: register|http://leader.breitbanddienste.at/res/RESDispatcher|LISTEN|300|leader|leader.breitbanddienste.at|10.0.0 from host:leader.breitbanddienste.at
2006-03-16 19:07:20,380 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: register|http://leader.breitbanddienste.at/res/RESDispatcher|LISTEN|300|leader|leader.breitbanddienste.at|10.0.0 from host:leader.breitbanddienste.at
2006-03-16 19:07:25,385 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://leader.breitbanddienste.at/res/RESDispatcher|LISTEN|300|leader|leader.breitbanddienste.at|10.0.0 from host:leader.breitbanddienste.at
2006-03-16 19:07:46,343 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-16 19:07:46,344 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host leader.breitbanddienste.at
2006-03-16 19:07:46,345 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-16 19:07:46,346 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host leader.breitbanddienste.at
2006-03-16 19:07:46,347 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-16 19:07:46,348 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host leader.breitbanddienste.at
2006-03-16 19:07:46,349 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-16 19:07:46,349 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host leader.breitbanddienste.at
Posted: Fri Mar 17, 2006 5:03 am
by ScalixSupport
Hi,
please post output of
cat /etc/hosts
here.
Cheers,
Sascha.
Posted: Fri Mar 17, 2006 5:05 am
by rudi
Hi,
thanks for your answer. I have found the problem. The port 80 was not reachable to connect RES.
Best Regards!
Posted: Fri Mar 17, 2006 11:13 am
by santo
So how did you solve it ?
How did you make the port reachable ?
Posted: Fri Mar 17, 2006 3:17 pm
by AussieOwner
For future reference. You can glean some really good info from the heartbeat message in the caa.log file that you sent. For example, in the message:
2006-03-16 19:07:25,385 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://leader.breitbanddienste.at/res/RESDispatcher|LISTEN|300|leader|leader.breitbanddienste.at|10.0.0 from host:leader.breitbanddienste.at
This message contains the URL that SAC wil use to contact RES. This url in this message is: http://leader.breitbanddienste.at/res/RESDispatcher
Paste this into a browser and try to connect. If you cant connect to it, then neither can SAC. The problem will be on the RES side.
Posted: Mon Mar 20, 2006 4:57 am
by santo
Ok, I understand that, but how can it be fixed ?
What do I have to change in what file ?
Or is it a permissions problem ?
That's not clear to me
Posted: Mon Mar 20, 2006 5:32 am
by rudi
Configure Apache2, to listen on port 80. Thats all.
Posted: Mon Mar 20, 2006 7:14 am
by santo
Thanks, now I understand it ;-)
Unfortunately, the problem is I have to run apache on another port than 80 :-(
and that's probably the reason why it isn't working: I changed the port of apache right after installation
Posted: Mon Mar 20, 2006 7:27 am
by ScalixSupport
Hi,
can you be more specific as to what is not working?
Cheers,
Sascha.
Posted: Mon Mar 20, 2006 8:58 am
by santo
The problem is that I cannot login to the admin console.
The error I get is:
Code: Select all
Could Not Login
Could not fetch configuration information
Possible problem with administration server
On the server side I see this in the caa.log logfile:
Code: Select all
2006-03-20 13:52:46,731 INFO [RESMonitor.run:115] Server vmsrv-scalix.mydomain.com up 3 hrs, 43 mins, 57 secs
2006-03-20 13:52:54,146 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://vmsrv-scalix.mydomain.com/res/RESDispatcher|LISTEN|300|vmsrv-scalix|vmsrv-scalix.mydomain.com|10.0.0 from host:vmsrv-scalix.mydomain.com
2006-03-20 13:52:54,954 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:54,958 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:54,965 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:54,967 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:54,970 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:54,974 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:54,980 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:54,982 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:55,032 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:55,034 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:55,042 WARN [GetServerNameGenerationRules.createSOAPResponseMessage:102] Skipping server vmsrv-scalix.mydomain.com no document received.
2006-03-20 13:52:55,092 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:55,094 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:55,102 WARN [GetServerMailAddressGenerationRules.createSOAPResponseMessage:96] Skipping server vmsrv-scalix.mydomain.com no document received.
2006-03-20 13:52:55,156 FATAL [RESServiceHandler.executeRESCommand:1819] java.net.ConnectException: Connection refused
2006-03-20 13:52:55,160 FATAL [RESServiceHandler.executeRESCommand:1824] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host vmsrv-scalix.mydomain.com
2006-03-20 13:52:55,169 WARN [GetPasswordSettings.createSOAPResponseMessage:108] Skipping server vmsrv-scalix.mydomain.com no document received.
2006-03-20 13:52:55,227 FATAL [RESServiceHandler.GetMailNodesList:827] java.net.ConnectException: Connection refused:vmsrv-scalix.mydomain.com
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at com.scalix.sac.ubermgr.caa.RESConnection.sendMessage(RESConnection.java:99)
at com.scalix.sac.ubermgr.util.ConnectionHelperUtils.sendAndReceiveMessage(ConnectionHelperUtils.java:165)
at com.scalix.sac.ubermgr.res.RESServiceHandler.GetMailNodesList(RESServiceHandler.java:810)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.scalix.sac.ubermgr.caa.RESService.doRequest(RESService.java:109)
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.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
2006-03-20 13:52:55,232 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server vmsrv-scalix.mydomain.com. No document received!
As it turns out according to this thread, the problem is that SAC cannot connect to RES.
The solution should be to change the listening port of Apache to port 80.
But that's the problem: I can't run apache on port 80.
So I think the solution would be to tell SAC that it needs to connect on port 8080 instead of port 80.
But how do I do that ?
Posted: Thu Apr 27, 2006 3:20 am
by santo
any help on this one please ?
Posted: Fri Apr 28, 2006 6:38 am
by santo
I fixed it by setting the tcp port in res.properties ad explained in
http://www.scalix.com/community/viewtopic.php?t=2047