HTTP 400 Bad Request

Discuss the Scalix web client

Moderators: ScalixSupport, admin

house122

HTTP 400 Bad Request

Postby house122 » Tue Nov 24, 2009 2:34 pm

Good day,

I am new to Linux and Scalix. I have installed Scalix on a CentOS 5 server. I was able to open a web browser within the network and access sac with no problem. After restarting the server, I could not access sac anymore through any browser. All I get is HTTP 400 Bad Request message.

Can anyone please help?

Thank you in advance!

ltward
Posts: 309
Joined: Tue Jan 15, 2008 1:54 pm
Contact:

Re: HTTP 400 Bad Request

Postby ltward » Tue Dec 01, 2009 9:59 am

Try connecting to the SAC again and then go to /var/opt/scalix/??/tomcat/logs and do
ls -lrt

See what log files get updated when you try to login to SAC and check them for hints about what is going wrong.
Also check your httpd log files. In CentOS that's under /etc/httpd/logs. Don't remember where it is under SUSE.

house122

Re: HTTP 400 Bad Request

Postby house122 » Fri Jan 08, 2010 4:11 pm

Thank you for the guidance!

I found the following in the scalix-caa.log:
ERROR java.net.SocketException: Socket closed. After this I get:
INFO com.scalix.sac.ubermgr.NotificationEventListener$WorkerThread-thread-1 Thread shutting down.

Does this mean that Java is causing the problem?

Had the problem with Scalix 11.4.5 and 11.4.6

Any help would be appreciated!


Return to “Scalix Web Access”



Who is online

Users browsing this forum: No registered users and 1 guest