On Thu, 21 Nov 2013 04:00, Patrick Shanahan <paka@...> wrote:
- Cristian Rodríguez crrodriguez@opensuse.org [11-20-13 20:18]:
El 20/11/13 21:46, Patrick Shanahan escribió:
- Cristian Rodríguez crrodriguez@opensuse.org [11-20-13 18:51]:
El 20/11/13 20:33, Patrick Shanahan escribió:
Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1
Is the daemon configuration file correct ? it exited cleanly with EXIT_FAILURE .
I am presently running privoxy via --no-daemon and it is active and showing no errors. It ran successfully for years until the 13.1 update. If you are referring to a file other than /var/lib/privoxy/etc/config, please tell me which,
I am refering to the file which is being read by privoxy in the unit file, that is /etc/privoxy/config
I do have /etc/privoxy/config, but:
21:57 Crash: ~ # rpm -ql privoxy
[snip]
/etc/privoxy
THIS IS A LINK (points to /var/lib/privoxy/etc)
[snip]
/var/lib/privoxy/etc /var/lib/privoxy/etc/config
THERE IS THE REAL FILE
/var/lib/privoxy/log
THE LOG DIR
/var/lib/privoxy/var/log /var/lib/privoxy/var/log/privoxy
LINK (points to /var/lib/privoxy/log)
The files that will have the most interesting infos are:
1. The main config file: /var/lib/privoxy/etc/config (also reachable throu /etc/privoxy/config)
2. The logfile written by privoxy itself, defaults to: /var/lib/privoxy/log/logfile
For the config file, search for the lines with
logdir (/log|/var/log/privoxy= logfile logfile # must exist or no logging at all
debug [num] # multiple lines, will be added up as bitfield debug 4096 # 4096 and 8192 are the minimum until privoxy debug 8192 # runs smootly
Also have a look inside the service file: /usr/lib/systemd/system/privoxy.service
The entries Type=
my handwritten file for 12.3 has Type=forking PIDFile=/var/run/privoxy.pid WorkingDirectory=/var/lib/privoxy ExecStart=/usr/sbin/privoxy --user privoxy.privoxy --pidfile /var/run/privoxy.pid --chroot /etc/config ExecReload=/bin/kill -USR1 $MAINPID
On instict I'd say something is wrong with the config. But if the logfile exists, that should give you some insights.
Otherwise, make sure that the 'logfile' entry exists, and the 'debug' lines with 4096 and 8192 are not commented out, and try again, and look at the privoxy logfile for hints.
- Yamaban.