I'm going to revitalize an old problem of mine with a new post. This problem has been going on for a LONG time, and it is to the point where it is about to be a killer.
Basic situation is this:
Everything works fine, webmail works, SAC works, all is good in the world... when the server is freshly turned on etc. If you wait several hours, the SAC stops working and gives this error when you try to login to it:
Could Not Login
Could not fetch configuration information.
Possible problem with administration server
Note that the login information is correct and functional, because if you enter in the wrong login information it gives you a correct page that tells you that you have a wrong login ID/password. I am also only using http not https.
A temporary solution to this problem is to restart the scalix-tomcat service, at that point the SAC will be available for a few hours, but it will revert back to not working anymore. I have added the restarting of the service to my daily maintenance script that runs at 2am, but I can promise that the SAC will be locked out 100% of the time by noon, and probably 60-70% of the time by 10am.
After working through the problem in the forums etc, I managed to turn on debugging via changing the INFO to DEBUG in the file /var/opt/scalix/NN/caa/config/log4j.properties
After debugging was turned on, I was able to isolate an exact error message for my problem in the file /var/opt/scalix/NN/tomcat/logs/scalix-caa.log to be this error:
Code: Select all
2007-03-28 23:14:01,961 ERROR [GetServerNameGenerationRules.createSOAPResponseMessage:140] null
2007-03-28 23:14:02,356 ERROR [GetServerMailAddressGenerationRules.createSOAPResponseMessage:152] null
2007-03-28 23:14:02,825 ERROR [GetPasswordSettings.createSOAPResponseMessage:237] null
2007-03-28 23:14:03,216 ERROR [RESServiceHandler.GetMailNodesList:960] Server mail.mydomain.com terminated with status ERROR:514 - Exception -
2007-03-28 23:14:03,217 ERROR [GetMailNodesList.buildResponseMessage:104] Skipping server mail.mydomain.com. No document received!With this new set of error messages, I was able to find references to the same problems all the way back into the testing Release Candidates for Scalix 11.
To this point, this is the best that I have been able to accomplish. I have not yet been able to figure out any actual cause of the error, and I do not know of any proper solution. It has happened to me since the installation of this server, which involved porting over the old Scalix 10 data to the new server, then running the install for Scalix 11.0 which updated the data as it installed. This server was running CentOS 4.4 at the time, and is currently running CentOS 4.5. The old server was running Fedora 4, and never had this problem.
If anyone has any suggestions, PLEASE let me know...
Thank you!
Mito
