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
This method finds the latest backup by looking at the zip files containing the date found in the client's DIRAC/Configuration/Version.
This version is distributed by the client by the CS, so there's no real reason it would be wrong.
Except when a slave is found dead.
In that case, a new version is generated:
@400000006756768d1d106ff4.s-57426-2024-12-09 04:46:50 UTC Configuration/Server [140072925378112] WARN: Found dead slave dips://speen.nikhef.nl:9135/Configuration/Server
@400000006756768d1d106ff4.s:57428:2024-12-09 04:46:51 UTC Configuration/Server [140072925378112] INFO: Generated new version 2024-12-09 04:46:51.020183
But this version is never actually committed (and we do not want to). So there's no backup file corresponding to that date.
The text was updated successfully, but these errors were encountered:
fstagni
changed the title
Cannot update CS after finding dead CS slave
Cannot update CS after finding dead CS worker
Dec 19, 2024
When updating the CS from the WebApp, we occasionally get
This is due to the CS not finding a correct backup in
DIRAC/src/DIRAC/ConfigurationSystem/private/ServiceInterfaceBase.py
Line 267 in c4b7a6e
This method finds the latest backup by looking at the zip files containing the date found in the client's
DIRAC/Configuration/Version
.This version is distributed by the client by the CS, so there's no real reason it would be wrong.
Except when a slave is found dead.
In that case, a new version is generated:
But this version is never actually committed (and we do not want to). So there's no backup file corresponding to that date.
The text was updated successfully, but these errors were encountered: