I'm having an issue with my site. We were using Redis sessions, but after some issues with latency we've decided to switch back to MySQL sessions.
The app/etc/local.xml file used to look something like
<config> <global> [...] <session_save>db</session_save> <redis_session> <host>127.0.0.1</host> <port>6379</port> <password></password> <timeout>2.5</timeout> <persistent>sess-db2</persistent> <db>2</db> <compression_threshold>2048</compression_threshold> <compression_lib>gzip</compression_lib> <log_level>7</log_level> <max_concurrency>6</max_concurrency> <break_after_frontend>5</break_after_frontend> <break_after_adminhtml>30</break_after_adminhtml> <bot_lifetime>7200</bot_lifetime> </redis_session> </global> [...] </config>
However, now with the Redis configuration removed it's
<config> <global> [...] <session_save>db</session_save> </global> [...] </config>
The problem is that it looks like Redis sessions are still being used. For every connection a new exception is being logged.
Connection to Redis failed after 1 failures.
Unable to connect to Redis; falling back to MySQL handler
So it looks like even though the Redis configuration has been removed, it's still not told that it shouldn't be using Redis anymore, either.
Is there a way to force it back to using MySQL sessions?