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#65908 - [tinyproxy] fails to start properly with systemd

Attached to Project: Community Packages
Opened by Ignacio Serrano (ignic) - Friday, 20 March 2020, 18:13 GMT
Last edited by freswa (frederik) - Friday, 20 March 2020, 20:31 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 3
Private No

Details

The tinyproxy.service contains the following parameter:
PIDFile=/run/tinyproxy/tinyproxy.pid

But the default /etc/tinyproxy/tinyproxy.conf has the parameter "PidFile" commented and, according to the same file, "If not specified, no pidfile will be written". Moreover, the pid file defined is in a different path:
#PidFile "/var/run/tinyproxy/tinyproxy.pid"

As a result, systemctl fails to start the service properly:
# systemctl start tinyproxy.service
Job for tinyproxy.service failed because a timeout was exceeded.
See "systemctl status tinyproxy.service" and "journalctl -xe" for details.

$ systemctl status tinyproxy.service
[...] systemd[1]: tinyproxy.service: Can't open PID file /run/tinyproxy/tinyproxy.pid (yet?) after start: Operation not permitted

Uncommenting the PidFile parameter in tinyproxy.conf and setting it to the right path fixes the problem:
PidFile "/run/tinyproxy/tinyproxy.pid"
This task depends upon

Loading...