Several problems after upgrading 10->11.1

J.Hinz · Postby **J.Hinz** » Wed Sep 12, 2007 11:06 am

Hello,

I upgraded a Scalix 10.0.5 to Scalix 11.1 yesterday. The sytem was upgraded before from RHEL3 to RHEL5.

The installation procedure using ./scalix_installer --cli worked out without errors.

The configuration of the used ports is different from the default-configuration.

The Apache is running on Port 8080. The SSL-Version is on Port 8443.

Therefore the /etc/opt/scalix-tomcat/connector/ajp/instance-scalix.conf was configured that way:

<VirtualHost scalix.gruppe.de:8080>
Include /etc/opt/scalix-tomcat/connector/ajp/app-scalix.*.conf
</VirtualHost>

<VirtualHost scalix.gruppe.de:8443>
SSLEngine on

SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
SSLCertificateFile /etc/httpd/conf/ssl.crt/server.crt
SSLCertificateKeyFile /etc/httpd/conf/ssl.key/server.key
Include /etc/opt/scalix-tomcat/connector/ajp/app-scalix.*.conf
</VirtualHost>

Because the RES-tomcat-instance listens normally to port 8080, this fist changed in /opt/scalix/tomcat5/conf/server.xml the section

<Connector port="8081"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />

and set in /opt/scalix/var/sx/res/config/res.properties the line "res.tomcat.tcp.port=8081".

After that the SAC worked again.

When I just took a look at the server.xml I saw that my 8081-section is gone.

Than webmail and SAC worked.

But the mobile web client always reported "wrong username or password".

I when I set the loglevel to DEBUG, I noticed in the mobile.log that the process wanted to connect to port 80. Then I changed the URL in the file /var/opt/scalix/sx/mobile/mobile.properties:

# Copyright (C) 2006 Scalix Corporation. All rights reserved.

#
# URL of the Scalix Platform
#
platform.url=http://scalix.gruppe.de:8080/api

#
# maximum number of search results
#
search.maxresults=100

If you try to login now, nothing happens, the browser is waiting... after 1 or 2 minutes
the tomcat reports an timeout, the log reports:

2007-08-30 15:26:54,858 DEBUG [Init.contextInitialized:16] Received contextInitialized event
2007-08-30 15:26:54,872 DEBUG [Config.getInputStreamForFile:101] Reading config from /var/opt/scalix/sx/mobile/mobile.properties
2007-08-30 15:26:54,876 DEBUG [Config.load:78] done loading Scalix Mobile Web Client configuration (version 11.1.0.45)
2007-08-30 15:34:12,079 DEBUG [Connection.execute:106] <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Temporarily Unavailable</title>
</head><body>
<h1>Service Temporarily Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<hr>
<address>Apache/2.2.3 (Red Hat) Server at scalix.gruppe.de Port 8080</address>
</body></html>

All other logfiles report nothing from interest.

I wonder if http://scalix.gruppe.de:8080/api is the right platform.url? Because in the file /etc/opt/scalix-tomcat/connector/ajp/app-scalix.api.conf it says ProxyPass /api ajp://scalix.gruppe.de:8009/api, so the /api-URL is on port 8080.

I also reconfigured ALL scalix-componentes with the scalix-installer.

Since the update we have several problems with the system:

- Some users cannot create entries in public calenders although the user-specific rights are correct

- When opening the rules assistant in Outlook, some users get the Outlook-Rules-Assistant instead the Scalix Rule-Wizard

- When trying to open the Rules-Wizard in OWA, you generally get "The requested URL /Scalix/rw/prof=RW-GERMAN was not found on this server"

- The SWA is very instable. After some time it reports that the calender could not been loaded, and when opening messages in the message-window the "message is loading" remains forever... you can only close the SWA-window using the task-manager.

In the fatal-Log we see lots of these message:

SERIOUS ERROR Local Delivery(Local Delivery) Wed Sep 5 16:52:26 2007
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb3)[0x574ae3]
/opt/scalix/lib/libom_cvc.so(cvc_enhCnvString+0x122)[0x5bca2b]
/opt/scalix/lib/libom_cvc.so(cvc_ConvertString+0x6a)[0x5bd605]
/opt/scalix/lib/libom_rtfl.so(rtfl_BuildLine+0x4df)[0x2bc91f]
/opt/scalix/lib/libom_rtfl.so[0x2bf125]
/opt/scalix/lib/libom_rtfl.so(rtfl_Parse+0x173)[0x2c0c33]
/opt/scalix/lib/libom_rtfl.so(rtfl_search+0x130)[0x2be225]
/opt/scalix/lib/libom_flt.so[0x11c352]
/opt/scalix/lib/libom_flt.so(flt_ApplyTextMatch+0xfd)[0x11c4b2]
/opt/scalix/lib/libom_flt.so(Test_TextBody_Att+0x1f8)[0x119b9f]
/opt/scalix/lib/libom_flt.so(flt_ApplySingle+0x781)[0x11855d]
/opt/scalix/lib/libom_flt.so(flt_ApplyNextFilter+0x256)[0x1176ed]
/opt/scalix/lib/libom_flt.so(flt_ApplyOuterGroup+0xd5)[0x117319]
/opt/scalix/lib/libom_flt.so(flt_ApplyFC+0x15b)[0x116dd7]
local.delivery 44776800[0x8058000]
local.delivery 44776800[0x8052d8b]
local.delivery 44776800[0x805ce14]
local.delivery 44776800[0x805eeb3]
local.delivery 44776800[0x805fc53]
/lib/libc.so.6(__libc_start_main+0xdc)[0x746dec]
local.delivery 44776800[0x804cff1]
Pid of logging process: 20151
Last Msg Id: H000030600ecbee1.1189003936.scalix.gruppe.de

What causes all those problems?

Joerg

chris · Postby **chris** » Wed Sep 12, 2007 11:16 am

Hi JÃ¶rg,

the first thing I would recommend doing is standardizing your tomcat/apache/mod_jk configuration.

Compare to a vanilla 11.x system to see the recommended configuration.

The errors you're seeing in SWA are certainly not all related to the non-standard config, but I think it would be a good first step to get back to the recommended and supported configuration.

Chris

Scalix Forums

Several problems after upgrading 10->11.1

Several problems after upgrading 10->11.1

Who is online