A fatal error has occurred
Could not connect to database for SQL SessionHandler.
Details have been logged for the administrator.
Anyone know the fix.![]()
Thanks!
A fatal error has occurred
Could not connect to database for SQL SessionHandler.
Details have been logged for the administrator.
Anyone know the fix.![]()
Thanks!
SSH to your server and type the following commands:
#mysql
#mysql> use horde
#mysql> repair table horde_sessionhandler;
Nope doesn't fix it, but thanks for the try.
Both times cpanel fixed it they said this:
I have edited /root/.my.cnf and removed the quotes and Horde is now working properly.
and this:
I've removed the extra quotes, and it should be working now. Let me know if you continue to experience this problem.
But that file only has double quotes. Not sure what quotes to remove and from what line??
Thanks
I see. The quotes are deprecated in new versions of MySQL.
Im getting this error and i dont have any quotes in my.cnf
Im not using a remote mysql server either
anyone know how to fix this?
Ive done a forced upcp a forcedhordereset and run a repai on the horde database but still no joy
That won't work on the horde_sessionhandler table since it's of type InnoDB, which doesn't support repair. One can try CHECK TABLE horde_sessionhandler, but the sureset option is to drop the table and recreate it:
> drop table horde_sessionhandler;
> CREATE TABLE horde_sessionhandler (
session_id VARCHAR(32) NOT NULL,
session_lastmodified INT NOT NULL,
session_data LONGBLOB,
PRIMARY KEY (session_id)
) ENGINE = InnoDB;
well I have tried the suggestions from cpanelkenneth but Horde mail still shows the same error.
Is there a real fix for this?
Well for the next person this happens to you might try this from shell
/usr/local/cpanel/bin/update-horde --force
It worked for us
I'm glad you got it working. For future reference, here are some steps that will either fix the problem, or provide more clues:
- Check that the horde_sessionhandler is not corrupted. If it is, the drop and create statements I posted above will resolve this particular issue.
- Verify the horde user has proper permissions on the horde_sessionhandler table. Specifically it should have select, insert, update and delete permissions. If not, then grant them:
Code:> GRANT SELECT, INSERT, UPDATE, DELETE ON horde_sessionhandler TO horde@localhost; > FLUSH PRIVILEGES;- Enable logging in Horde. Edit the file /usr/local/cpanel/base/horde/config/conf.php:
Try logging into Horde, then check the file created in /tmp. It will be named some thing like horde_123445.logCode:// change $conf['log']['enabled'] = false; // to $conf['log']['enabled'] = true; // change $conf['log']['priority'] = PEAR_LOG_WARN; // to $conf['log']['priority'] = PEAR_LOG_DEBUG;
- You can also enable MySQL error logging on the off chance something appears there. Edit /etc/my.cnf to contain:
You can place the log whereever you want (some opt for /var/lib/mysql/mysql.log)Code:log-error=/var/log/mysql.log