could not find resDispatcher

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

OliE
Posts: 14
Joined: Fri Sep 09, 2005 1:54 pm

could not find resDispatcher

Postby OliE » Wed Feb 15, 2006 4:27 pm

Hi,

I have a problem to login into sac after I upgrade to V10.
First I receive only a message that the pw was incorrent after I change the password for sxadmin with ommodu -o sxadmin -p newpw
than I get the error that scalix did not find resDispatcher.
Tomcat runs on port 8443 with ssl Support because port 80 and 8080 are reserved for my apache web server.
The log file looks for me that scalix want the resDipatcher on port 80 but there is my apache web server any hints how can I reolve the problem?

caa.log file

Code: Select all

2006-02-15 21:19:36,642 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,644 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,650 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,652 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,658 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,660 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,666 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,668 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,755 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,757 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,762  WARN [GetServerNameGenerationRules.createSOAPResponseMessage:102] Skipping server server.workgroup.de no document received.
2006-02-15 21:19:36,831 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,833 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,838  WARN [GetServerMailAddressGenerationRules.createSOAPResponseMessage:96] Skipping server server.workgroup.de no document received.
2006-02-15 21:19:36,884 FATAL [RESServiceHandler.executeRESCommand:1819] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
2006-02-15 21:19:36,886 FATAL [RESServiceHandler.executeRESCommand:1828] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-02-15 21:19:36,900  WARN [GetPasswordSettings.createSOAPResponseMessage:108] Skipping server server.workgroup.de no document received.
2006-02-15 21:19:36,948 FATAL [RESServiceHandler.GetMailNodesList:827] java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher:server.workgroup.de
java.io.FileNotFoundException: http://server.workgroup.de/res/RESDispatcher
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
        at java.net.URLConnection.getContent(Unknown Source)
        at com.scalix.sac.ubermgr.caa.RESConnection.receiveMessage(RESConnection.java:114)
        at com.scalix.sac.ubermgr.util.ConnectionHelperUtils.sendAndReceiveMessage(ConnectionHelperUtils.java:166)
        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.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-02-15 21:19:36,951 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server server.workgroup.de. No document received!
2006-02-15 21:19:48,959  INFO [RESMonitor.run:115] Server server.workgroup.de up 16 mins, 51 secs
2006-02-15 21:20:02,812  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://server.workgroup.de/res/RESDispatcher|LISTEN|300|server|server.workgroup.de|10.0.0 from host:server.workgroup.de


Best Regards,
Oli

crazy_russian

Postby crazy_russian » Wed Feb 15, 2006 8:35 pm

Hi,

Scalix installer now configures a new instance of tomcat under /opt/scalix-tomcat and enables mod_jk connector for apache. Please check the configuration in the /etc/opt/scalix/res/config/res.properties file to make sure that the port number specified there is set to 80.

If the port number is set to 80 please check the existence of scalix configuration files under the /etc/httpd/conf.d/ directory.

Hope that helps,
Yuri
Scalix Corp

OliE
Posts: 14
Joined: Fri Sep 09, 2005 1:54 pm

Postby OliE » Thu Feb 16, 2006 4:21 am

thx for you reply.
All apache config files located in /etc/httpd/conf.d the res.properties look like by me

Code: Select all

res.ubermanager.udp.port=3450
res.tomcat.tcp.port=

when I added port 80 to tcp.port then I get this error in /var/log/httpd/mod_jk.log

Code: Select all

[Thu Feb 16 09:12:09 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=2
[Thu Feb 16 09:12:09 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13
[Thu Feb 16 09:12:09 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13)
[Thu Feb 16 09:12:09 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Feb 16 09:12:09 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=3
[Thu Feb 16 09:12:09 2006] [error] ajp_service::jk_ajp_common.c (1758): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=worker1 failed
[Thu Feb 16 09:12:09 2006] worker1 server.workgroup.de 0.009152

[Thu Feb 16 09:12:09 2006] [info]  jk_handler::mod_jk.c (1971): Service error=0 for worker=worker1
[Thu Feb 16 09:12:09 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Thu Feb 16 09:12:10 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Thu Feb 16 09:12:10 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13


But tomcat listen on port 8009

Code: Select all

[root@server httpd]# netstat -l | grep 8009
tcp        0      0 localhost.localdomain:8009  *:*                         LISTEN


I have only uncomment the SSL Support out in /opt/scalix-tomcat/conf/server.xml by tomcat

Code: Select all

   <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->

    <Connector port="8443"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" debug="0" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />

    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
               address="127.0.0.1"
               enableLookups="false" redirectPort="8443" debug="0"
               protocol="AJP/1.3" />


Best Regards,
Oli

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Thu Feb 16, 2006 7:03 am

Hi,

what makes me wonder in general is, why

Thu Feb 16 09:12:09 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13
[Thu Feb 16 09:12:09 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13)

does not connect. Can you please telnet localhost 8009 and see if it accepts connections?

Also, please disable selinux for testing purposes. This requires a reboot.

Edit /etc/selinux/config and set SELINUX=permissive

Is this FC4?

Thanks,

Sascha.

OliE
Posts: 14
Joined: Fri Sep 09, 2005 1:54 pm

Postby OliE » Thu Feb 16, 2006 9:33 am

Yes on the server run FC4 and selinux blocks the connect so when I disable selinux than it works :)
But how must selinux configured with scalix?
Before I change it to permissive I see this in the audit.log file:

Code: Select all

type=AVC msg=audit(1140093080.904:890): avc:  denied  { name_connect } for  pid=12537 comm="httpd" dest=8009 scontext=root:system_r:httpd_t tcontext=system_u:object_r:port_t tclass=tcp_socket
type=SYSCALL msg=audit(1140093080.904:890): arch=40000003 syscall=102 success=no exit=-13 a0=3 a1=bffdd970 a2=71f93c a3=bffdda68 items=0 pid=12537 auid=501 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 comm="httpd" exe="/usr/sbin/httpd"
type=SOCKADDR msg=audit(1140093080.904:890): saddr=02001F497F0000010000000000000000
type=SOCKETCALL msg=audit(1140093080.904:890): nargs=3 a0=10 a1=99893d8 a2=10


Now no logs are added to audit.log but when I enable selinux than it will not work. I see also no webpages of scalix over port 80 when selinux is enabled only when I connect directly to port 8443.

Best Regards,
Oli

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Thu Feb 16, 2006 9:55 am

OliE wrote:Yes on the server run FC4 and selinux blocks the connect so when I disable selinux than it works :)


well, there you go, case closed. Disabling SELinux is also mentioned in the EXCELLENT INSTALLATION GUIDE that is a MUST READ.

;-)

Sascha.

OliE
Posts: 14
Joined: Fri Sep 09, 2005 1:54 pm

Postby OliE » Thu Feb 16, 2006 11:00 am

k thx for your help. :D
I found the setting I need to enable "Allow HTTPD scripts to connect to the network" I had this disabled now Scalix works fine the evolution connector also :)

Best Regards.
Oli


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 14 guests

cron