Users suddenly can't login / restarting tomcat fixes

[TheDude]

Hello all!

I am loving the Community Edition and everything works great, except for a couple of weird things with the web mail. I can create a new user and their pop3 account will work perfect instantly, but, they won’t be able to login to the web access until I restart tomcat. Also, sometimes users suddenly can’t login to the web mail – I can fix this by restarting tomcat. Here is part of todays tomcat error log were a user who *I KNOW* was entering the correct password was shut out (he got in fine, using the same password, right after I restarted the tomcat service from a terminal prompt):


</debug></e:BadUserName></detail></SOAP-ENV:Fault>
2005-11-07 12:35:57 StandardContext[/webmail]ip: xx.xx.xx.xx; username: john.doe@ourdomain.com; message: <SOAP-ENV:Fault><faultcode>SOAP-ENV:CLIENT.BadUserName</faultcode><faultstring>The username or password is incorrect. Note that passwords are case sensitive. Try again.</faultstring><detail><e:BadUserName xmlns:e="http://scalix.com/errors"><message>The username or password is incorrect. Note that passwords are case sensitive. Try again.</message><debug>user: john.doe@ourdomain.com
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;john.doe@ourdomain.com&lt;/username&gt;&lt;emailDomain&gt;com&lt;/emailDomain&gt;&lt;fugu&gt;Ox353a3d3f29242d322c283132232f2b2b34343104&lt;/fugu&gt;&lt;ts&gt;0&lt;/ts&gt;&lt;rand&gt;10C351A600CD43D92F430F4179294FD2&lt;/rand&gt;&lt;rand2&gt;583d59f7f8729161eeea1a7033d11fdc62df8773&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:BadUserName></detail></SOAP-ENV:Fault>


Thanks for any help, I love Scalix!

The Dude

[TheDude]

I have been crawling this board for awhile and I just found a reference to a patch.

I am running server 9.4.0.8-0.1 and the board says I should upgrade to 9.4.0.9 if I am having concurent user problems. My users get an error saying the password is bad. Is that the way this problem shows itself?

Also, If I do install this patch will it mess up my Spam Assasin integration? What all does the patch alter?

Thanks,

Dude

[ScalixSupport]

Hi The Dude,

Ready for a White Russian? ;-)

You'll find a RELEASE_NOTES.html file after you uncompress the package that will document the changes. Your SpamAssasign will be fine.

Thanks,
Don

[TheDude]

Thanks Don!

The patch fixed the problems *and* it did not change any of the many, many things I have tweeked (including the super-complicated-until-you-guys-post-an-updated-tutorial spam assasin integration that took me 2 days!!!) :lol:

That is some great coding on the patch! Will all future upgrades work without changing things like the partner.xml file and the sendmail config? How do we know when you guys have posted a new Scalix?

I was happy with Scalix even when I had to restart tomcat all the time, so I should be real happy now!

Thanks!

The Dude

[ScalixSupport]

We're working on different ways of communicating new updates but, for the moment, subscribing to the announcements forum digest should work.
Cheers

Dave

[florian]

and for the technical part of the upgrade, it is our goal to make sure that most upgrades will just work like the one you just experienced, running our installer, minimal downtime (typically <15 minutes) and no manual intervention.

Obviously, this will depend on the changes we do in the, but we'll try to keep it simple like that; as we'll be working hard to bring new features to our users as fast as we can, this is certainly a _must_ to keep the admin happy as well.

Glad it worked for you,
Florian.