Topic: Horde / Webmail not accepting login - "login failed"

[pmstewart]

For some strange reason the domain.com/webmail has suddenly developed a hiccup! All (admin included) accounts on the server will not log into webmail -

Error returned - "Login Failed"

Have tried to delete users and recreate them - same problem
Have tried to reset passwords - same problem
Have tried to create new users - same problem

Running SME 7.3 with updates done a few weeks ago but all was working well until today - last time successful logon about 8 hours before this started.

Logging on with pop3 / smtp from local network - ok
Logging on with pop3s / ssmpt from outside local network - ok (server-gateway mode)

No changes were made to this server except to plug it into a battery backup but NUT is disabled. (shut down server from console before connecting battery)

There are two of us who scoured the forums all day looking for an answer and in bugzilla as well - cannot seem to find anything on this issue.

Any suggestion?

TIA

Paul

[pfloor]

Anything in the log files?

[cactus]

Any suggestion?

Yes launch a bug in the bugtracker as this should not happen. The devs will most likely be able to solve your problem and the quickest way to draw their attention is to use the bugtracker. Post a referral to the bug you created here please for future reference.

[pmstewart]

Cactus: As requested - Bug reported - http://bugs.contribs.org/show_bug.cgi?id=4552

PFloor: The message log indicates a problem with the horde/imp/lib/Auth module as shown below:

Code: [Select]

Sep 11 13:19:23 HORDE[3969]: [imp] FAILED LOGIN xxx.xxx.xxx.xxx to localhost:143[imap/notls] as "user" [on line 258 of "/home/httpd/html/horde/imp/lib/Auth/imp.php"]
Sep 11 13:20:16 HORDE[3971]: [imp] FAILED LOGIN xxx.xxx.xxx.xxx to localhost:143[imap/notls] as "user" [on line 258 of "/home/httpd/html/horde/imp/lib/Auth/imp.php"]
Sep 11 13:20:31 HORDE[3971]: [imp] FAILED LOGIN xxx.xxx.xxx.xxx to localhost:143[imap/notls] as admin  [on line 258 of "/home/httpd/html/horde/imp/lib/Auth/imp.php"]

After more investigation a reinstallation of imp may solve the problem (not the best way but no-where else to look)

Went to the server-manager and using the updates panel uninstalled and reisntalled the imp modules.

Everything is happy now!

Thank you both for your prompt response

[cactus]

After more investigation a reinstallation of imp may solve the problem (not the best way but no-where else to look)

Went to the server-manager and using the updates panel uninstalled and reisntalled the imp modules.

Everything is happy now!

Good that everything is working now, but by your actions we are now no longer able to determine what has happened causing the error.

Next time please do not touch your system when reporting a bug, other than instructions given in the bug report.

[pfloor]

After more investigation a reinstallation of imp may solve the problem (not the best way but no-where else to look)

Went to the server-manager and using the updates panel uninstalled and reisntalled the imp modules.

Everything is happy now!

I wouldn't be so quick to say "Everything is happy now".  Using the server-manager to remove packages has been known to remove more than you bargain for and then not reinstall everything (see this unresolved bugs http://bugs.contribs.org/show_bug.cgi?id=3133 and http://bugs.contribs.org/show_bug.cgi?id=3134)

I cant say that you would have experienced those bugs but you may want to check your log files and compare the packages were removed and then reinstalled to make sure everything was done correctly.

[pmstewart]

Even after three years of investigation, trial & error, and practice there are many things about the server which baffle me.

Cactus, I didn't think that one through very closely, I certainly will remember your suggestion for future reference....thank you for
bringing to my attention my short sightedness.

PFloor, Thank you as well for pointing out the posts in bugzilla, I had never seen those before and will use this to test the server for
possible dependencies I very well may have missed.

You guys are tops!

Paul

Note: My apologies to the members of the forum for pointing out the "WRONG" way to do things .....I hope everyone has been helped
through this information......

[pmstewart]

PFloor,

According to the Yum log the following took place on that day:

Code: [Select]

Sep 12 12:14:52 Erased: horde
Sep 12 12:14:53 Erased: e-smith-horde
Sep 12 12:14:54 Erased: imp-h3
Sep 12 12:14:56 Erased: e-smith-imp
Sep 12 12:14:58 Erased: turba-h3
Sep 12 12:14:58 Erased: e-smith-turba
Sep 12 12:14:59 Erased: ingo-h3
Sep 12 12:14:59 Erased: e-smith-ingo


Sep 12 12:25:29 Installed: horde.noarch 3.1.7-1.el4.sme
Sep 12 12:25:30 Installed: e-smith-horde.noarch 1.13.0-24.el4.sme
Sep 12 12:25:31 Installed: imp-h3.noarch 4.1.6-1.el4.sme
Sep 12 12:25:32 Installed: e-smith-imp.noarch 1.13.0-11.el4.sme
Sep 12 12:25:32 Installed: turba-h3.noarch 2.1.7-1.el4.sme
Sep 12 12:25:35 Installed: e-smith-turba.noarch 1.7.0-17.el4.sme
Sep 12 12:25:36 Installed: ingo-h3.noarch 1.1.5-1.el4.sme
Sep 12 12:25:36 Installed: e-smith-ingo.noarch 1.1-6.el4.sme


The messages log does not show any errors which were not present before this change except for the imp login messages are now successful.

Paul

[pfloor]

Paul, you really lucked out there.

The software panel uses "yum -y remove <selected package(s)>

Almost every "yum remove xxx" will remove (due to dependencies) some key packages.  It turns into a chain reaction and render the server useless. You have probably found some of the (very) few packages that can be removed via yum without trashing the server.

You must be living right

[Blackbox]

I refer to bug tracker No. 4552.

I have just experienced this problem as soon as I enabled the webmail.

 Nov 12 12:57:48 mailer HORDE[3968]: [imp] FAILED LOGIN 192.168.2.101 to localhost:143[imap/notls] as admin [on line 258 of "/home/httpd/html/horde/imp/lib/Auth/imp.php"]

I noticed that bug 4552 has been closed due to a work around.

If the development team would like to re-open the ticket, I will be more than happy to assist them.

I would really appreciate if this could be solve as I need to access my email via the web interface.

Thanks

[thomasch]

Paul, you really lucked out there.

The software panel uses "yum -y remove <selected package(s)>

Almost every "yum remove xxx" will remove (due to dependencies) some key packages.  It turns into a chain reaction and render the server useless. You have probably found some of the (very) few packages that can be removed via yum without trashing the server.

Yes. Very very dangerous. Give it a click and the server trashed.

The good news is that (I believe) the devs team are working on it.
There's a NFR in bugtracker to remove this (yum) functionality from panel or at least give a a very big red blinkin' warning as this is very dangerous command to run.

thomas

[thomasch]

If the development team would like to re-open the ticket, I will be more than happy to assist them.

You can always 'butt in' in to that bug and ask for a REOPEN.

thomas

[Blackbox]

Hi,
I inserted a comment in that bug asking the development team to reopen.

Am I doing it the correct way to ask for a reopen?

Or is there any other way to nofiy them.

Kindly advise
Thanks

[Blackbox]

Hi,
I would really like to fix this issue as pressure is accumulating in my boss's head.

Can someone list which modules I need to reinstall in order for webmail to work please?

Thanks in advance

[mrjhb3]

Hi,
I would really like to fix this issue as pressure is accumulating in my boss's head.

Can someone list which modules I need to reinstall in order for webmail to work please?

Thanks in advance

What happened before webmail stopped working?  Did you install some updates and webmail stopped.  If so, do you have a custom-template for 110AppRegistryHorde?  If so, that needs to be removed as per bug 3707, http://bugs.contribs.org/show_bug.cgi?id=3707.

If you removed the webmail modules, then go to the command line and do a

Code: [Select]

yum install e-smith-horde e-smith-ingo e-smith-turba e-smith-imp
Then the appropriate horde modules will be pulled in as dependencies.  If you already had webmail enabled and active, then all you'll need to do is

Code: [Select]

signal-event email-updateThen access webmail.  If all else fails, then you can issue the hammer

Code: [Select]

signal-event post-upgrade ; signal-event reboot
The above is just a guess as there's not enough information that I can see that states what you did before webmail broke.

John