Do not install packages manually. Could it be that your repositories on the server are outdated, Martin? When you add channels and repositories via spacewalk-common-channels they are not configured to sync automatically. So it could be you are using an old version of the client tools, with an old prometheus. Please check. If that is the case, you have two alternatives: 1. Launch a manual sync each time there's a new Uyuni version 2. Configure scheduled syncing for the repositories (and force a manual sync now). Best regards. On jueves, 23 de abril de 2020 12:48:00 (CEST) João Cavalheiro wrote:
Hello Martin,
Your Prometheus version seems to be older than the one we have on Uyuni, and coming from a different repository (Haupt-Repository?).
Can you please try to manually install the package from `https://software.opensuse.org//download.html?project=systemsmanagement%3AUy uni%3AStable&package=golang-github-prometheus-prometheus` and check if it solves the problem?
Best regards, João
On 23/04/20 11:27, Martin Willisegger wrote:
Hello João
I used the command from the guide to install prometheus: zypper in golang-github-prometheus-prometheus
This "prometheus" related packes are installed: uyuni:/var/log # zypper se --installed -s prometheus Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository ---+----------------------------------------+---------+------------------- +--------+------------------------------------------------
i+ | golang-github-prometheus-alertmanager | package | 0.16.2-lp151.15.1 | x86_64 | Server Monitoring Software (openSUSE_Leap_15.1) i | golang-github-prometheus-node_exporter | package | 0.18.1-1.1.uyuni | x86_64 | uyuni-server-stable i+ | golang-github-prometheus-prometheus | package | 2.7.1-lp151.1.4 | x86_64 | Haupt-Repository i+ | golang-github-prometheus-promu | package | 0.5.0-lp151.6.1 | x86_64 | Server Monitoring Software (openSUSE_Leap_15.1) i | prometheus-client-java | package | 0.3.0-1.2.uyuni | noarch | uyuni-server-stable i | prometheus-exporters-formula | package | 0.5-3.1.uyuni | noarch | uyuni-server-stable i | prometheus-formula | package | 0.2-1.1.uyuni | noarch | uyuni-server-stable i | prometheus-jmx_exporter | package | 0.3.1-3.3.uyuni | noarch | uyuni-server-stable i | prometheus-jmx_exporter-tomcat | package | 0.3.1-3.3.uyuni | noarch | uyuni-server-stableLoading repository data...
Best regards, Martin
Am 23.04.20 um 10:43 schrieb João Cavalheiro:
Hello Martin,
In order to use the Service Discovery feature, you have to use the Prometheus version provided in the Uyuni Client Tools channel, which has a specific extension to support this.
Can you confirm which version you have installed?
Best regards, João
On 22/04/20 22:08, Martin Willisegger wrote:
Hello everyone
I have just updated my older (4.0.x) uyuni installation on openSuSE Leap 15.1 to version 2020.04.
Basically everything worked as before after that. I use the installation mainly for educational purposes, since we just bought a SuSE Manager license at work and I will have to familiarize myself with it in the future.
I have now tried to set up the monitoring using this guide: https://www.uyuni-project.org/uyuni-docs/uyuni/administration/monitoring .html
I tried to install the Prometheus service once via zypper and later also via the Web GUI. The installation worked with both variants, but Prometheus will no longer start if you enter the configuration as described in the manual.
The problem seems to be this area: # Managed systems metrics: - job_name: 'mgr-clients' uyuni_sd_configs: - host: "http://server.url" username: "admin" password: "admin"
Journalctl then shows the following error after a restart of Prometheus and the service dies immediately:
Apr 22 22:21:11 uyuni systemd[1]: Started Monitoring system and time series database. -- Subject: Unit prometheus.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com