Strange Errors on Clean FC4 Install

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

burhankhalid
Posts: 137
Joined: Mon Dec 19, 2005 8:31 am

Strange Errors on Clean FC4 Install

Postby burhankhalid » Tue Mar 07, 2006 10:07 am

I am trying a variety of server configurations to see what kind of performance we can get. So I built a new server, with a clean 'minimum' install of FC4.

I only installed those dependencies that were required by scalix. Namely, Apache, elinks, and the libstd dependencies.

I installed Scalix 10, everything installed without a problem (no dependency/network errors). Using the bundled Tomcat and Java (since there is no java on the system).

When I run the system, everything seems to be running normally:

Code: Select all

[root@avalon ~]# ps -ef | grep httpd
root      6535     1  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6673  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6674  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6675  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6676  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6677  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6678  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6679  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
apache    6680  6535  0 16:33 ?        00:00:00 /usr/sbin/httpd
root      7290  7262  0 16:38 pts/0    00:00:00 grep httpd
[root@avalon ~]# ps -ef | grep tomcat
root      6686     1  3 16:33 tty1     00:00:12 /usr/java/jre1.5.0_04/bin/java -server -Djava.net.preferIPv4Stack=true -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      7296  7262  0 16:39 pts/0    00:00:00 grep tomcat


The default Apache page comes up when I access the server from another machine using both its domain name, and its IP address. However, both sac and webmail give 503 errors "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."

I did some trawling on the logs, and the following things stood out:

mod_jk.log this error keeps repeating

Code: Select all

[Tue Mar 07 16:08:50 2006] [error] init_jk::mod_jk.c (2356): Initializing shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:08:50 2006] [error] jk_child_init::mod_jk.c (2312): Attachning shm:/etc/httpd/logs/jk-runtime-status errno=13
[Tue Mar 07 16:09:24 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13
[Tue Mar 07 16:09:24 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13)
[Tue Mar 07 16:09:24 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Tue Mar 07 16:09:24 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=1
[Tue Mar 07 16:09:24 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13
[Tue Mar 07 16:09:24 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13)
[Tue Mar 07 16:09:24 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Tue Mar 07 16:09:24 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=2
[Tue Mar 07 16:09:24 2006] [info]  jk_open_socket::jk_connect.c (444): connect to 127.0.0.1:8009 failed with errno=13
[Tue Mar 07 16:09:24 2006] [info]  ajp_connect_to_endpoint::jk_ajp_common.c (889): Failed opening socket to (127.0.0.1:8009) with (errno=13)
[Tue Mar 07 16:09:24 2006] [info]  ajp_send_request::jk_ajp_common.c (1248): Error connecting to the Tomcat process.
[Tue Mar 07 16:09:24 2006] [info]  ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed,  recoverable operation attempt=3
[Tue Mar 07 16:09:24 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
[Tue Mar 07 16:09:24 2006] worker1 avalon.domain.com 0.001273


/opt/scalix-tomcat/logs/catalina.out

Code: Select all

Mar 7, 2006 4:33:43 PM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true
Mar 7, 2006 4:33:46 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/opt/scalix-tomcat/conf/Catalina/localhost/scalix-webcal.xml
reading configuration @ /etc/opt/scalix/webmail/swa.properties
Mar 7, 2006 4:33:47 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/opt/scalix-tomcat/conf/Catalina/localhost/scalix-caa.xml
Mar 7, 2006 4:33:47 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/opt/scalix-tomcat/webapps/caa/WEB-INF/lib/j2ee.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
CAA: caa-root-directory is /etc/opt/scalix/caa/
CAA: Loaded web.xml init params
CAA: caa-config-directory is /etc/opt/scalix/caa/config
CAA: log4j-init-file is /etc/opt/scalix/caa/config/log4j.properties
CAA: caa-framework-init-file is /etc/opt/scalix/caa/config/framework-config.xml
Mar 7, 2006 4:33:48 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/opt/scalix-tomcat/conf/Catalina/localhost/manager.xml
Mar 7, 2006 4:33:48 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/opt/scalix-tomcat/conf/Catalina/localhost/scalix-res.xml
RES: Initializing log4j using file /etc/opt/scalix/res/config/log4j.properties
Mar 7, 2006 4:33:49 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:/opt/scalix-tomcat/conf/Catalina/localhost/scalix-admin.xml
Mar 7, 2006 4:33:49 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL file:/opt/scalix-tomcat/webapps/jsp-examples
Mar 7, 2006 4:33:49 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tomcat-docs from URL file:/opt/scalix-tomcat/webapps/tomcat-docs
Mar 7, 2006 4:33:49 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL file:/opt/scalix-tomcat/webapps/servlets-examples
Mar 7, 2006 4:33:50 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path  from URL file:/opt/scalix-tomcat/webapps/ROOT
Mar 7, 2006 4:33:50 PM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL file:/opt/scalix-tomcat/webapps/webdav
Mar 7, 2006 4:33:50 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /127.0.0.1:8009


caa.log

Code: Select all

2006-03-07 16:33:48,112  INFO [SOAPDispatcherServlet.init:76] ====> CAA is starting up, standby <====
2006-03-07 16:33:48,236 ERROR [CAAConfigLoader.parseComponentNode:244] Service scalix.res, Component disabled has no class defined!
2006-03-07 16:33:48,262  WARN [CAAConfigLoader.parseConfigDocument:224] No services are configured in this config file
2006-03-07 16:33:48,343  INFO [GuidToServerCache$CleanupThread.run:39] Guid2Server cache is empty. Skipping cleanup
2006-03-07 16:33:48,344  INFO [NotificationEventListener.launch:242] Main Notification Event Listener thread launched...
2006-03-07 16:33:48,348  INFO [NotificationEventListener.launch:245] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-0 launched...
2006-03-07 16:33:48,350  INFO [NotificationEventListener.launch:245] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-1 launched...
2006-03-07 16:33:48,354  INFO [RESInitializer.initNotificationListener:214] RESMonitor-thread Thread launched...
2006-03-07 16:33:48,364  INFO [SOAPDispatcherServlet.init:118] ====> CAA started, you may fire when ready <====
2006-03-07 16:33:49,424  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: register|http://avalon.domain.com/res/RESDispatcher|LISTEN|300|avalon|avalon.domain.com|10.0.0 from host:avalon.domain.com
2006-03-07 16:33:54,433  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: register|http://avalon.domain.com/res/RESDispatcher|LISTEN|300|avalon|avalon.domain.com|10.0.0 from host:avalon.domain.com
2006-03-07 16:33:59,438  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://avalon.domain.com/res/RESDispatcher|LISTEN|300|avalon|avalon.domain.com|10.0.0 from host:avalon.domain.com
2006-03-07 16:34:48,362  INFO [RESMonitor.run:115] Server avalon.domain.com up 53 secs
2006-03-07 16:34:59,586  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://avalon.domain.com/res/RESDispatcher|LISTEN|300|avalon|avalon.domain.com|10.0.0 from host:avalon.domain.com
2006-03-07 16:35:44,878  INFO [SOAPDispatcherServlet.init:76] ====> CAA is starting up, standby <====
2006-03-07 16:35:44,908 ERROR [CAAConfigLoader.parseComponentNode:244] Service scalix.res, Component disabled has no class defined!
2006-03-07 16:35:44,933  WARN [CAAConfigLoader.parseConfigDocument:224] No services are configured in this config file
2006-03-07 16:35:45,017 FATAL [CAAInitializerManager.loadAllInitializers:58] Exception in initializer for scalix.res
java.net.BindException: Address already in use
[ trace follows ]


Kind of lost here as to what could be the problem. Any ideas? Right now I am running a system-wide update to see if that fixes any problems. I already tried the following:

1. Complete re-install (uninstall, reboot, re-install)
2. Shutdown iptables and try again
3. Manually stop/start Tomcat

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

Postby ScalixSupport » Tue Mar 07, 2006 11:22 am

mod_jk will typically talk to tomcat on port 8009 of the localhost address.

The error at the bottom of caa.log shows

Code: Select all

java.net.BindException: Address already in use


So, the first thing to do is

Code: Select all

lsof -i :8009

to see what might be listening on that port.

Cheers

Dave

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

Postby ScalixSupport » Tue Mar 07, 2006 11:26 am

And to add to what Dave said, please disable SELinux as stated in the release notes.

Cheers,

Sascha.

burhankhalid
Posts: 137
Joined: Mon Dec 19, 2005 8:31 am

Postby burhankhalid » Tue Mar 07, 2006 11:31 am

This doesn't look right, does it?

Code: Select all

[root@avalon ~]# lsof -i :8009
COMMAND  PID USER   FD   TYPE DEVICE SIZE NODE NAME
java    7912 root   22u  IPv4  41002       TCP localhost.localdomain:8009 (LISTEN)

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

Postby ScalixSupport » Tue Mar 07, 2006 11:34 am

It does look right if tomcat is started.

Sascha's comment about selinux is a valid one. After you have disabled selinux, reboot the box to start again and report the results.

Cheers

Dave

burhankhalid
Posts: 137
Joined: Mon Dec 19, 2005 8:31 am

Postby burhankhalid » Tue Mar 07, 2006 12:05 pm

Solved!

It was the SELinux problem. Can't believe I missed that step.

I would like to summarize what I did incase someone else wants to know what is the minimum requirements for running Scalix using FC4.

For those that would like to know how to setup a 'minimal' installation of Scalix on FC4, follow these steps:

Highly recommended

1. Proper DNS setup. You can run your own local DNS server if you like.
2. Static IP for your Scalix server

Steps to install:

Ensure minimum requirements as far as RAM is concerned
DISABLE SELINUX I forgot to do this at install time. By default, SELinux is enabled. You might also want to tick the boxes to enable passthrough for web (80) and SMTP (25) ports in the firewall configuration step. If you forget to disable SELinux, you can always disable it later by editing the /etc/sysconfig/selinux file and change the line SELINUX=enforcing to SELINUX=disabled. You will need to restart your system for the kernel to restart without SELinux.

1. Download and burn CD1 of the 4 CD iso pack
2. Reboot your system with the CD follow the steps but ensure that:
2a. You do not choose DHCP for your ethernet card. You need to set your static IP.
2b. You set the proper DNS information. You need to do this when you choose static IP. You should also enable the option to start the network at boot time
3. Follow the default partitioning scheme (as I did) or create your own partitions as you see fit.
4. Choose the minimum install
5. Click through, and follow the default install steps till you have rebooted your new system.

First Reboot

At the first reboot, you must login as root (that's the only user on the system). The first thing you should do is create a new standard user.

From the prompt, run:

# useradd -m -G users,wheel username
# passwd username

This will create a standard user account for you that has access to the 'wheel' group for su purposes.

Logout, then login with your standard user.

Before you can install Scalix, you must install a few packages to satisfy install requirements. These are:

Apache 2 yum install httpd
Elinks yum install elinks
compat-lib-stdc++-296 yum install compat-libstdc++-296

Run the above commands as root.

Download or copy over from the network the scalix installer archive.

Extract it:

$ tar -xzvf scalix-tab

Change to the scalix directory

$ cd scalix-tab

Run the installer as root ./scalix-installer

Follow the installer prompts (covered extensively elsewhere).

If everything goes as planned, you should have a working scalix server. Test it as per the administration guide.

Somethings to do post-install:

Enable httpd to run at boot time:

su -c '/sbin/chkconfig --level 345 httpd on'

That's it :D

jjj

No access beceaus of firewall...

Postby jjj » Thu Apr 13, 2006 8:22 am

burhankhalid; thanks! Great job.

small addition:

The firewall rules are still blokking port,80,21,110 and 143; so have a look at
http://www.scalix.com/community/viewtop ... c&start=15

--
Jeroen J.J. Eck
Amersfoort / The Netherlands

I e-mail therefore I am


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 11 guests