You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that EverestTimeoutError is not handled in Auth module:
Jan 24 10:51:23 everest-manager[23420]: {"SEVERITY": "ERRO", "SYSLOG_IDENTIFIER": "auth:Auth ", "CODE_FILE": "", "CODE_LINE": "", "MESSAGE": "Timeout while waiting for result of xxx->token_validator:auth_token_validator->validate_token()"}
Jan 24 10:51:23 everest-manager[23420]: terminate called after throwing an instance of 'boost::wrapexceptEverest::EverestTimeoutError'
Jan 24 10:51:23 everest-manager[23420]: what(): Timeout while waiting for result of xxx->token_validator:auth_token_validator->validate_token()
Jan 24 10:51:26 systemd-coredump[24275]: [🡕] Process 23420 (auth:Auth) of user 0 dumped core.
Jan 24 10:51:26 everest-manager[23390]: {"SEVERITY": "CRIT", "SYSLOG_IDENTIFIER": "manager ", "CODE_FILE": "", "CODE_LINE": "", "MESSAGE": "Module auth (pid: 23420) exited with status: 134. Terminating all modules."}
EVerest Domain
Authorization
Affected EVerest Module
Auth
To Reproduce
Steps to reproduce:
Call validate_token and do not reply within timeout
Anything else?
No response
The text was updated successfully, but these errors were encountered:
wku12
changed the title
Auth module crashes when validate_token timesout
Auth module crashes when validate_token times out
Jan 24, 2025
Thanks for raising this issue, that's indeed something that needs addressing. There's a slightly related PR in everest-framework that makes handling the exceptions that can occur during command calls a bit more explicit but even then the handling ultimately needs to be done in the caller. This would mean having try-catch blocks around command calls and the appropriate error handling/recovering logic.
Describe the bug
It seems that EverestTimeoutError is not handled in Auth module:
EVerest Domain
Authorization
Affected EVerest Module
Auth
To Reproduce
Steps to reproduce:
Anything else?
No response
The text was updated successfully, but these errors were encountered: