Page 1 of 1

Could not login to /webmail or /sac after installation

Posted: Tue Aug 09, 2005 12:38 pm
by mwozenilek
After a installation without errors i'm not able to login to webmail- or sac-site with my sxadmin account. webmail gives me: "There was a problem connecting the mail server. Please try again later." sac gives me "The administration server is not responding." (yes, i've used me scalix login-id).

I've checked the logs. What is mentionable:

--------------------
caa.log:
2005-08-09 18:22:38,449 ERROR [RbacAuthorizationHelper.authenticateUser:80] Exception:
javax.naming.CommunicationException: vmw-fc4.wozenilek.de:389 [Root exception is java.net.SocketException: Invalid argument or cannot assign requested address]
--------------------


--------------------
scalix-swa_log.2005-08-09.txt:
2005-08-09 18:19:58 StandardContext[/webmail]ip: 192.168.5.50; username: sxadmin; message: <SOAP-ENV:Fault><faultcode>SOAP-ENV:CLIENT.ProblemConnectingToImap</faultcode><faultstring>There was a problem connecting to the mail server. Please try again later.</faultstring><detail><e:ProblemConnectingToImap xmlns:e="http://scalix.com/errors"><message>There was a problem connecting to the mail server. Please try again later.</message><debug>user: sxadmin
request method(s): login
XML:
&lt;SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"&gt;&lt;SOAP-ENV:Header&gt;&lt;credentials xmlns="http://scalix.com/schemas/gofish" SOAP-ENV:mustUnderstand="1"&gt;&lt;username&gt;sxadmin&lt;/username&gt;&lt;emailDomain&gt;wozenilek.de&lt;/emailDomain&gt;&lt;fugu&gt;Ox6d6762646f36383234252e2530322a2623322608&lt;/fugu&gt;&lt;ts&gt;0&lt;/ts&gt;&lt;rand&gt;8378C2D080D977B49B7373FEB66D9D95&lt;/rand&gt;&lt;rand2&gt;74bd0a87ab9de6c228b3284789ca3cd040a4b315&lt;/rand2&gt;&lt;/credentials&gt;&lt;/SOAP-ENV:Header&gt;&lt;SOAP-ENV:Body&gt;&lt;m:login xmlns:m="http://scalix.com/methods"/&gt;&lt;/SOAP-ENV:Body&gt;&lt;/SOAP-ENV:Envelope&gt;</debug></e:ProblemConnectingToImap></detail></SOAP-ENV:Fault>
--------------------

What i've checked:
- permissions with scalix helper program
- /etc/services
- DNS
- /etc/hosts
- Java J2SE SDK Version (1.4.2)
- Services running

Any ideas?

Posted: Tue Aug 09, 2005 5:53 pm
by ScalixSupport
Hello,

Just curious what version of Tomcat are you using?

Thanks,
Yuri

Posted: Wed Aug 10, 2005 2:22 am
by mwozenilek
The one which comes with the installer: 5.0.28.

Further versions:

- Fedora Core 4 on VMWare 4.5

Posted: Wed Aug 10, 2005 4:09 pm
by florian
the first error from caa.log has some port number 389 to it. are you running an openldap server on the machine that binds to port 389?

could you check...
* status of ldap server in omstat -a
* omshowlog output for ldap server startup errors
* netstat -anp | grep 389 for the name of the process that is bound to port 389 - should be omslapd

did you do any hostname changes after you ran the scalix installer?

thx,
F.

Posted: Wed Aug 10, 2005 4:45 pm
by mwozenilek
[root@vmw-fc4 ~]# omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 21:29:43
Notification Server Started 21:29:43 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped
Database Monitor Started 21:29:43
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 21:29:43
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 21:29:43
SMTP Relay Started 21:29:43
Mime Browser Controller Started 21:29:43

--------------------------------

omshowlog shows no errors

--------------------------------

[root@vmw-fc4 ~]# netstat -anp | grep 389
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 4273/omslapd

--------------------------------

No, i've not changed the name of the machine in /etc/sysconfig/network or in /etc/hosts.

I'm very sorry that I could not supply your with more "ideas". But I've tried so many things that I don't know what else could be wrong.

Maybe it's a problem with VMWare 4.5 and the Java-Stuff. Maybe I will try it on a "real" machine when I have some time. Overall this beast seems to be very very complex and there are so many potential problems.

Thanks for your help!

Posted: Wed Aug 10, 2005 5:02 pm
by ScalixSupport
A quick Google for this error reveals the following link:

http://www.jroller.com/page/dissonance/ ... _4_and_jdk

Reading into this, the workaround is to add the following option to JAVA_OPTS in $TOMCAT_HOME/bin/setclasspath.sh:

-Djava.net.preferIPv4Stack=true



Cheers

Dave

Posted: Thu Aug 11, 2005 2:13 pm
by mwozenilek
Yep! Now it's working! It was the IPv6 thing. I've never tought it could be this problem because Truedesk and Desknow (both using java) are working fine.

LDAP has crashed one time but only once.

Thanks!

Posted: Fri Sep 16, 2005 9:45 pm
by yakwakdo
I do not see a JAVA_OPTS in setclasspath.sh. Can you post a working sample please?



ScalixSupport wrote:A quick Google for this error reveals the following link:

http://www.jroller.com/page/dissonance/ ... _4_and_jdk

Reading into this, the workaround is to add the following option to JAVA_OPTS in $TOMCAT_HOME/bin/setclasspath.sh:

-Djava.net.preferIPv4Stack=true



Cheers

Dave

Same problem

Posted: Wed Nov 02, 2005 11:23 am
by TonyC2
I am having this exact problem but adding the JAVA_OPTS line into catalina.sh is not fixing the problem. any other suggestions?

Posted: Wed Nov 02, 2005 11:50 am
by natkins
Hi guys,

The installer should have added the following lines to the top of your Tomcat/bin/setclasspath.sh file:

# Added by Scalix Wizard version 9.4.xx (do not remove any of this section)
JAVA_HOME=/usr/java/j2sdk1.4.2_07
JAVA_OPTS="-server -Xms512m -Xmx512m -Djava.net.preferIPv4Stack=true"
# End of added Scalix Wizard entries

note the last JAVA_OPTS param, it's needed in Fedora Core 4 because of some recent changes that cause Java to revert to IPv6 mode by default.

Hope this helps.

Nick.