[BUG] Describe the issue

[juaninditex]

Description

Describe the bug clearly and concisely.

Steps to Reproduce

1. ...In overview in a couple of sections appears this error
   Metrics data not available yet

API request failed: 500 INTERNAL SERVER ERROR

Expected Behavior

What should happen?

Screenshots (Required)

Add images to help illustrate the issue.

Environment

• Operating system:
• Software version:
• Other relevant details:

Additional Information

Add any other context about the problem here.

[juaninditex]

if you need any additional information please let me know
(you can answer in spanish if you prefer)

[MacRimi]

Hola @juaninditex que versión de ProxMenux Monitor estás usando, la estable o la beta. Ese error en principio fue resuelto y en la próxima versión estable estará aplicado. Eso solía por un desajuste entre el nombre de host y el nombre del nodo interno.

Por favor podrías confírmame la versión?

[juaninditex]

Hola Pedro, gracias por la rápida respuesta me la instalé hoy mismo con el codigo bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)"
tengo la ProxMenux Monitor v1.0.1

[MacRimi]

Prueba la versión beta, que ya es próxima a release.

Esto debería resolverse:

bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/develop/install_proxmenux_beta.sh)"

Luego cuando salga la estable, si quieres te pasa a esa rama.

[juaninditex]

gracias pro tu rapida respuesta anoche ni la vi, me acabo de instlar la neuva version y sigue con el error ProxMenux Monitor v1.0.2-beta Si te sirven logs o algo para ayudarte, dime y miro de buscarlos y enviartelos, mil gracias!!

[MacRimi]

ok vamos a ver si descubrimos donde este el fallo.

por favor ejecuta estos comandos en ese nodo y pásame el log completo

1. Ver l error 500 en el log

journalctl -u proxmenux-monitor --since "1 hour ago" | grep -i "error\|traceback\|exception\|500" | tail -50

2. Si no hay nada, ver los últimos logs del servicio directamente

journalctl -u proxmenux-monitor -n 100 | tail -80

3. Verificar si rrdtool está instalado

which rrdtool && rrdtool --version | head -1

4. Verificar estructura de directorios RRD

ls -la /var/lib/rrdcached/db/

5. Buscar archivos RRD del nodo

ls -la /var/lib/rrdcached/db/pve2-node/ 2>&1
ls -la /var/lib/rrdcached/db/pve-node-*/ 2>&1

6. Verificar el hostname

hostname

7. Verificar permisos del socket rrdcached

ls -la /var/run/rrdcached.sock 2>&1

8. Version de Proxmox

pveversion

Muchas gracias por tu colaboración.

[juaninditex]

no sé si te ayudara estos son mis resultados:
root@pve:# journalctl -u proxmenux-monitor --since "1 hour ago" | grep -i "error|traceback|exception|500" | tail -50
root@pve:# journalctl -u proxmenux-monitor -n 100 | tail -80
Apr 01 16:28:10 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: 🔧 Hardware monitoring tools:
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ ipmitool available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ sensors available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ upsc available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ libfreeipmi.so.17 loaded successfully
Apr 01 16:54:05 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard...
Apr 01 16:54:05 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 01 16:54:05 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:54:05 pve systemd[1]: proxmenux-monitor.service: Consumed 2min 12.739s CPU time, 1.1G memory peak.
-- Boot 5d30c025e7f342c2ad1e82d59e5fc717 --
Apr 01 16:55:05 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: 🔧 Hardware monitoring tools:
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ ipmitool available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ sensors available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ upsc available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 10:46:01 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard...
Apr 02 10:46:01 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 10:46:01 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 02 10:46:01 pve systemd[1]: proxmenux-monitor.service: Consumed 10min 42.094s CPU time, 1.1G memory peak.
Apr 02 10:46:01 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: 🔧 Hardware monitoring tools:
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ ipmitool available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ sensors available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ upsc available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 16:17:56 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta)...
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Killing process 317712 (ProxMenux-Monit) with signal SIGKILL.
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 16:17:56 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Consumed 6min 9.717s CPU time, 705.3M memory peak.
Apr 02 16:17:56 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: 🔧 Hardware monitoring tools:
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ ipmitool available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ sensors available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ upsc available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 16:20:32 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta)...
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Killing process 417912 (pvesh) with signal SIGKILL.
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Killing process 417913 (pvesh) with signal SIGKILL.
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 16:20:32 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Consumed 12.946s CPU time, 606.5M memory peak.
Apr 02 16:20:32 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: 🔧 Hardware monitoring tools:
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ ipmitool available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ sensors available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ upsc available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ libfreeipmi.so.17 loaded successfully
root@pve:# journalctl -u proxmenux-monitor -n 100 | tail -80
Apr 01 16:28:10 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: 🔧 Hardware monitoring tools:
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ ipmitool available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ sensors available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ upsc available
Apr 01 16:28:10 pve ProxMenux-Monitor.AppImage[2386672]: ✅ libfreeipmi.so.17 loaded successfully
Apr 01 16:54:05 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard...
Apr 01 16:54:05 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 01 16:54:05 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:54:05 pve systemd[1]: proxmenux-monitor.service: Consumed 2min 12.739s CPU time, 1.1G memory peak.
-- Boot 5d30c025e7f342c2ad1e82d59e5fc717 --
Apr 01 16:55:05 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: 🔧 Hardware monitoring tools:
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ ipmitool available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ sensors available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ upsc available
Apr 01 16:55:05 pve ProxMenux-Monitor.AppImage[1011]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 10:46:01 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard...
Apr 02 10:46:01 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 10:46:01 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard.
Apr 02 10:46:01 pve systemd[1]: proxmenux-monitor.service: Consumed 10min 42.094s CPU time, 1.1G memory peak.
Apr 02 10:46:01 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: 🔧 Hardware monitoring tools:
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ ipmitool available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ sensors available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ upsc available
Apr 02 10:46:01 pve ProxMenux-Monitor.AppImage[317710]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 16:17:56 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta)...
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Killing process 317712 (ProxMenux-Monit) with signal SIGKILL.
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 16:17:56 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:17:56 pve systemd[1]: proxmenux-monitor.service: Consumed 6min 9.717s CPU time, 705.3M memory peak.
Apr 02 16:17:56 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: 🔧 Hardware monitoring tools:
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ ipmitool available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ sensors available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ upsc available
Apr 02 16:17:56 pve ProxMenux-Monitor.AppImage[416751]: ✅ libfreeipmi.so.17 loaded successfully
Apr 02 16:20:32 pve systemd[1]: Stopping proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta)...
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Killing process 417912 (pvesh) with signal SIGKILL.
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Killing process 417913 (pvesh) with signal SIGKILL.
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Deactivated successfully.
Apr 02 16:20:32 pve systemd[1]: Stopped proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:20:32 pve systemd[1]: proxmenux-monitor.service: Consumed 12.946s CPU time, 606.5M memory peak.
Apr 02 16:20:32 pve systemd[1]: Started proxmenux-monitor.service - ProxMenux Monitor - Web Dashboard (Beta).
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: 🚀 Starting ProxMenux Monitor Dashboard...
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: 🔧 Hardware monitoring tools:
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ ipmitool available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ sensors available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ upsc available
Apr 02 16:20:32 pve ProxMenux-Monitor.AppImage[417942]: ✅ libfreeipmi.so.17 loaded successfully
root@pve:# which rrdtool && rrdtool --version | head -1
/usr/bin/rrdtool
RRDtool 1.7.2 Copyright by Tobias Oetiker tobi@oetiker.ch
root@pve:# ls -la /var/lib/rrdcached/db/
total 20
drwxr-xr-x 5 root root 4096 Jan 12 23:35 .
drwxr-xr-x 4 root root 4096 Jan 9 16:24 ..
drwxr-x--- 2 root root 4096 Jan 9 16:25 pve-node-9.0
drwxr-x--- 3 root root 4096 Jan 9 15:32 pve-storage-9.0
drwxr-x--- 2 root root 4096 Mar 27 00:02 pve-vm-9.0
root@pve:# ls -la /var/lib/rrdcached/db/pve2-node/ 2>&1
ls -la /var/lib/rrdcached/db/pve-node-*/ 2>&1
ls: cannot access '/var/lib/rrdcached/db/pve2-node/': No such file or directory
total 8
drwxr-x--- 2 root root 4096 Jan 9 16:25 .
drwxr-xr-x 5 root root 4096 Jan 12 23:35 ..
-rw-r--r-- 1 root root 0 Jan 9 16:25 pve
root@pve:# hostname
pve
root@pve:# ls -la /var/run/rrdcached.sock 2>&1
srw-rw-rw- 1 root root 0 Apr 1 16:55 /var/run/rrdcached.sock
root@pve:# pveversion
pve-manager/9.1.7/16b139a017452f16 (running kernel: 6.17.13-2-pve)
root@pve:#

[MacRimi]

Muchas gracias por el log y si se ve el motivo de que no se te muestren las grafías. El archivo RRD de tu nodo esta vacio

-rw-r--r-- 1 root root 0 Jan 9 16:25 pve

El archivo /var/lib/rrdcached/db/pve-node-9.0/pve existe pero no tiene datos. Ese es el motivo por el que las graficas de metricas fallen.

El motivo no sabría decirte bien por que, puede ser varias causas, rrdcached nunca funcionó correctamente despues de la instalacion de Proxmox, o hubo un problema de permisos que impidio escribir datos. Pero esto es extraño que ocurra

Intenta reiniciar el servicio rrdcached para que regenere el archivo:

systemctl restart rrdcached

Si despues de unos minutos el problema persiste, verifica que el archivo tenga datos:

ls -la /var/lib/rrdcached/db/pve-node-9.0/pve

Si sigue en 0 bytes, puede que necesites eliminar el archivo vacio y reiniciar rrdcached para que lo regenere:

rm /var/lib/rrdcached/db/pve-node-9.0/pve
systemctl restart rrdcached

confírmame si te funciona.