Scrutiny app does not display any information

[hook]

My YunoHost server

Hardware: Old laptop or computer
YunoHost version: 11.2.9.1 (stable)
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen | … (all of it)
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain:
If your request is related to an app, specify its name and version: scrutiny 0.7.2~ynh1

Description of my issue

I installed Scrutiny, but when I open it, I do not get any info:

The scrutiny collector log is here: hastebin

The one thing that pops up there – although oddly enough, YunoHost reports Scrutiny is working fine – is the following line (and variations of it):

time="2023-12-29T00:14:32+01:00" level=error msg="Could not retrieve device information for nvme0: exit status 2" type=metrics

On the other hand, if I ssh to the server and run smartctl --all /dev/nvme0 I do get the S.M.A.R.T. info I would expect.

Did I skip a setup step or what?

[ewilly]

Hi,

• what’s the output of smartctl --info --json /dev/nvme0 ?
• can you:
  1. add --debug at the end of the line starting with ExecStart= in the file /etc/systemd/system/scrutiny-collector.service
  2. execute systemctl daemon-reload
  3. manually start the collector with systemctl start scrutiny-collector.service
  4. check the log /var/log/scrutiny/collector.log which should be now more verbose

PS: hide or lightly modify you serial number

[hook]

@ewilly

• what’s the output of smartctl --info --json /dev/nvme0 ?

Pastebin here. (also, thanks for the S/N reminder)

• can you:
  1. add --debug at the end of the line starting with ExecStart= in the file /etc/systemd/system/scrutiny-collector.service
  2. execute systemctl daemon-reload
  3. manually start the collector with systemctl start scrutiny-collector.service
  4. check the log /var/log/scrutiny/collector.log which should be now more verbose

Pastebin here. Seems like a permission issue to me.

[ewilly]

Humm strange
Is your host 100% yunohost ? Are you running in a container ?

[hook]

Freshly built AMD64 PC, fresh install (cca. 2 weeks old), nothing else.

All I did was apt get htop, fish shell and a few such small CLI tools. Otherwise it’s very vanilla YunoHost.

The only thing I messed with the system (actually groups/permissions) was this part:

sudo su
cd /var/www/pelican
# Faire en sorte que tout les dossiers et fichiers appartiennent au groupe pelican
chown pelican:pelican -R .
# Ajouter nextcloud et www-data au groupe pelican
usermod -a -G pelican nextcloud
usermod -a -G pelican www-data
# Forcer à ce que les fichiers créés par nextcloud appartiennent toujours au groupe pelican
chmod g+s content
# Autoriser nextcloud (et incidemment www-data) à écrire dans content
chmod 770 content
chmod 660 content/* -R

from:

Suite installation pelican ssh et wireguard

Ta boîte bloque le port 22, mais te laisserait installer un client VPN sur ton ordinateur, et qui utilise un port exotique ? Je te propose plutôt de passer par Nextcloud, puisque tu es sûr que le trafic HTTPS fonctionne. Cela demande un peu de bidouille, mais j’ai pu prototyper ça. (je suis quasiment sûr d’avoir déjà évoqué cette idée sur le forum) Installe Nextcloud Changeons les droits d’accès des dossiers: sudo su cd /var/www/pelican # Faire en sorte que tout les dossiers et fichiers appa…

[ewilly]

@hook

Seems like a permission issue to me.

That’s certainly the point.

1. Can you edit /etc/systemd/system/scrutiny-collector.service and comment the 2 lines:

• CapabilityBoundingSet=~CAP_RAWIO CAP_MKNOD
• CapabilityBoundingSet=~CAP_SYS_ADMIN CAP_SYS_PTRACE CAP_SYSLOG

2. execute systemctl daemon-reload
3. manually start the collector with systemctl start scrutiny-collector.service
4. check the log /var/log/scrutiny/collector.log

[hook]

I did what you asked, and it works now, thanks

/var/log/scrutiny/collector.log now shows the S.M.A.R.T. data in JSON format and ends with:

time="2023-12-30T14:57:34+01:00" level=info msg="Publishing smartctl results for [REDACTED]\n" type=metrics
time="2023-12-30T14:57:34+01:00" level=info msg="Main: Completed" type=metrics

[ewilly]

what could be interesting now is to know which of the 2 lines or the both is necessary to comment. Knowing that i could update the app. Unfortunately i don’t own an nvme device so can’t do that myself…
can you do those tests ?

[hook]

Sure, happy to.

It turns out, only this line needs to be commented out:

# CapabilityBoundingSet=~CAP_SYS_ADMIN CAP_SYS_PTRACE CAP_SYSLOG

[hook]

BTW, and not entirely on topic – is it intended that the time in the graph in Scrutiny app is shown in UTC and not local?

(When clicking on the device, the mouse-over on when individual tests were made shows it in local time though.)

[ewilly]

Thanks
Can’t say for time sorry