Database error after update.

albertros

Hi,
I've just updated from 3.5.2 to 3.9.4 by overwriting the application as mentioned in the docs.

But now I get a worrying error in the database log:
2024-12-12 07:05:28.975 UTC [740] LOG: database system is ready to accept connections 2024-12-12 07:13:49.227 UTC [7034] reidrei@reidreidb0 ERROR: insert or update on table "login_session" violates foreign key constraint "login_session_login_id_fkey" 2024-12-12 07:13:49.227 UTC [7034] reidrei@reidreidb0 DETAIL: Key (login_id)=(0) is not present in table "login". 2024-12-12 07:13:49.227 UTC [7034] reidrei@reidreidb0 STATEMENT: commit 2024-12-12 08:29:21.426 UTC [7376] reidrei@reidreidb0 ERROR: insert or update on table "login_session" violates foreign key constraint "login_session_login_id_fkey" 2024-12-12 08:29:21.426 UTC [7376] reidrei@reidreidb0 DETAIL: Key (login_id)=(0) is not present in table "login". 2024-12-12 08:29:21.426 UTC [7376] reidrei@reidreidb0 STATEMENT: commit

What do i do now?

Thanks,

/tony

gabriel

This error message is weird. It suggests that you are trying to login with a login ID of 0, which does not exist. I have not seen this error before.

If you have a production system that needs to be running again asap, you could either rollback to a previous backup or we could find time for you on short notice to have a look via remote call.

If you require assistance, please let us know.

If you updated on a test system or have time to troubleshoot, you could first try to clear your browser cache and then try again. You would also need to go into more detail about what is happening. Do you get this error during upgrade or when somebody opens the browser? Does the browser show an error after authentication or do you not get this far?

Upgrading between 3.5.2 and 3.9.4 skipped 3 feature releases. It should work, but I would personally upgrade in smaller increments, to reduce risk.

albertros

Hi Gabriel,
Thanks, I'll try to do a sequential upgrade instead and let you know.

/tony

albertros

Hmm. Everything goes fine until I upgrade from 3.8.6 to 3.9.4. Then the database error shows up.

Kinda weird, should I update the applications before I upgrade the platform, or can I just do that afterwards?

/tony

albertros

albertros And it only happens when I log on as a user, not as admin.
The difference is that the user I log on as uses 2FA.

/tony

albertros

Okay, I get this
2024-12-12 12:31:54 websocket TRANSACTION 118575, started by login ID 0 (127.0.0.1)
In the debug log when I load the site -but before even specifying a username.

Could this be caused by R3 running behind an apache reverse proxy?

/tony

albertros

2024-12-12 12:35:52 websocket TRANSACTION 494226, started by login ID 0 (127.0.0.1) 2024-12-12 12:35:52 websocket authenticated client (login ID 0, admin: false) 2024-12-12 12:35:52 websocket failed to create login session log, ERROR: insert or update on table "login _session" violates foreign key constraint "login_session_login_id_fkey" (SQLSTATE 23503)

This comes when I enter username and password of a 2FA/enabled use, but before I enter the passcode.

gabriel

I just checked and I can reproduce this issue when I login with a MFA enabled user. But it does not block authentication, it just generates an ugly log error.

Can your users log into the system? Does everything work and you "just" get this error in the log? Or is there something wrong?

If it´s just the log error, do not worry. I think I know why this happens and it´s not critical - just a logging feature.

albertros

Hi Gabriel,
Sorry for not getting back to you sooner, a few other "very important" tasks pulled me away from this.
You're right, everything seems to be working fine except for the worrying error message in the logs.

I've updated both r3 and the applications now, is there a general order one should follow? e.g. do I have to update r3 before updating the applications or?

Thanks,

/tony

gabriel

I´ve checked the error and prepared a fix for the next patch release. There is nothing to worry about in this case, just an edge case, we´ve not considered which blocks a log entry from being created.

If you plan to update both, it´s easier to upgrade r3 first and then the apps as newer app releases are often requiring newer r3 versions. But it works either way.

albertros

gabriel Okay, thanks.
And thanks for the info re. application updating, that's actually the way i did it.

/tony