Problem with uwsgi-app@ffsync.service and new diagnostic system

My YunoHost server

Hardware: HP Microserver
YunoHost version: stable
I have access to my server : Through SSH and through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

With new version of yunohost I receive diagnostic emails containing (among others) this alert:

[ERROR] Service uwsgi-app@ffsync.service is dead :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart uwsgi-app@ffsync.service' and 'yunohost service log uwsgi-app@ffsync.service').

But my ffsync is working normally so I tried to understand what’s going on.

Checking the service with systemctl I have this result:

root@cybervalley:~# yunohost service log uwsgi-app@ffsync.service
journalctl: -- No entries --
root@cybervalley:~# systemctl status uwsgi-app@ffsync.service
● uwsgi-app@ffsync.service - ffsync uWSGI app
Loaded: loaded (/etc/systemd/system/uwsgi-app@.service; enabled; vendor prese
Drop-In: /etc/systemd/system/uwsgi-app@ffsync.service.d
Active: active (running) since Wed 2020-05-20 08:32:29 CEST; 3 days ago
Main PID: 2160 (uwsgi)
Status: "uWSGI is ready"
CGroup: /system.slice/system-uwsgi\x2dapp.slice/uwsgi-app@ffsync.service
       ├─2160 /usr/bin/uwsgi --ini /etc/uwsgi/apps-available/ffsync.ini --socket /var/run/ffsync/app.socket --logto /var/log/uwsgi/ffsync/ffsync.log
       └─2204 /usr/bin/uwsgi --ini /etc/uwsgi/apps-available/ffsync.ini --socket /var/run/ffsync/app.socket --logto /var/log/uwsgi/ffsync/ffsync.log

Warning: Journal has been rotated since unit was started. Log output is incomplete  or unavailable.

Instead with the command from the webadmin page I get

root@cybervalley:~# yunohost service status uwsgi-app@ffsync.service
configuration: unknown
description: ffsync.service uWSGI app
last_state_change: 1970-01-01 02:00:00
start_on_boot: enabled
status: dead

Hmf that seems to be because yunohost checks the status of [servicename].service … But for this service, the name is uwsgi-app@ffsync.service so that yields


which doesn’t make sense for systemd…

I’ll fix that in the core and try to tell the packagers to not name their services “something.service” and just “something”…

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.