* Yamaban firstname.lastname@example.org [11-20-13 22:35]:
On Thu, 21 Nov 2013 04:00, Patrick Shanahan <paka@...> wrote:
21:57 Crash: ~ # rpm -ql privoxy
THIS IS A LINK (points to /var/lib/privoxy/etc)
THERE IS THE REAL FILE
THE LOG DIR
LINK (points to /var/lib/privoxy/log)
The files that will have the most interesting infos are:
The main config file: /var/lib/privoxy/etc/config (also reachable throu /etc/privoxy/config)
The logfile written by privoxy itself, defaults to: /var/lib/privoxy/log/logfile
contains one line for 03-12-2011
For the config file, search for the lines with
was: logdir /log now: logdir /var/lib/privoxy/log
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
no debug was set, added 4096 and 8192
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
[Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target
[Service] Type=forking PIDFile=/run/privoxy.pid ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy /etc/privoxy/config
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.
It now starts :^)
Appears there is a problem with the new privoxy configuration not following previous installations, and with the error reporting or lack of "useful error messages".
Thanks for your and Christian's help, I am now a happy camper :^).