Hi everyone, Hi Kevin,
I was one of the users affected by the issue where the ost_session table exceeded 18GB of total size.
Figured out this issue when my server told me, oh, no space left for anything.
Couldnt even manage to DELETE certain rows from the table, hence I had to drop the entire table.
Now I've re created the table using
CREATE TABLE support_session (
id INT AUTO_INCREMENT PRIMARY KEY,
user_id INT NOT NULL,
session_data TEXT,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

But I believe that's not all I had to create, since I'm failing to login. Can you give me the correct command to regain the db? OR anyone can basically help me by doing and posting the result of the info about the table, for most cases "ost_sessions"
Thanks in advance!

      DarkTexas

      Never manually delete things..always a bad idea. If all you did was drop the table then recreating it is all you need to do. Of course you need to clear cache and cookies in the browser.

      If your session table is filling up then you are not on the latest version or your db/cron is having issues. Sessions are cleared via auto-cron/cron so if that’s not running then there are deeper issues afoot.

      Cheers.

        Correction:
        I appear to be wrong about clearing expired sessions on auto-cron. After reviewing the code, I do not see where expired sessions are cleared on auto-cron; only on normal cron. So, this means you must have a cron job setup and running to routinely clean the expired sessions.

        I will need the correct set-up for the table, as in the correct CREATE TABLE command.
        I'll investigate on the cron stuff as soon as I have regular access to the dashboard again. Thanks @KevinTheJedi!

          Write a Reply...