[Solved] Can't login to SAC after 11.4.4 upgrade

[nlindq]

I upgraded from 11.4.3 to 11.4.4 today, after which I receive the following when attempting to access the Administration Console:

Could Not Login
Could not fetch server list.
Possible problem with administration server

Any ideas?

[elliot01]

Just to report that we are in a similar boat.

Been testing Scalix 11.4.4.4904 on CentOS 5.3. All going well for about two weeks, then while continuing the test phase, importing users, trying some add-ons etc, suddenly start getting this same error.

What happens if you restart scalix-tomcat? On our system it will then allow us to login once. But not again until we restart the tomcat service again.

We have:
- Recreated sxqueryadmin
- Set scalix-caa.log and scalix-res.log to DEBUG level but seen nothing being reported which appears relevant.
- Inspected catalina.out log file - nothing relevant again.
- Ran omcheck numerous times.
- Disabled CentOS firewall
- Reconfigured each Scalix component separately.
- Uninstalled Scalix (retaining the message store) and reinstalled.
- Uninstalled Scalix (including the message store) and also manually dug out any Scalix-related files left behind, and deleted them. Then reinstalled from scratch - THE SAME PROBLEM! Only, the very first re-occurrence didn't appear until my third attempt at accessing SAC. Every tomcat restart after that is back to one successful login only before it dying.
- Followed numerous checks tips from this forum.

So far, we just can't get SAC back to fully working order

I have yet to receive any feedback via this forum. Fingers crossed someone will come along with some answers soon!

[nlindq]

Tried a restart of scalix-tomcat just to see, but I was unable to log in to the SAC even once.

[nlindq]

Okay, our SAC is working again. The issue seems to have been that we have multiple IP addresses on our Scalix server, but the /etc/hosts file only had the Scalix-configured hostname associated with one of the IPs. We added an additional entry for the other IP address and restarted; everything appears to be working fine now.