Open mamedin opened 2 hours ago
As workaround I added prometheus monitoring to MCPClients in localhost:
ARCHIVEMATICA_MCPCLIENT_MCPCLIENT_PROMETHEUS_BIND_PORT=7998
ARCHIVEMATICA_MCPCLIENT_MCPCLIENT_PROMETHEUS_BIND_ADDRESS=127.0.0.1
I suspect we are missing a conditional in some places like this:
https://github.com/artefactual/archivematica/blob/qa/1.x/src/MCPClient/lib/client/pool.py#L158
We should check the monitoring is enabled before running metrics functions
Expected behaviour
Current behaviour
Sometimes MCPclient tries to refresh the prometheus database (I suppose when worker pool member is restarted because reaching the limit (new AM1.16 feature: pool of workers))
It is happening at the transfer start. And it is not happening in all transfers.
MCPServer log error:
MCPCLient log in syslog:
Steps to reproduce
It isn't easy to reproduce, it only happened 1 time on each 2 system pipelines. So I suspect it only happens when restarting a worker.
Your environment (version of Archivematica, operating system, other relevant details)
Rocky 9, AM1.16
SS separated VM 2 pipelines
The issue happened in both pipelines (Identical config)
For Artefactual use:
Before you close this issue, you must check off the following: