Bug #24017
closed
Webapp can fail to start with null sessionid error
Added by Clark ANDRIANASOLO 10 months ago.
Updated 7 months ago.
Category:
Web - Maintenance
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Description
When restarting the webapp it could occur that it fails to boot with a an error
zio.FiberFailure: SystemError(Error when saving session 'null' info for user 'username', org.postgresql.util.PSQLException: ERROR: null value in column "sessionid" of relation "usersessions" violates not-null constraint
Detail: Failing row contains (username, null, 2024-01-12 11:35:00.413+01, file, {administrator}, all, null, null).)
Restarting again the webapp seems to fix the issue so it appears like a synchronization problem regarding user and session variables.
- Related to User story #23440: Add users table to better track user and sessions added
- Related to Bug #23920: Lift Async system is not able to find spring SecurityContextHolder added
It might be a user/session problem, but since it happens at reboot, on a time when no user are trying to log, it's more likely the cleaning of open sessions that is failing.
When we reboot, for each session that was open when rudder was stopped (and so, are still open in base but clearly are not really open at an http level), we add a "close" date at reboot time. But perhaps something is broken in that closing logic.
See: bootstrap.liftweb.checks.consistency.CloseOpenUserSessions
- Target version changed from 8.1.0~alpha1 to 8.1.0~beta1
- Target version changed from 8.1.0~beta1 to 8.1.0~beta2
- Target version changed from 8.1.0~beta2 to 8.1.0~rc1
- Target version changed from 8.1.0~rc1 to 8.1.0
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Target version changed from 8.1.0 to 7.3.14
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5593
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
This can't be validated easily, so we will need to see if the problem occures again with the correction.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.14, 8.0.8 and 8.1.1 which were released today.
- Related to Bug #25123: Authentication happens twice with same session id added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by