Hide Forgot
Description of problem:systemd[1]: tinyproxy.service: main process exited, code=exited, status=71 Version-Release number of selected component (if applicable): How reproducible:Every time Steps to Reproduce: 1.Install tinyproxy 2.boot 3. Actual results: systemd[1]: tinyproxy.service: main process exited, code=exited, status=71 Expected results: tinyproxy running Additional info: by default tinyproxy has the following in it's configuration # # PidFile: Write the PID of the main tinyproxy thread to this file so it # can be used for signalling purposes. # PidFile "/var/run/tinyproxy/tinyproxy.pid" upon installing tinyproxy, the tinyproxy directory under /var/run is there... after a reboot it's not so recreating the directory and assigning ownership let's the service start again
Correct me if I'm wrong, but this could be resolved by including a tinyproxy.conf with the following contents in /etc/tmpfiles.d d /var/run/tinyproxy 0755 tinyproxy tinyproxy -
Thanks, I'll be fixing this this weekend most likely.
I had a sam problem on Fedora 15. I tried start tinyproxy and systemctl status was good, but the tinyproxy wasn't started really. The tinyproxy log said: INFO Jun 09 15:29:16 [7674]: Initializing tinyproxy ... INFO Jun 09 15:29:16 [7674]: Reloading config file INFO Jun 09 15:29:16 [7674]: Setting "Via" header to 'tinyproxy' INFO Jun 09 15:29:16 [7674]: Adding Port [443] to the list allowed by CONNECT INFO Jun 09 15:29:16 [7674]: Adding Port [563] to the list allowed by CONNECT INFO Jun 09 15:29:16 [7674]: Now running as group "tinyproxy". INFO Jun 09 15:29:16 [7674]: Now running as user "tinyproxy". But when I tried start tinyproxy directly with "-d" switch, it said: tinyproxy: Could not create file /var/run/tinyproxy/tinyproxy.pid: No such file or directory tinyproxy: Could not create PID file. So I made /var/run/tinyproxy directory (owner, group is tinyproxy!) and now it works. In the log: INFO Jun 09 15:30:20 [7723]: Initializing tinyproxy ... INFO Jun 09 15:30:20 [7723]: Reloading config file INFO Jun 09 15:30:20 [7723]: Setting "Via" header to 'tinyproxy' INFO Jun 09 15:30:20 [7723]: Adding Port [443] to the list allowed by CONNECT INFO Jun 09 15:30:20 [7723]: Adding Port [563] to the list allowed by CONNECT INFO Jun 09 15:30:20 [7723]: Now running as group "tinyproxy". INFO Jun 09 15:30:20 [7723]: Now running as user "tinyproxy". INFO Jun 09 15:31:05 [7738]: Initializing tinyproxy ... INFO Jun 09 15:31:05 [7738]: Reloading config file INFO Jun 09 15:31:05 [7738]: Setting "Via" header to 'tinyproxy' INFO Jun 09 15:31:05 [7738]: Adding Port [443] to the list allowed by CONNECT INFO Jun 09 15:31:05 [7738]: Adding Port [563] to the list allowed by CONNECT INFO Jun 09 15:31:05 [7738]: Now running as group "tinyproxy". INFO Jun 09 15:31:06 [7738]: Now running as user "tinyproxy". INFO Jun 09 15:31:06 [7738]: Creating child number 1 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 2 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 3 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 4 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 5 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 6 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 7 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 8 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 9 of 10 ... INFO Jun 09 15:31:06 [7738]: Creating child number 10 of 10 ... INFO Jun 09 15:31:06 [7738]: Finished creating all children. INFO Jun 09 15:31:06 [7738]: Setting the various signals. INFO Jun 09 15:31:06 [7738]: Starting main loop. Accepting connections. So I guess, it's 2 different problem. One is the missing directory, and the other one is the tinyproxy logging. Why tinyproxy doesn't write this pid file problem into the log?
mkdir /var/run/tinyproxy don't help, because /var/run is a tmpfs, so the directories lost in every reboot.
Same issue here with Fedora 15 and tinyproxy-1.8.2-2.fc15.x86_64 . tinyproxy is unable to start because it doesn't find the directory /var/run/tinyproxy which is lost on reboot. Is there any update coming for this?
I create a new bug to change the boot system of tinyproxy with systemd. https://bugzilla.redhat.com/show_bug.cgi?id=760474 It will resolve this one.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping