SAC logon denied. RES server not running?

Discuss installation of Scalix software

Moderators: ScalixSupport, admin

hkphooey
Posts: 70
Joined: Tue Aug 29, 2006 5:03 am

SAC logon denied. RES server not running?

Postby hkphooey » Mon Sep 04, 2006 9:42 pm

Sorry to join the Me Too club, but I can't log on to SAC after installing. Although many peole are having similar problems, none of the solutions I've tried have borne fruit. I posted this in the SAC forum a few days ago, but didn't get any answers, so I'm trying again here.

Here's the setup
- CentOS 4.3, installing Community edition via the Redhat installer script.
- CAN log on to /webmail immdiately after installation with admin id (which I changed from the default to pluto) and password specified in

- Checked Authentication ID with omshowu. If I login to /sac/ with anything which doesn't match the Authentication ID, I get the message about wrong username, please try with @domain.com. If I log in with the correct Authentication ID I get
"Could not Login. Could not fetch configuration information. Possible problem with administration server"

- Output of tail -f /opt/scalix-tomcat/logs/caa.log

Code: Select all

2006-08-31 05:38:02,107  INFO [RESMonitor.run:115] Server mail.blah.com up 1 hrs, 21 mins, 0 secs
2006-08-31 05:38:07,328  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.blah.com:8123/res/RESDispatcher|LISTEN|300|mail|mail.blah.com|10.0.1 from host:mail.blah.com
2006-08-31 05:39:02,109  INFO [RESMonitor.run:115] Server mail.blah.com up 1 hrs, 22 mins, 0 secs
2006-08-31 05:39:07,330  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.blah.com:8123/res/RESDispatcher|LISTEN|300|mail|mail.blah.com|10.0.1 from host:mail.blah.com
2006-08-31 05:40:02,111  INFO [RESMonitor.run:115] Server mail.blah.com up 1 hrs, 23 mins, 0 secs
2006-08-31 05:40:07,332  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.blah.com:8123/res/RESDispatcher|LISTEN|300|mail|mail.blah.com|10.0.1 from host:mail.blah.com
2006-08-31 05:40:28,058 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,059 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,061 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,063 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,064 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,065 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,066 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,067 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,268 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,269 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,272  WARN [GetServerNameGenerationRules.createSOAPResponseMessage:102] Skipping server mail.blah.com no document received.
2006-08-31 05:40:28,472 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,473 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,478  WARN [GetServerMailAddressGenerationRules.createSOAPResponseMessage:96] Skipping server mail.blah.com no document received.
2006-08-31 05:40:28,675 FATAL [RESServiceHandler.executeRESCommand:1844] java.net.ConnectException: Connection refused
2006-08-31 05:40:28,676 FATAL [RESServiceHandler.executeRESCommand:1849] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mail.blah.com
2006-08-31 05:40:28,678  WARN [GetPasswordSettings.createSOAPResponseMessage:108] Skipping server mail.blah.com no document received.
2006-08-31 05:40:28,875 FATAL [RESServiceHandler.GetMailNodesList:828] java.net.ConnectException: Connection refused:mail.blah.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:811)
        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.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(Unknown Source)
2006-08-31 05:40:28,877 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server mail.blah.com. No document received!

The important bit of this seems to be that the RES server refused the connection.

- When I go to /res/ I get a directory listing with one file in, scalix-res.xml

This doesn't seem right to me. Any ideas?

hkphooey
Posts: 70
Joined: Tue Aug 29, 2006 5:03 am

Postby hkphooey » Wed Sep 06, 2006 2:15 am

Damn, that took a while, but I figured it out eventually.

During installation, I chose a non-standard port for the RES server, as I was intending to use 8080 for a webserver. Somehow these changes weren't propagated everywhere they needed to be in the config files, so Scalix got confused at the SAC login point.

The eventual solution is this:

Edit

Code: Select all

 /etc/opt/scalix/res/config/res.properties

and set

Code: Select all

res.tomcat.tcp.port=8080

Restart Tomcat

Code: Select all

/etc/init.d/scalix-tomcat restart


Now I can log in. Hope this helps someone. It drove me crazy for almost a week.

iomari

Postby iomari » Wed Oct 11, 2006 11:04 am

Edit
Code:
/etc/opt/scalix/res/config/res.properties

and set
Code:
res.tomcat.tcp.port=8080

Restart Tomcat
Code:
/etc/init.d/scalix-tomcat restart


My port has alreay been configured corretly yet I'm still having the same message on login as you.

Could not login
Could not fetch configuration Information
Possible problen with administration server


Could anyone out there please help me.
Here is my log file:


2006-10-11 15:56:09,559 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,560 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,561 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,562 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,563 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,563 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,564 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,565 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,566 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,567 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,568 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,568 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,570 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,570 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,669 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,669 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,672 WARN [GetServerNameGenerationRules.createSOAPResponseMessage:102] Skipping server mymail.mailserver.com no document received.
2006-10-11 15:56:09,872 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,873 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,876 WARN [GetServerMailAddressGenerationRules.createSOAPResponseMessage:96] Skipping server mymail.mailserver.com no document received.
2006-10-11 15:56:09,985 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused
2006-10-11 15:56:09,986 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host mymail.mailserver.com
2006-10-11 15:56:09,989 WARN [GetPasswordSettings.createSOAPResponseMessage:108] Skipping server mymail.mailserver.com no document received.
2006-10-11 15:56:10,105 FATAL [RESServiceHandler.GetMailNodesList:965] java.net.ConnectException: Connection refused:mymail.mailserver.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:948)
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:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
2006-10-11 15:56:10,106 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server mymail.mailserver.com. No document received!
2006-10-11 15:56:17,427 INFO [RESMonitor.run:115] Server mymail.mailserver.com up 17 mins, 58 secs
2006-10-11 15:56:24,045 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mymail.mailserver.com:8080/res/RESDispatcher|LISTEN|300|mymail|mymail.mailserver.com|11.0.0 from host:mymail.mailserver.com



thanks in advance
iomari

joako
Posts: 308
Joined: Tue May 08, 2007 10:45 pm

Postby joako » Wed Jun 06, 2007 5:41 pm

Did you ever fix this? Where is the HOSTNAME config besides the port? Why are there SO MANY configuration files?

fb
Posts: 22
Joined: Sun Jul 01, 2007 10:45 am

Postby fb » Fri Jul 13, 2007 12:33 pm

YIPPIEEE, I finally found a solution for your problem.....!!

the thing is the following....

1st check if your have tomcat running on port 8080 as http-proxy! if NOT, then that's the trouble.

you should then edit /var/opt/scalix/_YOUR_SCALIX_CODE/tomcat/server.xml and UNcomment the part in CATALINA service config where it begins with:

Code: Select all

 <Connector port="8080"


UNCOMMENT this part, restart scalix-tomcat and HERE YOU GO!

ITCons

Not able to Login to the Administrator Console

Postby ITCons » Thu Feb 07, 2008 8:10 pm

Since Apache has to talk to AJP and Tomcat, when not able to login to the Scalix Admin Console errors can occur along those lines. :shock: So much for the general explanation.

In my case, I spent a few hours digging through to the holy grale, which was at the end found in the server.xml file. I add this post in hope it will be helpful to someone else crossing the same issue in future installs. I am so generous, I know...

It all comes down to the following directive in the server.xml configuration:

Code: Select all

   <Connector port="8009" address="localhost">
Last edited by ITCons on Mon Jan 04, 2010 6:34 am, edited 1 time in total.

jaydenrussell
Posts: 11
Joined: Thu Aug 06, 2009 2:34 pm

Re:

Postby jaydenrussell » Tue Dec 22, 2009 3:26 pm

iomari wrote:Edit
Code:
res.properties

and set
Code:
res.tomcat.tcp.port=8080

Restart Tomcat
Code:
/etc/init.d/scalix-tomcat restart


The upgrade to 11.4.6 must have overwritten this since it was blank. I can now access the SAC! now to figure out why the mobile does not login

ls-al
Scalix Star
Scalix Star
Posts: 510
Joined: Tue Jun 29, 2004 8:28 am
Location: Leipzig, Germany
Contact:

Re: SAC logon denied. RES server not running?

Postby ls-al » Wed Dec 23, 2009 5:19 am

Its probably a bad idea to use these old threads as a reference when trying to solve issues with the newest product.
The first versions of Scalix used Tomcat directly through port 8080. Starting with Scalix 10 this was not necessary anymore as the scalix-tomcat-connector integreated the webapps into the Apache config through mod_jk and later via ProxyPass/ajp.
With the introduction of the Scalix DAV services port 8080 is used by Tomcat again to serve the /api/dav ressource. The use of other webapps like SAC/CAA/RES trough port 8080 is most likely not tested and should be avoided.

jaydenrussell
Posts: 11
Joined: Thu Aug 06, 2009 2:34 pm

Re: SAC logon denied. RES server not running?

Postby jaydenrussell » Thu Dec 24, 2009 10:36 am

Well I have a support ticket in but the 4 hr response time has me looking for other ideas. Plus its 4hrs each time for response with no general help.

It could be true this is not a solution but it works in the interm for SAC access. Mobile seems not to work so this could be an API issue or postres.


Return to “Installation”



Who is online

Users browsing this forum: No registered users and 4 guests