Failed to start Fancy Service Daemon.

[dumprop]

$ sudo systemctl enable --now fancy fancy-sleep
Job for fancy.service failed because the control process exited with error code.
See "systemctl status fancy.service" and "journalctl -xeu fancy.service" for details.

$ systemctl status fancy.service
× fancy.service - Fancy Service Daemon
     Loaded: loaded (/usr/local/lib/systemd/system/fancy.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2021-11-04 17:56:48 +03; 16s ago
    Process: 6271 ExecStart=/usr/bin/fancyd (code=exited, status=203/EXEC)
   Main PID: 6271 (code=exited, status=203/EXEC)
        CPU: 1ms

Nov 04 17:56:48 fedora systemd[1]: fancy.service: Scheduled restart job, restart counter is at 4.
Nov 04 17:56:48 fedora systemd[1]: Stopped Fancy Service Daemon.
Nov 04 17:56:48 fedora systemd[1]: fancy.service: Start request repeated too quickly.
Nov 04 17:56:48 fedora systemd[1]: fancy.service: Failed with result 'exit-code'.
Nov 04 17:56:48 fedora systemd[1]: Failed to start Fancy Service Daemon.

$ journalctl -xeu fancy.service
░░ 
░░ An ExecStart= process belonging to unit fancy.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 203.
Nov 04 17:56:47 fedora systemd[1]: fancy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit fancy.service has entered the 'failed' state with result 'exit-code'.
Nov 04 17:56:47 fedora systemd[1]: Failed to start Fancy Service Daemon.
░░ Subject: A start job for unit fancy.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit fancy.service has finished with a failure.
░░ 
░░ The job identifier is 6960 and the job result is failed.
Nov 04 17:56:48 fedora systemd[1]: fancy.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit fancy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Nov 04 17:56:48 fedora systemd[1]: Stopped Fancy Service Daemon.
░░ Subject: A stop job for unit fancy.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit fancy.service has finished.
░░ 
░░ The job identifier is 7072 and the job result is done.
Nov 04 17:56:48 fedora systemd[1]: fancy.service: Start request repeated too quickly.
Nov 04 17:56:48 fedora systemd[1]: fancy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit fancy.service has entered the 'failed' state with result 'exit-code'.
Nov 04 17:56:48 fedora systemd[1]: Failed to start Fancy Service Daemon.
░░ Subject: A start job for unit fancy.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit fancy.service has finished with a failure.
░░ 
░░ The job identifier is 7072 and the job result is failed.

[saidsay-so]

Can you run journalctl -xeu fancy.service | grep fancyd -C10, please?

[dumprop]

journalctl -xeu fancy.service | grep fancyd -C10

yes, of course, thank you for your quick response to issues Logs: https://pastebin.com/kkaP36Gv

[saidsay-so]

Thanks! So it tries to load NBFC settings, but it fails because a field is missing. It should normally not stop in this case, and just try to load default settings, but it seems that I have to fix this. Can you rename /etc/NbfcService/NbfcServiceSettings.xml to /etc/NbfcService/NbfcServiceSettings.xml.bak and try restarting it again?

[dumprop]

Thanks! So it tries to load NBFC settings, but it fails because a field is missing. It should normally not stop in this case, and just try to load default settings, but it seems that I have to fix this. Can you rename /etc/NbfcService/NbfcServiceSettings.xml to /etc/NbfcService/NbfcServiceSettings.xml.bak and try restarting it again?

That correct, thanks!