Scalix Forums

Posted: **Mon Mar 05, 2007 1:00 pm**

Hi there,

I just installed scalix 11.0.2.
Since I got several problems with my last installation I thought I may try out the new version.

Still the same problem tomcat is not listening on 8009.
I get error 503 on apache 2.2.4

Is there a way to figure out why it is not listening on 8009?
Or some other suggestions?

Cheers Michael

Posted: **Tue Mar 06, 2007 2:12 am**

Hi!

Is there any other application that uses port 8009. Can you check if any other tomcat that is
running on the server apart from Scalix Tomcat? Please reply to me with the result of the
command "ps ax | grep tomcat". Also can you please check the catalina logs that you could
find at /var/opt/scalix/s4/tomcat/logs.

Thanks,
Subir

Posted: **Tue Mar 06, 2007 3:37 pm**

Hi there,

ps aux | grep tomcat

Code: Select all

michaels-place:/home/loginuser # ps ax | grep tomcat
32401 ?        Sl     0:10 /usr/lib64/jvm/java/jre/bin/java -server -Djava.net.preferIPv4Stack=true -Dscalix.instance=/var/opt/scalix/me -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/var/opt/scalix/me/tomcat/conf/logging.properties -Djava.endorsed.dirs=/opt/scalix-tomcat/common/endorsed -classpath /usr/lib64/jvm/java/jre/lib/tools.jar:/opt/scalix-tomcat/bin/bootstrap.jar:/opt/scalix-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/var/opt/scalix/me/tomcat -Dcatalina.home=/opt/scalix-tomcat -Djava.io.tmpdir=/var/opt/scalix/me/tomcat/temp org.apache.catalina.startup.Bootstrap start
11893 pts/0    R+     0:00 grep tomcat

catalina.2007-03-05.log

Code: Select all

05.03.2007 22:05:39 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.p
ath: /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64/server:/usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64:/usr
/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/../lib/amd64
05.03.2007 22:05:39 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1328 ms
05.03.2007 22:05:39 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
05.03.2007 22:05:39 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.16
05.03.2007 22:05:39 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
05.03.2007 22:13:25 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.p
ath: /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64/server:/usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64:/usr
/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/../lib/amd64
05.03.2007 22:13:25 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1523 ms
05.03.2007 22:13:25 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
05.03.2007 22:13:25 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.16
05.03.2007 22:13:25 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled

catalina.out

Code: Select all

05.03.2007 22:13:25 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.p
ath: /usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64/server:/usr/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/lib/amd64:/usr
/lib64/jvm/java-1.5.0-sun-1.5.0_update10/jre/../lib/amd64
05.03.2007 22:13:25 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1523 ms
05.03.2007 22:13:25 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
05.03.2007 22:13:25 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.16
05.03.2007 22:13:25 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
RES: Initializing log4j using file /var/opt/scalix/me/res/config/log4j.properties
SIS received contextInitialized event
SIS initialized with config from /var/opt/scalix/me/sis/sis.properties

lsof -i :8009

Code: Select all

michaels-place:/var/opt/scalix/me/tomcat/logs # lsof -i:8009
michaels-place:/var/opt/scalix/me/tomcat/logs #

Cheers Michael

Posted: **Wed Mar 07, 2007 2:23 pm**

Subir,

Are there any informations you need as well to help me out?

Regards

Michael

Posted: **Thu Mar 08, 2007 1:31 am**

Hi Michael,

Please check the page below:
http://www.scalix.com/wiki/index.php?title=HowTos/ApacheConfiguration

See if the configurations on your server match the requirements.

Thanks,
Subir

Posted: **Thu Mar 08, 2007 4:42 pm**

Everythings seems to be setup right.

Regards

Michael

Posted: **Fri Mar 09, 2007 11:36 am**

Hi,

The configuration is alright. Can it be a problem with the 64bit version of openSuSE10.1?

Regards

Michael

Posted: **Fri Mar 09, 2007 3:49 pm**

If I want to use mod_jk do I have to change anything else then the scalix-tomcat-connector.conf?
I get the following error message in mod_jk.log

Code: Select all

[Fri Mar 09 20:48:06 2007] [28015:23600] [info]  jk_handler::mod_jk.c (2150): Could not find a worker for worker name=my-domain

my workers.conf

Code: Select all

JkWorkerProperty worker.list=my-domain

my instance*.conf

Code: Select all

<VirtualHost my-domain.info:80>
    Include /etc/opt/scalix-tomcat/connector/jk/app-my-domain.*.conf
</VirtualHost>
JkWorkerProperty worker.my-domain.type=ajp13
JkWorkerProperty worker.my-domain.host=my-domain.info
JkWorkerProperty worker.my-domain.port=8009
JkWorkerProperty worker.my-domain.lbfactor=50
JkWorkerProperty worker.my-domain.cachesize=10
JkWorkerProperty worker.my-domain.cache_timeout=600
JkWorkerProperty worker.my-domain.socket_keepalive=1
JkWorkerProperty worker.my-domain.recycle_timeout=300

Just checked lsof -i :8009

Code: Select all

michaels-place:/etc/opt/scalix-tomcat/connector/jk # lsof -i :8009
michaels-place:/etc/opt/scalix-tomcat/connector/jk #

Still nothing, yes I restarted tomcat

How can I trace why tomcat is not listening on 8009?
I mean where it stucks.

Regards

Michael

Posted: **Mon Mar 12, 2007 4:14 am**

Hi Michael,

I don't really think 64 bit server could be a problem. Can you reply to me with the contents of
the file /etc/httpd/conf.d/scalix-tomcat-connector.conf that are non-commented lines.

Also can you send the result of the command "ls -al /etc/opt/scalix-tomcat/connector/jk/".

Thanks,
Subir

Posted: **Wed Mar 14, 2007 12:08 pm**

I have changed everything to ajp again 'cause mod_jk didn't work for me.

scalix-tomcat-connector.conf

Code: Select all

<Location />
  AddOutputFilterByType DEFLATE text/xml text/html text/css
  AddOutputFilterByType DEFLATE application/x-javascript
</Location>


<IfModule mod_proxy_ajp.c>

Include /etc/opt/scalix-tomcat/connector/ajp/instance-*.conf

</IfModule>

When I tried to use mod_jk the lines below looked like:

Code: Select all

<Location />
  AddOutputFilterByType DEFLATE text/xml text/html text/css
  AddOutputFilterByType DEFLATE application/x-javascript
</Location>


<IfModule mod_jk.c>

Include /etc/opt/scalix-tomcat/connector/jk/instance-*.conf

</IfModule>

ls -al /etc/opt/scalix-tomcat/connector/jk/

Code: Select all

michaels-place:/home/loginuser # ls -al /etc/opt/scalix-tomcat/connector/jk/
insgesamt 36
drwxr-xr-x 2 root root 464 2007-03-09 21:02 .
drwxr-xr-x 4 root root  96 2007-03-09 15:39 ..
-rw-r--r-- 1 root root  29 2007-03-09 15:45 app-michaels-place.api.conf
-rw-r--r-- 1 root root  29 2007-03-09 15:45 app-michaels-place.caa.conf
-rw-r--r-- 1 root root  27 2007-03-09 15:45 app-michaels-place.m.conf
-rw-r--r-- 1 root root  29 2007-03-09 15:45 app-michaels-place.res.conf
-rw-r--r-- 1 root root  29 2007-03-09 15:45 app-michaels-place.sac.conf
-rw-r--r-- 1 root root  29 2007-03-09 15:45 app-michaels-place.sis.conf
-rw-r--r-- 1 root root  33 2007-03-09 15:45 app-michaels-place.webmail.conf
-rw-r--r-- 1 root root 567 2007-03-09 15:45 instance-michaels-place.conf
-rw-r--r-- 1 root root  44 2007-03-09 15:45 workers.conf

ls -al /etc/opt/scalix-tomcat/connector/ajp/

Code: Select all

michaels-place:/home/loginuser # ls -al /etc/opt/scalix-tomcat/connector/ajp/
insgesamt 32
drwxr-xr-x 2 root root 432 2007-03-09 21:01 .
drwxr-xr-x 4 root root  96 2007-03-09 15:39 ..
-rw-r--r-- 1 root root  50 2007-03-09 15:45 app-michaels-place.api.conf
-rw-r--r-- 1 root root  50 2007-03-09 15:45 app-michaels-place.caa.conf
-rw-r--r-- 1 root root  46 2007-03-09 15:45 app-michaels-place.m.conf
-rw-r--r-- 1 root root  50 2007-03-09 15:45 app-michaels-place.res.conf
-rw-r--r-- 1 root root  50 2007-03-09 15:45 app-michaels-place.sac.conf
-rw-r--r-- 1 root root  50 2007-03-09 15:45 app-michaels-place.sis.conf
-rw-r--r-- 1 root root  58 2007-03-09 15:45 app-michaels-place.webmail.conf
-rw-r--r-- 1 root root 127 2007-03-09 15:45 instance-michaels-place.conf

Regards Michael

Posted: **Thu Mar 15, 2007 6:31 am**

Hi Michael!

In the workers.conf file you posted earlier value for worker.list is as below:

JkWorkerProperty worker.list=my-domain

the file names in the folder ajp and jk under /etc/opt/scalix-tomcat/connector folders
should have been named app-my-domain.*.conf instead of what the files are currently
being named as app-michaels-place.*.conf.

Why don't you run the scalix-installer and re-configure the following components:
scalix-tomcat-5.5.16-195
scalix-tomcat-connector-11.0.0.181-1.rhel4

Thanks,
Subir

Posted: **Thu Mar 15, 2007 4:10 pm**

I just replaced everything with my-domain in the thread in reality it is

Code: Select all

JkWorkerProperty worker.list=michaels-place

Sorry for that

Posted: **Fri Mar 16, 2007 1:06 am**

Hi Michael!

I understand you tried to use ajp, however when I saw my scalix-tomcat-connector.conf file the JK settings were as below:

Code: Select all

# 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"
 
Include /etc/opt/scalix-tomcat/connector/jk/instance-*.conf
Include /etc/opt/scalix-tomcat/connector/jk/workers.conf
 
</IfModule>
 
# ---------------------------------------------------------------------------
# mod_jk connector configuration (part specific to RedHat)
# ---------------------------------------------------------------------------
 
<IfModule mod_jk.c>
# Where to put jk logs
# Update this path to match your logs directory location
# (put mod_jk.log next to access_log)
JkLogFile     /var/log/httpd/mod_jk.log
</IfModule>

You can also have a look at the link below:
http://www.scalix.com/wiki/index.php?ti ... Tos/Apache

Thanks,
Subir

Posted: **Sun Mar 18, 2007 6:00 am**

Hu Subir,

tried out to configure it with the help of the HowTo.
Still get the Error 503.

Is it possible to select mod_jk when I install it?

Regards

Michael

Posted: **Tue Mar 20, 2007 12:57 am**

Hi!

By default mod_jk is used.

Subir

Scalix Forums

Tomcat problem on openSuSE 10.1

Tomcat problem on openSuSE 10.1