FS#78349 - [tinyproxy] systemd unit won't start

Attached to Project: Community Packages
Opened by oleg burchakov (archetype) - Monday, 01 May 2023, 11:11 GMT
Last edited by Toolybird (Toolybird) - Monday, 01 May 2023, 20:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

...
==== AUTHENTICATION COMPLETE ====
Job for tinyproxy.service failed because a timeout was exceeded.
See "systemctl status tinyproxy.service" and "journalctl -xeu tinyproxy.service" for details.
...

...
may 01 14:00:58 creationcore systemd[1]: Starting Tinyproxy Web Proxy Server...
░░ Subject: A start job for unit tinyproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit tinyproxy.service has begun execution.
░░
░░ The job identifier is 1141.
may 01 14:00:58 creationcore systemd[1]: tinyproxy.service: Can't open PID file /run/tinyproxy/tinyproxy.pid (yet?) after start: Bad file descriptor
may 01 14:00:58 creationcore tinyproxy[3009]: Initializing tinyproxy ...
may 01 14:00:58 creationcore tinyproxy[3009]: Reloading config file
may 01 14:00:58 creationcore tinyproxy[3009]: Added address [127.0.0.1] to listen addresses.
may 01 14:00:58 creationcore tinyproxy[3009]: Setting "Via" header to 'tinyproxy'
may 01 14:00:58 creationcore tinyproxy[3009]: Reloading config file finished
may 01 14:00:58 creationcore tinyproxy[3009]: listen_sock called with addr = '127.0.0.1'
may 01 14:00:58 creationcore tinyproxy[3009]: trying to listen on host[127.0.0.1], family[2], socktype[1], proto[6]
may 01 14:00:58 creationcore tinyproxy[3009]: listening on fd [0]
may 01 14:00:58 creationcore tinyproxy[3009]: Now running as group "tinyproxy".
may 01 14:00:58 creationcore tinyproxy[3009]: Now running as user "tinyproxy".
may 01 14:00:58 creationcore tinyproxy[3009]: Setting the various signals.
may 01 14:00:58 creationcore tinyproxy[3009]: Starting main loop. Accepting connections.
may 01 14:02:28 creationcore systemd[1]: tinyproxy.service: start operation timed out. Terminating.
may 01 14:02:28 creationcore tinyproxy[3009]: Shutting down.
may 01 14:02:28 creationcore tinyproxy[3009]: trying to bring down 0 threads...
may 01 14:02:28 creationcore systemd[1]: tinyproxy.service: Failed with result 'timeout'.
...


The reason is that PidFile is disabled in config.
After this change:

...
diff --git a/tinyproxy/tinyproxy.conf b/tinyproxy/tinyproxy.conf
index 38a879f..f98bd5f 100644
--- a/tinyproxy/tinyproxy.conf
+++ b/tinyproxy/tinyproxy.conf
@@ -124,7 +124,7 @@ LogLevel Info
# can be used for signalling purposes.
# If not specified, no pidfile will be written.
#
-#PidFile "/var/run/tinyproxy/tinyproxy.pid"
+PidFile "/run/tinyproxy/tinyproxy.pid"

#
# XTinyproxy: Tell Tinyproxy to include the X-Tinyproxy header, which
...

tinyproxy starts successfully.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 01 May 2023, 20:01 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#65908 

Loading...