Project

General

Profile

Actions

Bug #24017

open

Webapp can fail to start with null sessionid error

Added by Clark ANDRIANASOLO 3 months ago. Updated 3 days ago.

Status:
Pending release
Priority:
N/A
Category:
Web - Maintenance
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Medium
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

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.


Subtasks 1 (0 open1 closed)

Bug #24755: In case a NULL was introduced earlier in sessionid, login is impossibleResolvedClark ANDRIANASOLOActions

Related issues 2 (0 open2 closed)

Related to Rudder - User story #23440: Add users table to better track user and sessionsReleasedVincent MEMBRÉActions
Related to Rudder - Bug #23920: Lift Async system is not able to find spring SecurityContextHolderReleasedVincent MEMBRÉActions
Actions #1

Updated by Clark ANDRIANASOLO 3 months ago

  • Related to User story #23440: Add users table to better track user and sessions added
Actions #2

Updated by François ARMAND 3 months ago

  • Related to Bug #23920: Lift Async system is not able to find spring SecurityContextHolder added
Actions #3

Updated by François ARMAND 3 months ago

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

Actions #4

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.0~alpha1 to 8.1.0~beta1
Actions #5

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 8.1.0~beta1 to 8.1.0~beta2
Actions #6

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 8.1.0~beta2 to 8.1.0~rc1
Actions #7

Updated by Vincent MEMBRÉ 17 days ago

  • Target version changed from 8.1.0~rc1 to 8.1.0
Actions #8

Updated by Clark ANDRIANASOLO 12 days ago

  • Assignee changed from François ARMAND to Clark ANDRIANASOLO
  • Target version changed from 8.1.0 to 7.3.14
Actions #9

Updated by Clark ANDRIANASOLO 12 days ago

  • Status changed from New to In progress
Actions #10

Updated by Clark ANDRIANASOLO 12 days ago

  • 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
Actions #11

Updated by Clark ANDRIANASOLO 4 days ago

  • Status changed from Pending technical review to Pending release
Actions #12

Updated by François ARMAND 4 days ago

  • Subtask #24755 added
Actions

Also available in: Atom PDF