Page 1 of 1

SAC issues after install

Posted: Tue Mar 15, 2011 11:48 am
by jdgiddings
Hello I just installed a Scalix server 11.x.x
The SAC was working just fine until I changed the server's local IP address and now it states:

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

It pops that error up very quickly after trying to login to the SAC.

Any help is much appreciated.

Re: SAC issues after install

Posted: Tue Mar 15, 2011 4:52 pm
by ls-al
Could you please have a look at the logs in /var/opt/scalix/??/tomcat/logs, especially scalix-caa.log and catalina.out and post the relevant entries?

Re: SAC issues after install

Posted: Tue Mar 15, 2011 4:53 pm
by jdgiddings
Thanks for the quick reply but I literally just figured it out and it's was the weirdest roundabout fix.

I logged into the sxadmin's webmail account (I wanted to see if I could log in at all with sxadmin's credentials) and it said it needed a new password due to expiration. I reset the password and it now works.
I can login to the SAC now.

Re: SAC issues after install

Posted: Tue Mar 15, 2011 5:18 pm
by ls-al
It turns out that this is a known issue.
The person who points to the corresponding improvement bug gets a recommendation for a "Scalix Star" ;-)

Re: SAC issues after install

Posted: Mon Mar 21, 2011 4:38 pm
by polleke
there are numerous improvemen (enh) bugs

this one is close and far enough

https://bugzilla.scalix.com/show_bug.cgi?id=18079

i spent a few hours reading bugs.. It was educational

Re: SAC issues after install

Posted: Mon Mar 21, 2011 4:47 pm
by ls-al
polleke wrote:there are numerous improvemen (enh) bugs

this one is close and far enough

https://bugzilla.scalix.com/show_bug.cgi?id=18079

i spent a few hours reading bugs.. It was educational


Its educational every time ;-)
But I thought of 18642.

Re: SAC issues after install

Posted: Tue Mar 22, 2011 7:02 am
by polleke
You sent me in the wrong direction. i was searching for enh bugs. ..

i have another trivial bug hopefully beating your admininistrator bug on most trivial bug

i found this in the wireless-activity.log
2011-03-22 12:01:29,142 INFO [PingCommand.execute:121] PING - deviceId:<DEVICEID>, user: <USER> ping was aborted for the the session