Problem to login SAC with FC5

Discuss Scalix Management Services ( formerly Scalix Admin Console )

Moderator: ScalixSupport

Phantasmagoria
Posts: 22
Joined: Tue Nov 15, 2005 4:29 am

Problem to login SAC with FC5

Postby Phantasmagoria » Sun Dec 24, 2006 2:06 pm

Just fresh install FC5 and Scalix 11...

When I use sxadmin to login it will display "Cannot fetch configuration information...", and I found error in logs file:

2006-12-25 02:04:58,157 FATAL [RESServiceHandler.executeRESCommand:2026] com.scalix.sac.ubermgr.res.RESServiceHandler:Connection refused: Failed to connect to RES on host xxx.domain.com
2006-12-25 02:04:58,159 FATAL [RESServiceHandler.executeRESCommand:2021] java.net.ConnectException: Connection refused

when I use sxadmin-xxx@domain.com to login it will display "You might have forgotten to include the domain name as part of your login ID...", and log error msg:


2006-12-25 02:02:45,317 ERROR [RbacAuthorizationHelper.authenticateUser:92] Exception:
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

And I found that /etc/init.d/scalix-tomcat status is not running...but when I type ps -ef|grep java, the job is running...moreover my ISP blocked port 80...

Sorry I search the forum and still cannot solved, pls help...thx

Lucas

Similar problem on CentOs 4.4

Postby Lucas » Sun Dec 24, 2006 5:45 pm

I'm having a similar problem on my Scalix 11 GA installation: I can't log on to SAC, but Webmail does work as expected. The error is:

Could Not Login
Could not fetch configuration information
Possible problem with administration server

I've modified the virtual host configuration as follows:

Code: Select all

<VirtualHost mail.servername.com:80>
    ServerName mail.servername.com
    Include /etc/opt/scalix-tomcat/connector/jk/app-servername.*.conf
</VirtualHost>
<VirtualHost mail.servername.com:443>
       ServerName mail.servername.com
       SSLEngine on

       SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
       SSLCertificateFile /etc/httpd/conf/ssl.crt/server.crt
       SSLCertificateKeyFile /etc/httpd/conf/ssl.key/server.key
       Include /etc/opt/scalix-tomcat/connector/jk/app-servername.*.conf
</VirtualHost>
JkWorkerProperty worker.servername.type=ajp13
JkWorkerProperty worker.servername.host=mail.servername.com
JkWorkerProperty worker.servername.port=8009
JkWorkerProperty worker.servername.lbfactor=50
JkWorkerProperty worker.servername.cachesize=10
JkWorkerProperty worker.servername.cache_timeout=600
JkWorkerProperty worker.servername.socket_keepalive=1
JkWorkerProperty worker.servername.recycle_timeout=300


On that configuration, webmail still works but SAC gives exactly the same error. Authentication is working properly, since the "Could not fetch information" error appears only if I enter the correct password - invalid passwords are properly identified as such.

Overall, it seems that unless Scalix is the first server that's replying on servername.com, I'll end up getting SAC problems. Is there some configuration file I'm missing? Is Scalix attempting to access it via IP address?

Thanks in advance.

Phantasmagoria
Posts: 22
Joined: Tue Nov 15, 2005 4:29 am

Postby Phantasmagoria » Mon Dec 25, 2006 6:30 am

Finally I solved my problem...can login sac now!

Since my ISP blocked port 80, I need edit the following file:
/var/opt/scalix/bg/res/config/res.properties

Inside have a line:
res.tomcat.tcp.port=(Default is nothing)
I changed it to:
res.tomcat.tcp.port=1234(See which port u using it)

Thats work for me!

pibarrola

Postby pibarrola » Wed Dec 27, 2006 11:53 pm

Lucas,

I was having the same problem with SAC after upgrading from 10.0 to 11.0. I was able to resolve it by adding the following lines to /etc/opt/scalix-tomcat/connector/*/instance-<servername>.conf.

Code: Select all

<VirtualHost *:80>
    ServerName virtual-name.example.com
    Include /etc/opt/scalix-tomcat/connector/jk/app-servername.*.conf
</VirtualHost>
<VirtualHost *:80>
    ServerName servername.example.com
    Include /etc/opt/scalix-tomcat/connector/jk/app-servername.*.conf
</VirtualHost>


I noticed in the log files that Scalix was trying to access some services by going to http://servername.example.com/res/RESDi ... blahblah... The way the virtual hosts were configured Apache wasn't serving up anything for that hostname.

HTH,
Phil

Lucas

Postby Lucas » Sat Dec 30, 2006 12:14 am

Thanks a lot for your suggestion, Phil. Unfortunately it doesn't seem to have solved my problem. Which log did you find this reference at, so I can check what mine is doing?

joey4712
Posts: 29
Joined: Tue Jan 16, 2007 3:17 pm

Re: Problem to login SAC with FC5

Postby joey4712 » Wed Feb 14, 2007 4:50 pm

Phantasmagoria wrote:Just fresh install FC5 and Scalix 11...

When I use sxadmin to login it will display "Cannot fetch configuration information...", and I found error in logs file:



I have the same problem with an almost fresh install of FC5 and Scalix 11. It says "Cannot fetch configuration information..." when logging into SAC with sxadmin and the correct passwort.

Additional info: After rebooting the server, I can log into SAC without problems. When trying again about an hour later I'm getting the above error again.

Can anyone confirm this? Did anyone find a solution for this??

Thanks....

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Re: Problem to login SAC with FC5

Postby mito » Tue Feb 27, 2007 10:17 am

joey4712 wrote:I have the same problem with an almost fresh install of FC5 and Scalix 11. It says "Cannot fetch configuration information..." when logging into SAC with sxadmin and the correct passwort.

Additional info: After rebooting the server, I can log into SAC without problems. When trying again about an hour later I'm getting the above error again.


I am still on Scalix 10, but after a recent server migration to a new server I now might be having this problem. I had been able to login to the SAC previously, but now I cannot login, getting the same error. I haven't restarted it yet as it is currently in a heavy-use time of day and most of my users use webmail.

I'm not sure what's going on with mine right now, just noticed it and started looking into it. I'll let you know more if I find out anything more.

Mito

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Postby mito » Wed Mar 07, 2007 9:27 pm

The next chance I had after posting my last message I rebooted the server and I was able to get into the SAC. Now, a week later, the next time I go into it I again can't login, the same message:

Code: Select all

Could Not Login
Could not fetch configuration information.
Possible problem with administration server


My environment is Scalix 10.0.5 running on CentOS 4.4. Nothing has changed since I was able to login last, and webmail still works perfectly.

Any ideas?

jonwatson
Posts: 25
Joined: Sun Jan 14, 2007 11:04 pm
Location: Calgary, Alberta, Canada, eh?
Contact:

Postby jonwatson » Mon Mar 12, 2007 5:54 pm

Same problem.

Sigh..the more I have to play with Scalix, the more I like Citadel. There's a lot of broken stuff under the hood.
http://www.jonwatson.ca
Friends don't let friends do Windows.

rex007can

Postby rex007can » Tue Mar 13, 2007 8:21 am

Exact same problem here.

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Postby mito » Thu Mar 15, 2007 10:07 am

This is getting to be a very annoying problem, with no solution even hinted yet.

I would be VERY happy to do some troubleshooting, looking at logs, checking things out, etc, if anyone has any suggestions.

Rebooting the server every night just so that the SAC can be accessible isn't a valid solution. I never had this problem running Scalix 10 on FC4, but now that I'm on Scalix 10 on CentOS 4.4, I'm constantly having this problem.

Any suggestions are welcomed and encouraged! thanks!

rex007can

Postby rex007can » Thu Mar 15, 2007 11:14 am

Restarting Tomcat and doing a killall java in between start and stop does bring SWA back up without a complete reboot.
You could create a small 3 line script and run it as a cron job.

I know it not even close to a solution, but it beats rebooting...

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Postby mito » Thu Mar 15, 2007 11:48 am

rex007can wrote:Restarting Tomcat and doing a killall java in between start and stop does bring SWA back up without a complete reboot.
You could create a small 3 line script and run it as a cron job.

I know it not even close to a solution, but it beats rebooting...


I've tried restarting tomcat several times (each time hoping a miracle would happen.... lol....

but I never did a killall between the shutdown and the startup. I'll try that....

Does anyone know if this problem is fixed in 11.0.2?

mito
Posts: 194
Joined: Fri Mar 24, 2006 11:33 am

Postby mito » Thu Mar 22, 2007 12:06 pm

Any input on this? It is actually kinda serious as it makes the administration of the scalix server almost impossible without a restart...

Even if the restarting of tomcat fixes it, doing so disconnects all users that are currently using the webmail, and they loose any emails that they are currently writing. While this normally wouldn't be a problem, one could simply look and reboot the server/services when nobody is logged in... but you can't do that because you can't get into the SAC.

Any dev input on this issue? I'm hopefully going to be able to upgrade to 11.0.2.1 this weekend, but if this is still happening in that version, this is going to be very bad....

Mito

rex007can

Postby rex007can » Thu Mar 22, 2007 1:30 pm



Return to “Scalix Management Services”



Who is online

Users browsing this forum: No registered users and 1 guest