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
Describe the bug
It's not the first time I notice this behavior, but now I manage to collect the required artifacts.
When WMAgent components crash and their worker thread is terminated, example:
2024-08-29 21:30:51,756:140034193299200:INFO:BaseWorkerThread:Worker thread <WMComponent.ErrorHandler.ErrorHandlerPoller.ErrorHandlerPoller object at 0x7f5c48a74310> terminated
they are still reported as running with manage status script:
(WMAgent-2.3.4.3) [xxx@cmsgwms-xxx:current]$ manage status
Component:ErrorHandler Running:1166
...
which actually makes sense, as the process still exists:
This behavior is different than the one we used to have in the RPM model, which would bring the component down (and exit the process) if the component only had that one worker thread (which is the case for ErrorHandler).
Note that the component (worker thread) is properly monitored in WMStats, which correctly says that the component is down.
How to reproduce it
Perhaps as simple as making a component to crash.
Expected behavior
If the component has a single worker thread (which is the most majority of the WMAgent components), whenever a worker thread gets terminated, it should terminate the process as well and properly report that component as down in the manage script.
Additional context and error message
None
The text was updated successfully, but these errors were encountered:
Impact of the bug
WMAgent (docker model)
Describe the bug
It's not the first time I notice this behavior, but now I manage to collect the required artifacts.
When WMAgent components crash and their worker thread is terminated, example:
they are still reported as running with manage status script:
which actually makes sense, as the process still exists:
This behavior is different than the one we used to have in the RPM model, which would bring the component down (and exit the process) if the component only had that one worker thread (which is the case for ErrorHandler).
Note that the component (worker thread) is properly monitored in WMStats, which correctly says that the component is down.
How to reproduce it
Perhaps as simple as making a component to crash.
Expected behavior
If the component has a single worker thread (which is the most majority of the WMAgent components), whenever a worker thread gets
terminated
, it should terminate the process as well and properly report that component as down in the manage script.Additional context and error message
None
The text was updated successfully, but these errors were encountered: