Postby kcwhited » Mon Jun 29, 2009 2:59 pm
I have a problem where SWA quits working. I have had the problem since I installed Scalix, I am running Centos 5.3 and have just upgraded to scalix 11.4.4 this problem existed in 11.4.3 before the upgrade.
I have 15 users and I am the only one that uses SWA. I also have two pcs that are connected to my mailbox, which may lead to the question does scalix have an issue with multiple concurent logins to one mailbox?
I am not sure if it is a multiple login problem because it does seem to happen whether or not my outlook is connected to scalix.
The problem can occur while I am logged into scalix SWA or after it just sits for a few days. If I am logged in it just stops responding and says it cannot connect the scalix server which isn't an internet related problem as I am on the local network. If it stops responding I simply close IE or FF and try to log back in and I am presented with a messages that states "Your Scalix server is temporarily unavilable. Please try again later." The only way I can regain control of Scalix is to restart the scalix service, the outlook / scalix connector continues to function properly. I can log into SAC but I cannot log into SWA with any user until I restart scalix.
When I restart scalix I do get a message that states
Stopping Scalix services (scalix): ***************** WARNING **************************
/opt/scalix/bin/omshut : Some UAL Interface processes are still running
after waiting for 300 seconds for their termination
To wait for a longer period run 'omshut -t <timeout>'.
***************** WARNING **************************
[ OK ]
Starting Scalix services (scalix): [ OK ]
After that everything will work for a day or three then I have to kick the service again. As far as I can tell there isn't anything consistent in the mailbox that can cause this problem, nor would I expect it too.
Does anyone have any ideas how I might kill this gremlin.
Currently I am only using scalix for my personal mail, but the intention of using it was to test before purchasing the enterprise version for the office. I certainly can't be restarting Scalix every other day if I were to deploy it in production. I know there has to be something that needs tweaked because certainly nobody else seems to be having a problem like this.
Here is my environment:
Windows server 2k8 sp2 with VMWARE SERVER 2.0.1
2x dual core opteron 2.0ghz
host 8gb ram
The scalix vm runs Centos 5.3 32bit with all yum updates. (tried the updates after I had this problem) - no joy
VM has 1536MB of ram and 50GB drive.
SCALIX 11.4.4
Last edited by kcwhited on Tue Jul 07, 2009 10:48 am, edited 1 time in total.