tickets #123828
open
- Private changed from Yes to No
- Related to tickets #123133: metrics.o.o: /var/log/messages flooded with GB of influxd messages added
- Assignee set to witekbedyk
- Related to action #159669: No new openQA data on metrics.opensuse.org since o3 migration to PRG2 size:S added
I only maintain the access metrics service on metrics.o.o. and had never touched the others.
From what I can see in the systemd journal the osrt-metrics@openSUSE:Factory.service
fails when trying to connect to review.tumbleweed.boombatower.com
[1]. Is this service maintained? Do we have a replacement?
If not, we could try dropping release metrics and see if the rest of the script works.
[1] https://github.com/openSUSE/openSUSE-release-tools/blob/master/metrics_release.py#L8
witekbedyk wrote in #note-6:
I only maintain the access metrics service on metrics.o.o. and had never touched the others.
From what I can see in the systemd journal the osrt-metrics@openSUSE:Factory.service
fails when trying to connect to review.tumbleweed.boombatower.com
[1]. Is this service maintained? Do we have a replacement?
I doubt that service is ever coming back; IIRC it was mostly used to try to give a 'stability score' to snapshots (which was never really reliable) - the rest of the metrics should be ok (i.e review/SR graphs, …)
I have commented out the line in the script responsible for getting metrics from boombatower
service. Now we get the following error message:
Aug 06 12:28:42 metrics osrt-metrics[17510]: urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.opensuse.org', port=None): Max retries exceeded with url: /search/project?match=starts-with%28remoteurl%2C+%22http%22%29 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fae7b618390>: Failed to establish a new connection: [Errno 101] Network is unreachable',))
That smells like a missing firewall rule to allow outgoing traffic to api.o.o.
@crameleon, can you please have a look?
Going by #159669 there seem to be more resources the maintainer of the machine never requested access to, I suggest them to review the full service requirements of the machine and to open a ticket with me requesting all policies at once.
Also, review.tumbleweed.boombatower.com is reachable from the internet for me, whilst I don't know about this service, I wouldn't conclude it isn't maintained from it not being reachable from within a restricted network. :)
crameleon wrote in #note-10:
Also, review.tumbleweed.boombatower.com is reachable from the internet for me, whilst I don't know about this service, I wouldn't conclude it isn't maintained from it not being reachable from within a restricted network. :)
review.tumbleweed.boombatower.com is defunct, last update dates back to 2021-07-12 - underlying issue for that is #95756;
Also available in: Atom
PDF