11.24 Upgrade: Roundcube Database Connect Error

RickG

Well-Known Member
Feb 28, 2005
238
2
168
North Carolina
Just migrated from 11.23 -> 11.2411.24.4-R32603 without incident.

Only issue is that users cannot access Roundcube webmail (they are getting DATABASE ERROR: CONNECTION FAILED!) when trying to bring up the URL.

I've had roundcube installed under /usr/local/lib/php/roundcube/ and running w/o issue prior to the 11.24 upgrade. In the roundcube log file I'm finding:

[25-Dec-2008 11:00:35 -0500] DB Error: _doConnect: [Error message: Access denied for user 'roundcube'@'localhost' (using password: YES)]

Any thoughts?
 
Last edited:

nerbonne

Well-Known Member
Aug 19, 2007
52
1
58
I get this same error after upgrading from 10.x to 11.x. Both Roundcube and Horde give this error, while squirrellmail works? Previously in 10.x we did not have Roundcube.

I'd be really interested in a solution to this. Thanks.

Horde error:

A fatal error has occurred
DB Error: connect failed
Details have been logged for the administrator.


Here is what my mysql error file says. Note that there are no new entries newer than the 18th, but the problem still occurs and I just tried to login and an error was not written:

081118 10:03:41 [Warning] Found invalid password for user: '[email protected]'; Ignoring user
081118 10:03:41 [Warning] Found invalid password for user: '[email protected]'; Ignoring user
081217 8:00:14 [Warning] Found invalid password for user: '[email protected]'; Ignoring user
081217 8:00:14 [Warning] Found invalid password for user: '[email protected]'; Ignoring user
081218 8:00:36 [Warning] Found invalid password for user: '[email protected]'; Ignoring user
081218 8:00:36 [Warning] Found invalid password for user: '[email protected]'; Ignoring user



Also note that the server came up normally with no errors:

081225 12:14:38 InnoDB: Starting shutdown...
081225 12:14:40 InnoDB: Shutdown completed; log sequence number 0 189056493
081225 12:14:40 [Note] /usr/sbin/mysqld: Shutdown complete

081225 12:14:40 mysqld ended

081225 12:14:40 mysqld started
081225 12:14:40 InnoDB: Started; log sequence number 0 189056493
081225 12:14:40 [Note] /usr/sbin/mysqld: ready for connections.
 
Last edited:

sirotex

Well-Known Member
Jul 10, 2008
121
0
66
It isn't MySQL, it's IMAP. I've been playing with Courier & Dovecot all day. Using courier in 11.24 it fails to start, but yet can connect to webmail. Dovecot however stays up etc but isn't converting the mail DB's correctly so you will be best using Courier, and moving to STABLE untill they fix it.
 

nerbonne

Well-Known Member
Aug 19, 2007
52
1
58
Ok, I was able to fix my problem by setting courier to "manual update" and leaving all other software on never, and then running a cp update. After the update roundcube worked fine.

Thanks for the help.
 

RickG

Well-Known Member
Feb 28, 2005
238
2
168
North Carolina
Resolved

As part of troubleshooting process, I re-ran the Roundcube installer utility and discovered that the database user no longer had write permissions to the database. I re-granted all privileges to the user and we're back in business.

Not certain what in the 11.24 upgrade might have caused this. All other php based MySQL applications have worked w/o error since the update.
 
Last edited:

BuffaloWeb

Well-Known Member
Jul 1, 2003
83
0
156
Resolved

As part of troubleshooting process, I re-ran the Roundcube installer utility and discovered that the database user no longer had write permissions to the database. I re-granted all privileges to the user and we're back in business.

Not certain what in the 11.24 upgrade might have caused this. All other php based MySQL applications have worked w/o error since the update.
Can you give some specific instructions please? Which user, which db?
 

RickG

Well-Known Member
Feb 28, 2005
238
2
168
North Carolina
Can you give some specific instructions please? Which user, which db?
On the install instructions at http://trac.roundcube.net/wiki/Howto_Install, scroll down to Database Configuration. I simply "re-granted" privelieges (given the database was already set up) per their instructions and we were good to go. Still not certain what in the 11.24 upgrade caused this issue, as it only effected the RoundCube application (all other PHP/MySQL scripts continued to work w/o error).