Problem logging into Management Services

[Lucas]

Hi,

I'm having a problem logging in to the management services with Scalix 11. You can read the full description here: http://www.scalix.com/community/viewtopic.php?t=5250 (it first appeared on RC2, but I've since upgraded to GA)

I'm wondering if this has something to do with the SIS URL. If I do an omshowu -n sxadmin, I get:

Code: Select all

SIS URL : sxidx://servername.com/05000000c3df5854-2.49.25.47


Since I had moved things to mail.servername.com, I executed:

Code: Select all

ommodu -n sxadmin -index sxidx://mail.servername.com/05000000c3df5854-2.49.25.47


But that did not help things.

This is what I have on /opt/scalix/global/config

Code: Select all

OMNAME=servername
OMHOSTNAME=mail.servername.com
OMDATADIR=/var/opt/scalix/as/s
OMAUTOSTART=TRUE


And this is what I have on the scalix-caa.log

Code: Select all

[root@servername s]# tail /var/opt/scalix/as/tomcat/logs/scalix-caa.log
2006-12-25 11:32:11,072  INFO [RESMonitor.run:115] Server servername.com up 19 hrs, 55 mins, 0 secs
2006-12-25 11:32:17,748  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://servername.com/res/RESDispatcher|LISTEN|300|servername|servername.com|11.0.0 from host:servername.com
2006-12-25 11:33:11,074  INFO [RESMonitor.run:115] Server servername.com up 19 hrs, 56 mins, 0 secs
2006-12-25 11:33:17,750  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://servername.com/res/RESDispatcher|LISTEN|300|servername|servername.com|11.0.0 from host:servername.com
2006-12-25 11:34:11,076  INFO [RESMonitor.run:115] Server servername.com up 19 hrs, 57 mins, 0 secs
2006-12-25 11:34:17,752  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://servername.com/res/RESDispatcher|LISTEN|300|servername|servername.com|11.0.0 from host:servername.com
2006-12-25 11:35:11,078  INFO [RESMonitor.run:115] Server servername.com up 19 hrs, 58 mins, 0 secs
2006-12-25 11:35:17,754  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://servername.com/res/RESDispatcher|LISTEN|300|servername|servername.com|11.0.0 from host:servername.com
2006-12-25 11:36:11,080  INFO [RESMonitor.run:115] Server servername.com up 19 hrs, 59 mins, 0 secs
2006-12-25 11:36:17,756  INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://servername.com/res/RESDispatcher|LISTEN|300|servername|servername.com|11.0.0 from host:servername.com


I'm sort of flying blind - can anyone point me to a documentation indicating where I should be looking at?

I noticed that this points to servername.com and not mail.servername.com - I imagine this might be related to the problem, but don't know if this is tomcat configuration of Scalix (I'm not experienced with Tomcat). Any pointers are welcome.

[Lucas]

Checking caa.log, I'v found the following when I attempt to access the SAC:

servername.com2006-12-31 14:15:31,577 FATAL [RESServiceHandler.executeRESCommand:2021] java.io.IOException: Server returned HTTP response code: 500 for URL: http://servername.com/res/RESDispatcher
2006-12-31 14:15:31,578 FATAL [RESServiceHandler.executeRESCommand:2030] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs
2006-12-31 14:15:31,600 FATAL [RESServiceHandler.executeRESCommand:2021] java.io.IOException: Server returned HTTP response code: 500 for URL: http://servername.com/res/RESDispatcher
2006-12-31 14:15:31,601 FATAL [RESServiceHandler.executeRESCommand:2030] com.scalix.sac.ubermgr.res.RESServiceHandler:Fatal Exception raised. Check the CAA logs


Clearly I need to modify the server for the RESDispatcher as well to be mail.servername.com, but I don't know where that's configured. Can anyone point me in the right direction?

[dannyt]

Hi,

It would appear the problem(s) may be caused by the incomplete procedures when moving (or renaming) the Scalix host. Have a read at the man page (man sxmodfqdn) and the related section in the Admin Guide for changing host FQDN to see if that helps.

You may have to rerun the installer and reconfigure the management services (scalix-sac and scalix-res) again afterwards to ensure that the correct config files are set up.

Regards,
Danny

[Lucas]

Thanks a whole lot for the pointer, Danny. sxmodfqdn didn't help, but running the installer and re-configuring the management services did the trick.