Dovecot Pam and Roundcube

Hi,

I updated latelly some php packages on Centos 6.5 and I get this now when trying to login with roundcube ONLY:

==> /var/log/secure <==
Dec 14 12:19:55 jefferson auth: pam_unix(dovecot:auth): check pass; user unknown
Dec 14 12:19:55 jefferson auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=test@xxxx.com rhost=127.0.0.1
Dec 14 12:19:55 jefferson auth: pam_succeed_if(dovecot:auth): error retrieving information about user test@xxxx.com

==> /var/log/maillog <==
Dec 14 12:20:00 jefferson dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=test@xxxx.com, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured

No options were changed anywere so somehow the update broke something.
This is the list of what was updated, I will try to revert back to old packages BUT it seems like it induced some issues:

Dec 10 14:05:32 Updated: libjpeg-turbo-1.2.1-3.el6_5.i686 Dec 13 11:38:28 Updated: php-common-5.3.3-27.el6_5.i686 Dec 13 11:38:31 Updated: nspr-4.10.2-1.el6_5.i686 Dec 13 11:38:33 Updated: nss-util-3.15.3-1.el6_5.i686 Dec 13 11:38:35 Updated: php-pdo-5.3.3-27.el6_5.i686 Dec 13 11:38:44 Updated: nss-3.15.3-2.el6_5.i686 Dec 13 11:38:46 Updated: nss-sysinit-3.15.3-2.el6_5.i686 Dec 13 11:39:01 Updated: php-cli-5.3.3-27.el6_5.i686 Dec 13 11:39:09 Updated: php-5.3.3-27.el6_5.i686 Dec 13 11:39:25 Updated: nss-tools-3.15.3-2.el6_5.i686 Dec 13 11:39:26 Updated: php-mysql-5.3.3-27.el6_5.i686 Dec 13 11:39:28 Updated: php-odbc-5.3.3-27.el6_5.i686 Dec 13 11:39:29 Updated: php-pgsql-5.3.3-27.el6_5.i686 Dec 13 11:39:34 Updated: php-mbstring-5.3.3-27.el6_5.i686 Dec 13 11:39:37 Updated: php-gd-5.3.3-27.el6_5.i686 Dec 13 11:39:40 Updated: php-xml-5.3.3-27.el6_5.i686 Dec 13 11:39:41 Updated: php-imap-5.3.3-27.el6_5.i686 Dec 13 11:39:42 Updated: php-snmp-5.3.3-27.el6_5.i686

The more I search for solutions the more it looks like a pam problem.
When I try other method such as shadow or passwd it still fails with same error message.
I am no expert on the plumbing between dovecot, saslauthd, postfix and other related packages BUT there is something wrong with this upgrade.

Regards,

Howdy,

Hmm, I haven’t seen any issues like you’re describing when updating the PHP and NSS packages on CentOS.

Is this same user able to log into IMAP using another tool which uses Dovecot, such as Outlook or Thunderbird?

Also, are there any third party repositories enabled on your server? What output do you receive when running this command:

ls /etc/yum.repos.d/

Howdy,

It works fine with e-mail client such as thunderbird or else BUT with roundcube no.

Here is the output uf the command ls:

[root@jefferson ~]# ls /etc/yum.repos.d/ total 60K drwxr-xr-x 2 root root 4.0K Dec 7 12:33 . drwxr-xr-x 85 root root 4.0K Dec 14 16:31 .. -rw-r--r-- 1 root root 1.9K Nov 30 19:06 CentOS-Base.repo -rw-r--r-- 1 root root 638 Nov 30 19:06 CentOS-Debuginfo.repo -rw-r--r-- 1 root root 630 Nov 30 19:06 CentOS-Media.repo -rw-r--r-- 1 root root 4.5K Nov 30 19:06 CentOS-Vault.repo -rw-r--r-- 1 root root 1.7K Aug 13 2005 RPM-GPG-KEY.dag.txt -rw-r--r-- 1 root root 1.1K Nov 4 2012 epel-testing.repo -rw-r--r-- 1 root root 957 Oct 26 08:29 epel.repo -rw-r--r-- 1 root root 739 Mar 20 2013 mirrors-rpmforge -rw-r--r-- 1 root root 717 Mar 20 2013 mirrors-rpmforge-extras -rw-r--r-- 1 root root 728 Mar 20 2013 mirrors-rpmforge-testing -rw-r--r-- 1 root root 1.2K Oct 23 11:42 rpmforge.repo -rwsr-s--- 1 root root 471 Jun 2 2011 virtualmin.repo [root@jefferson ~]#

Thanks for your experience, always greatly appreciated.

Regards,

Hi,

I solved it. The problem happened when I upgraded the roundcube app.
I removed it and re installed it and bingo.

Weird stuff. This means that any upgrade requires a complete system backup when you cnnot afford downtime in production.

Regards,

I’m glad you figured it out!

Yeah, normally RoundCube upgrades are fairly straight forward, but as you mentioned it’s probably wise to have backups of it just in case.

If you don’t already, I might suggest setting up nightly Virtual Server backups within Backup and Restore -> Scheduled Backups.

Then, if an app upgrade goes awry, you could always restore to the previous night’s backup.

-Eric