Hi, Yup, that’s why. The systemd service file is not dynamic and does not take into account the actual install path. You may be able to use systemd to run frr as your user, in your home, by modifying the paths in the service file. However, that is not really what this service file is meant for. Depending on how you configured your frr build, just changing the various paths of the service might be enough. frrinit.sh might give you some trouble though, as this script is rather huge and convoluted. Good luck! Alexis PS: don’t forget the ML in your CCs ;)
Le 9 déc. 2019 à 14:05, <ian.2.oakley@bt.com> <ian.2.oakley@bt.com> a écrit :
Hi Alexis,
I copied the frr.service file into /etc/system/system and then ran sudo service frr start. That gave me the following: Job for frr.service failed because the control process exited with error code. See "systemctl status frr.service" and "journalctl -xe" for details.
Running systemctl status frr.service gave me: frr.service - FRRouting Loaded: loaded (/etc/systemd/system/frr.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-12-09 13:00:29 GMT; 11s ago Docs: https://frrouting.readthedocs.io/en/latest/setup.html Process: 16172 ExecStart=/usr/lib/frr/frrinit.sh start (code=exited, status=203/EXEC)
Dec 09 13:00:29 IanRed systemd[1]: Starting FRRouting... Dec 09 13:00:29 IanRed systemd[16172]: frr.service: Failed to execute command: No such file or directory Dec 09 13:00:29 IanRed systemd[16172]: frr.service: Failed at step EXEC spawning /usr/lib/frr/frrinit.sh: No such file or directory Dec 09 13:00:29 IanRed systemd[1]: frr.service: Control process exited, code=exited status=203 Dec 09 13:00:29 IanRed systemd[1]: frr.service: Failed with result 'exit-code'. Dec 09 13:00:29 IanRed systemd[1]: Failed to start FRRouting. Dec 09 13:00:29 IanRed systemd[1]: frr.service: Triggering OnFailure= dependencies. Dec 09 13:00:29 IanRed systemd[1]: frr.service: Failed to enqueue OnFailure= job: No such file or directory
The install directory for my FRR install is in /home/user/ - does that explain anything?
Regards, Ian
-----Original Message----- From: Alexis Bauvin <abauvin@scaleway.com> Sent: 09 December 2019 12:55 To: Oakley,I,Ian,TUS2 R <ian.2.oakley@bt.com> Cc: frog@lists.frrouting.org Subject: Re: [FROG] Failed to start frr.service: Unit frr.service not found
Hi,
This is a SystemD unit file. It needs to be placed in /etc/systemd/system for systemd to find it and start frr.
Alexis
Le 9 déc. 2019 à 13:07, <ian.2.oakley@bt.com> <ian.2.oakley@bt.com> a écrit :
Hi,
I installed FRR on my Ubuntu virtual machine from source, hoping to use it with CORE for multicast routing with PIM. However, I haven’t been able to manage even that; when I attempt to start the FRR service (sudo service frr start) I am given the error message in the subject (Failed to start frr.service: Unit frr.service not found.) This is despite me running the command in my /frr/tools directory where frr.service is located. Am I missing something here?
Best regards, Ian Oakley
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog