#3765 With mcrypt enabled I get frequent unexpected logouts
Hi there,
when mcrypt is enabled on my server I often get logged out of PMA out of nothing. I'm then redirected to the login page which shows an error (I think it was #1045).
After that it is very hard (sometimes impossible) to re-login. That means I will instantly get logged out and redirected to the login page with the error again. (As I use a password manager there is for sure no problem with the password.) When I disable JavaScript the login page with the error only appears in the right (content) frame while the left (menu) frame is actually showing all tables as if the login would have worked.
When I try long enough (and I have the feeling that changing the language speeds the process up) somtimes suddenly the login just works again. Then I can work with PMA for some seconds to even some hours (it seems totally random) until an unexpected logout again happens...
There is no error in the apache error log, nothing that would seem unusual in the access log and I couldn't find any error in any other log.
I'm using phpMyAdmin 3.5.5, Apache/2.2.22, MySQL 5.5.28-0ubuntu0.12.04.3 - (Ubuntu), PHP 5.3.10-1ubuntu3.4, Charset is UTF-8 Unicode
As soon as I disable mcrypt for the PMA domain everything works fine only there is a big warning on the home page that mcrypt is missing :c
Thanks for your support
Hi,
which browser are you using? Did you try another browser?
What is the value of $cfg['LoginCookieValidity'] in your phpMyAdmin configuration? and of your session.gc_maxlifetime in php.ini ?
This does not feel like a phpMyAdmin bug to me, because we would get more reports about this.
@lem9
It seems you are right. $cfg['LoginCookieValidity'] were set to 2 days and session.gc_maxlifetime to one year (both stated in seconds of course) but as you said that you think it is very unlikely a PMA bug I completely uninstalled the php5 mcrypt extension on my server and reinstalled it.
That was three days ago and I worked quite a lot on the app which DB I manage over PMA in that time. And so far the error didn't occur again. As it occurred very frequently and soon before I guess it is gone for good.
No idea what was wrong with the mcrypt installation or configuration and why it only affected PMA on the server but as long as everything works now I don't really care.
Thanks for your support!