Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: thenkel on April 02, 2005, 09:05:14 PM

Title: Horde/IMP login failure
Post by: thenkel on April 02, 2005, 09:05:14 PM
I have a SME 6 server with latest updates that has been working exceptionally well. Recently however, the webmail (horde/imp) stopped letting users login. Logging in presents the message:

Login failed for some reason. Most likely your username or password was entered incorrectly.

I have twiggi installed on the server as well, and it too does not allow login. I have searched the forums and tried the horde dbconfig fix just for kicks - it does not work, as i assumed i'm not having a problem with the db.

Looking into the log files i found this bit of information:
IMAP LOG
Code: [Select]
2005-04-02 13:17:40.566556500 2005.04.02 18:17:40 LOG5[3009:1024]: Using 'imap' as tcpwrapper service name
2005-04-02 13:17:40.567288500 2005.04.02 18:17:40 LOG4[3009:1024]: Failed to write strong random data to seed - may be a permissions or seeding problem
2005-04-02 13:17:40.567350500 2005.04.02 18:17:40 LOG4[3009:1024]: PRNG may not have been seeded with enough random bytes
2005-04-02 13:17:40.568940500 2005.04.02 18:17:40 LOG3[3009:1024]: Error reading certificate file: imapd.pem
2005-04-02 13:17:40.569009500 2005.04.02 18:17:40 LOG3[3009:1024]: SSL_CTX_use_certificate_chain_file: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded


messages log
Code: [Select]
Apr  1 07:42:58 server HORDE[17787]: [imp] FAILED LOGIN 209.130.202.252 to localhost:143[imap/notls] as rsmith [on line 287 of "/home/httpd/html/horde/imp/lib/IMP.php"]
Apr  1 07:42:58 server HORDE[17787]: PHP Notice:  (null)(): Connection failed to localhost,143: Connection timed out (errflg=2) in Unknown on line 0


I'm assuming my problem is related to ssl seeding/random number generator. But i am not sure where to go from here.

My questions to all is, has anybody seen this problem before, and if you have what did you do to fix it?

Thank you in advance, these forums have helped me fix a lot of problems in the past by just browsing and searching, but this one is really a head scratcher to me.
Title: Horde/IMP login failure
Post by: ergozd on April 03, 2005, 08:06:11 AM
May be you can re-generate new .pem file

# /etc/e-smith/events/actions/imap-pem-cert
Title: Horde/IMP login failure
Post by: thenkel on April 03, 2005, 07:41:55 PM
ergozd --

Thanks for the tip, but no joy :(

After further investigation it appears to be a stunnel problem(?) Will keep the thread alive until i find a solution one way or the other......

Just fyi, I got the webmail working again (kinda) by setting imp to pop3 rather than imap. Luckily, the webmail is only used for remote mail and not daily email activity.
Title: Re: Horde/IMP login failure
Post by: CharlieBrady on April 03, 2005, 11:58:00 PM
Quote from: "thenkel"
I have a SME 6 server with latest updates that has been working exceptionally well.


What "latest updates" have you applied?

If you've "upgraded" stunnel, you would likely have broken imap access.
Title: Horde/IMP login failure
Post by: thenkel on April 04, 2005, 04:56:38 PM
No updates lately, this machine serves a remote office and was completely (clean install) upgraded from sme5.6 in december. The only updates the machine has recieved is the smeplus.sh script after the intial refresh/upgrade was complete. Other than that, the machine had been performing flawlessly.

I have rkhunter installed, and it hasn't turned up anything strange. I'm almost certain that noone onsite could have done anything, as this is a "magic box" to them (i.e. it has no monitor/keyboard yet still "magically" serves them files/email/etc.)

Thank you for your input :)
Title: Re: Horde/IMP login failure
Post by: CharlieBrady on April 10, 2006, 05:01:15 PM
Quote from: "thenkel"
I have a SME 6 server with latest updates that has been working exceptionally well. Recently however, the webmail (horde/imp) stopped letting users login.


All problems should be reported (only) via the Bug Tracker.