service tabs is empty

[GitzJoey]

hi just recently (after dietpi upgrade 9.6.1 the service tab of dashboard suddenly become blank

here's the console output

tested in Firefox and Edge, both yield the same

from journalctl

[MichaIng]

Is this the nightly or stable version of dietpi-dashboard? I checked the code but could not find where this error message is produced. Best match is: https://github.com/ravenclaw900/DietPi-Dashboard/blob/main/src/page_handlers.rs#L240

However, that would mean that it tried to run systemctl get failed name, while it should have done something like systemctl start apache2 if you use start/stop services with this page.

Also not sure where the frontent calls eval(), but it is generated.

Also, a DietPi update does not update the dashboard (unless you did not have v0.6.2 yet, which as a security patch). Dud you try to restart it already?

systemctl restart dietpi-dashboard

[GitzJoey]

based on the footer

and yes restart, even reboot already done but still empty

this might be the source, i'm not sure its usefull

i found that this issue is caused when Vue.js devtools addons is enabled

I also tried to disable all the addons in my FF the error is gone but the services stilll empty

tried in edge (without any addons) also failed

I tried to turn on debug, i only have incoming body is empty

somehow the websocket for service is returning empty array

[GitzJoey]

I found the issue, is because dietpi-services status returning something like this

once i fix the fail2ban, and running properly and the dietpi-services status returning without any error, the websocket now returning array

would be good if can catch this or maybe returning some error messages

can close this issue, thanks for the attentions

[MichaIng]

Oh, so it does not gracefully deal with the status output for failed services. But also, the output indeed looks weird. I was expecting it to show "fail2ban failed (Result: exit-code)" on the first line, and this "x fail2ban.service - Fail2Ban Service" stuff on a next line. I guess that way, also the dashboard would catch it properly. Basically some characters, including the newline, are missing.

... checking back the dietpi-services code: Indeed the shortened line is replaced with the full output in case of a failure, instead of appending the full output. For the dashboard, it would make sense to append the full output, so that the dashboard can scrape the "correct" lines by their prefix. Or better some machine-readable flag like we added it for dietpi-software, with a more consistent and simpler to parse output.