Can't login to sac or webmail

[SeanMatula]

telnet localhost 8009
Trying 127.0.0.1...
Connected to localhost (127.0.0.1).
Escape character is '^]'.

where would scalix-jk-common.conf be located on a FC4 install?

Thanks for all your help

-Sean

[ScalixSupport]

Hi Sean,

On page 2 of this thread Dave posted the location (/etc/httpd/conf.d). You can also use the locate or find command to find any file on your system.

Thanks,
Rachel

[SeanMatula]

Code: Select all

#
# Scalix JK connector configuration
# (file common to all platforms)
#

# Setup JK connector needed to run Tomcat under Apache server:

<IfModule mod_jk.c>

# Set the jk log level [debug/error/info]
JkLogLevel          info
# Select the log format
JkLogStampFormat   "[%a %b %d %H:%M:%S %Y] "
# JkOptions indicate to send SSL KEY SIZE,
JkOptions          +ForwardKeySize +ForwardURICompat -ForwardDirectories
# JkRequestLogFormat set the request format
JkRequestLogFormat "%w %V %T"
# Send everything for context /examples to worker named worker1 (ajp13)
JkMount            /webmail* worker1
JkMount            /sac* worker1
JkMount            /caa* worker1
JkMount            /webcal* worker1
JkMount            /res* worker1

# workers.properties content:

# Define 1 real worker using ajp13
JkWorkerProperty worker.list=worker1
# Set properties for worker1 (ajp13)
JkWorkerProperty worker.worker1.type=ajp13
JkWorkerProperty worker.worker1.host=localhost
JkWorkerProperty worker.worker1.port=8009
JkWorkerProperty worker.worker1.lbfactor=50
JkWorkerProperty worker.worker1.cachesize=10
JkWorkerProperty worker.worker1.cache_timeout=600
JkWorkerProperty worker.worker1.socket_keepalive=1
JkWorkerProperty worker.worker1.reclycle_timeout=300

</IfModule>

[ScalixSupport]

Hi Sean,

That file looks good as well. So, back to my previous question, had you made any changes to your /etc/hosts or scalix-jk-common.conf file since you've restarted apache? You log is showing that Apache is trying to talk to Tomcat via your hosts IP rather than localhost -

[Sun Mar 19 19:02:57 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (192.168.1.2:8009) with (errno=111)

If you've made changes, then you need to restart apache. If you haven't any chnages can you check your mod_jk.log file again to see if it's still trying to connect to 192.168.1.2:8009 rather than 127.0.0.1:8009.

Thanks,
Rachel

[SeanMatula]

WOO HOO!

Restarting Apache worked. I did make a change to /etc/hosts, but guess I didn't restart after.

Thanks so much for your help.

Sean

[l8er]

... You also need to check /etc/hosts to make sure that you have nothing other than localhost.localdomain and localhost on the 127.0.0.1 line. ...

I've spent the last few days trying to get Scalix running on Fedora Core 4. I finally ran across this thread and the above hint got me up and running. The 127.0.0.1 line was missing entirely from /etc/hosts. After adding:
127.0.0.1 localhost.localdomain localhost
and restarting httpd, I'm up and running. Woo-hoo! Thanks.

-Gary

[ScalixSupport]

Any idea why this was the case ? Even when the FC installer puts the hostname on the 127.0.0.1 line, the information is still there.

Does this mean that you had edited the file to remove the line ?

Cheers

Dave

[l8er]

... Does this mean that you had edited the file to remove the line ? ...

If I removed it, it was not intentionally. The Scalix installer gave me an error about DNS and IP not matching under "Checking network", and my solution as to add 192.168.100.254 with my domain name in hosts. At that point 127.0.0.1 was there and I did not choose to delete it - but when Scalix finished installing and I searched for a solution - 127.0.0.1 was no longer in hosts.

-Gary

[drewnick]

Hello friends. We have this installed on Fedora Core 4.

The system will run fine for dayas and then suddenly

We get the error messages on the Web site (503) error messages. No one is logging in via SSH and changing anything. Rebooting the server fixes the problem for another few days. I caught it before it was rebooted and top showed low memory usage (50 MB out of 768 available).

Here's my mod_jk.log

Code: Select all

[Wed Jun 07 15:34:10 2006] [info]  jk_handler::mod_jk.c (1971): Service error=0 for worker=worker1
[Wed Jun 07 15:36:02 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Wed Jun 07 15:36:02 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Wed Jun 07 15:36:02 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Wed Jun 07 15:36:02 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=1
[Wed Jun 07 15:36:02 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Wed Jun 07 15:36:02 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Wed Jun 07 15:36:02 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Wed Jun 07 15:36:02 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=2
[Wed Jun 07 15:36:02 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Wed Jun 07 15:36:02 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Wed Jun 07 15:36:02 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Wed Jun 07 15:36:02 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=3
[Wed Jun 07 15:36:02 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


I wonder if anyone knows why 8009 would be failing on its own?