Hi guys,
We have moodle version 4.5.1 installed in a debian server, we were previously using dbsessions, but we switched to file sessions following the official documentation present in https://docs.moodle.org/405/en/Session_handling#Use_database_for_session_information and noticed that the sessions were being saved to both the sessions folder and the database sessions table.
Is this normal? What can we do to prevent the sessions from being saved to the database?
Are you sure that the sessions are being stored to the database? I think you'll find that they are not. Only the session identifier is stored in the table if you are not using db sessions. And that is normal.
I've said this a few times recently, but I would strongly recommend you consider moving to Redis for sessions.
I've said this a few times recently, but I would strongly recommend you consider moving to Redis for sessions.
Dear @Howard MIller.
Thanks for the clarifications. We're considering using redis for sessions but needed to fix session timout issues. The confusion standed for the fact that in a new installation the sessions table is not created but in an existing one using db sessions and then switching to file sessions the sessions table kept being used.
Thanks for the clarifications. We're considering using redis for sessions but needed to fix session timout issues. The confusion standed for the fact that in a new installation the sessions table is not created but in an existing one using db sessions and then switching to file sessions the sessions table kept being used.
Reminded me of 'sessions' table gets populated, 'dbsessions' is not set [Moodle 4.1.15+]. No, it is not resolved yet.
