Page 1 of 1

New Instlation

Posted: Mon Jun 05, 2006 1:38 pm
by instabin
I just installed suse oss 10.0

Downloaed scalix and started installing...
Installed all required dependencs.

Finished installation of scalix...

Tryed to open admin web site at end of install. Request was rejected... (Browerser error)

Posted: Mon Jun 05, 2006 2:14 pm
by ScalixSupport
Could you give some more details. What you've provided so far gives us nothing to work with.

Cheers

Dave

Posted: Mon Jun 05, 2006 2:24 pm
by instabin
What kind of details...
Are there some log files that I could post, if so where are they located.

Posted: Mon Jun 05, 2006 4:30 pm
by instabin
This is the only thing i could find with errors in it.

mod_jk.log
------------------------------------------------------------------
[Thu Jun 01 14:53:27 2006] [error] init_jk::mod_jk.c (2356): Initializing shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:27 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:27 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:27 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:27 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:27 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:53:53 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:53:53 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:53:53 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:53:53 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1
[Thu Jun 01 14:53:53 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:53:53 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:53:53 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:53:53 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=2
[Thu Jun 01 14:53:53 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:53:53 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:53:53 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:53:53 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=3
[Thu Jun 01 14:53:53 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 Jun 01 14:53:53 2006] worker1 suselinux.fultonprecision.local 0.001002

[Thu Jun 01 14:53:53 2006] [info] jk_handler::mod_jk.c (1971): Service error=0 for worker=worker1
[Thu Jun 01 14:53:53 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2
[Thu Jun 01 14:54:06 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:54:06 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:54:06 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:54:06 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1
[Thu Jun 01 14:54:06 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:54:06 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:54:06 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:54:06 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=2
[Thu Jun 01 14:54:06 2006] [info] jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=111
[Thu Jun 01 14:54:06 2006] [info] ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=111)
[Thu Jun 01 14:54:06 2006] [info] ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Thu Jun 01 14:54:06 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=3
[Thu Jun 01 14:54:06 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 Jun 01 14:54:06 2006] worker1 192.168.0.11 0.001053

[Thu Jun 01 14:54:06 2006] [info] jk_handler::mod_jk.c (1971): Service error=0 for worker=worker1
[Thu Jun 01 14:54:06 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/srv/www/logs/jk-runtime-status errno=2

Posted: Mon Jun 05, 2006 5:00 pm
by ScalixSupport
Have you disabled selinux in /etc/sysconfig/selinux ?

Cheers

Dave

Posted: Tue Jun 06, 2006 5:59 am
by instabin
I do not have that file or folder...

/etc/sysconfig/selinux

Posted: Tue Jun 06, 2006 6:02 am
by ScalixSupport
Is Tomcat running?

ps -ef | grep java

please post the output.

Is this Suse 10.0 or 10.1 ? If the latter, you need to disable Apparmor.

Cheers,

Sascha.

Posted: Tue Jun 06, 2006 6:04 am
by instabin
suselinux:~ # ps -ef | grep java
root 4558 1 0 Jun01 ? 00:00:44 /usr/java/jre1.5.0_04/bin/java -server -Djava.net.preferIPv4Stack=true -Xms128m -Xmx128m -Djava.endorsed.dirs=/opt/scalix-tomcat/common/endorsed -classpath /usr/java/jre1.5.0_04/lib/tools.jar:/opt/scalix-tomcat/bin/bootstrap.jar:/opt/scalix-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/opt/scalix-tomcat -Dcatalina.home=/opt/scalix-tomcat -Djava.io.tmpdir=/opt/scalix-tomcat/temp org.apache.catalina.startup.Bootstrap start
root 26516 26503 0 07:58 pts/0 00:00:00 grep java


Also it is 10.0

Posted: Tue Jun 06, 2006 8:26 am
by ScalixSupport
ok, could you

vat /etc/hosts

please as well.

Also

lsof -i tcp:8009

Posted: Tue Jun 06, 2006 8:30 am
by instabin
127.0.0.1 localhost

# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.0.11 suselinux.fultonprecision.local suselinux

Posted: Tue Jun 06, 2006 10:31 am
by instabin
Do i have to reconfigure apache after the instlation?

Or does the instlation do that for me?

Posted: Tue Jun 06, 2006 5:17 pm
by instabin
I ended up installing fedora 4 and reinstalling scalix

Now it works perfect

Just for future reference

Posted: Mon Aug 13, 2007 8:12 pm
by deyjvu
I had to change a server name from just the hostname to the FQDN and followed the steps in the HOWTO on the Wiki for changing the server name, restarting apache and tomcat but could not get beyond this error.

In the end I uninstalled all parts of Scalix except the core server module and most particularly the Apache-Tomcat Connector and Tomcat were part of the uninstall. Reinstalled them all making sure the servername was correct, did not remove anything like caches etc when asked. Restarted everything and after that no more errno 111.

In case anyone else is faced with this issue, thought this might be of assistance.