Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35283 - [shorewall] systemd service file fails to start

Attached to Project: Community Packages
Opened by Biro Balazs (scar) - Tuesday, 14 May 2013, 19:21 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 15 May 2013, 07:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Since today's update shorewall did not wanted to start up.
Log here:

máj 14 21:03:44 router systemd[452]: Failed at step EXEC spawning /usr/sbin/shorewall: No such file or directory
-- Subject: Process /usr/sbin/shorewall could not be executed
-- The process /usr/sbin/shorewall could not be executed and failed.
máj 14 21:03:44 router systemd[1]: shorewall.service: main process exited, code=exited, status=203/EXEC


Additional info:

shorewall 4.5.16.1-2 (older one was 4.5.15-1)

steps to reproduce: upgrade shorewall

*****

as you can see, the systemd service file tries to start /usr/sbin/shorewall but the binary is at /usr/bin/shorewall, so modifying the service file solves the problem

could you fix it, please?
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 15 May 2013, 07:59 GMT
Reason for closing:  Works for me
Additional comments about closing:  The service file in 4.5.16.1-2 has the correct path.
Comment by Evangelos Foutras (foutrelis) - Tuesday, 14 May 2013, 20:21 GMT
$ grep bin /usr/lib/systemd/system/shorewall.service
ExecStart=/usr/bin/shorewall $OPTIONS start
ExecStop=/usr/bin/shorewall $OPTIONS stop

Have you overridden shorewall.service by copying it to /etc/systemd/system or something?

Also make sure you have reloaded all unit files (systemctl --system daemon-reload).
Comment by Biro Balazs (scar) - Wednesday, 15 May 2013, 07:09 GMT
I've directly edited the service file (/usr/lib/systemd/system/shorewall.service)
Now it is fine.

I just had to reboot? In that case, sorry for reporting...

Loading...