On 6/6/09, Per Jessen wrote:

...

I'm trying to get privoxy to run, but when I issue /usr/sbin/privoxy start or /etc/init.d/privoxy start it tries to start and then says "failed".

Have you checked the various logs for error messages? Sounds like a config problem.

/Per

Thanks, but I don't know which logs to check. I got the config file from this tutorial http://www.junauza.com/2009/03/three-easy-steps-to-set-up-anonymous.html and it's listed below. I noticed after checking the tutorial that it's for Ubuntu, maybe some of the info in the config file does not work for Suse. Thanks, Gustav snipped from the tutorial: I "Then, overwrite the entire content of /etc/privoxy/config with this configuration file: # Generally, this file goes in /etc/privoxy/config forward-socks4a / 127.0.0.1:9050 . confdir /etc/privoxy logdir /var/log/privoxy actionsfile standard actionsfile default actionsfile user filterfile default.filter debug 4096 debug 8192 user-manual /usr/share/doc/privoxy/user-manual listen-address 127.0.0.1:8118 toggle 1 enable-remote-toggle 0 enable-edit-actions 0 enable-remote-http-toggle 0 buffer-limit 4096 " -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 6 June 2009 14:02:21 Per Jessen wrote:

Gustav Degreef wrote:

...

On 6/6/09, Per Jessen wrote:

...

...

I'm trying to get privoxy to run, but when I issue /usr/sbin/privoxy start or /etc/init.d/privoxy start it tries to start and then says "failed".

Have you checked the various logs for error messages? Sounds like a config problem.

/Per

Thanks, but I don't know which logs to check.

To start with

/var/log/boot.msg /var/log/messages /var/log/audit/audit.log

If that doesn't reveal anything, I would run the daemon in the foreground with debug on. I'm sure privoxy has settings for that.

/Per

-- Per Jessen, Zürich (15.1°C)

In openSUSE, privoxy runs chroot. Log files can be found in the directory "/var/lib/privoxy/log". Regards, Erwin Lam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Gustav Degreef wrote:

It was suggested I start the daemon in the foreground with debug - no clue how to do that. Any further suggestions or pointers would be welcome. Thanks, Gustav

Gustav, then you go and google a bit: First stop = http://www.privoxy.org/ - "User Manual", "Command line options" >= --no-daemon So run "privoxy --no-daemon <configfile>". There doesn't seem to be a debug options. If that doesn't get privoxy running, there's bound to be error messages of some sort. /Per -- Per Jessen, Zürich (18.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Gustav Degreef wrote:

...

So run "privoxy --no-daemon <configfile>". There doesn't seem to be a debug options. If that doesn't get privoxy running, there's bound to be error messages of some sort.

/Per

Thanks, Per, that started it. The output is:

That's great - we're making progress.

privoxy --no-daemon /etc/privoxy/config Jun 06 21:47:49 Privoxy(b7d496c0) Info: loading configuration file '/etc/privoxy /config': Jun 06 21:47:49 Privoxy(b7d496c0) Info: Privoxy version 3.0.6 Jun 06 21:47:49 Privoxy(b7d496c0) Info: Program name: privoxy Jun 06 21:47:49 Privoxy(b7d496c0) Info: Listening on port 8118 for local connect ions only

So it looks like it's running just fine?

Can you give me a pointer what to do now to start it automatically? The information from the Suse SDB page said that one had to edit /etc/init.d scripts. At that point I was in way over my head, and perhaps I still am. The tutorial I read made is seem so easy, perhaps it's not. Anyway thanks for your help. Gustav

If the init-script (/etc/init.d/privoxy) doesn't start the daemon the way you did above, you probably need to amend the sysconfig - I don't have privoxy installed myself, but I'm guessing it will have a /etc/sysconfig/privoxy file with some configuration items that will determine how it is started at boot-time. What happens if you just do "rcprivoxy start"? /Per -- Per Jessen, Zürich (16.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 6/7/09, Erwin Lam wrote:

On Saturday 6 June 2009 19:21:55 Per Jessen wrote:

...

Gustav Degreef wrote:

...

...

So run "privoxy --no-daemon <configfile>". There doesn't seem to be a debug options. If that doesn't get privoxy running, there's bound to be error messages of some sort.

/Per

Thanks, Per, that started it. The output is:

That's great - we're making progress.

...

privoxy --no-daemon /etc/privoxy/config Jun 06 21:47:49 Privoxy(b7d496c0) Info: loading configuration file '/etc/privoxy /config': Jun 06 21:47:49 Privoxy(b7d496c0) Info: Privoxy version 3.0.6 Jun 06 21:47:49 Privoxy(b7d496c0) Info: Program name: privoxy Jun 06 21:47:49 Privoxy(b7d496c0) Info: Listening on port 8118 for local connect ions only

So it looks like it's running just fine?

I think so. But I haven't gotten that far to check with my browser.

...

...

Can you give me a pointer what to do now to start it automatically?

If the init-script (/etc/init.d/privoxy) doesn't start the daemon the way you did above, you probably need to amend the sysconfig - I don't have privoxy installed myself, but I'm guessing it will have a /etc/sysconfig/privoxy file with some configuration items that will determine how it is started at boot-time.

What happens if you just do "rcprivoxy start"?

It fails.

...

/Per

To see if your system is configured to start privoxy automatically, issue the command

chkconfig --list | grep privoxy

You should see some thing like

privoxy 0:off 1:off 2:off 3:on 4:off 5:on 6:off

chkconfig --list | grep privoxy privoxy 0:off 1:off 2:off 3:off 4:off 5:off 6:off Looks like that's a problem. It's configured off in all runlevels

To correct this, issue the command

insserv /etc/init.d/privoxy

Did that, with no error messages.

In addition, check that "/etc/privoxy" is a link to "/var/lib/privoxy/etc".

Yes, it is.

I also noticed that there are a few errors is your privoxy configuration file. Since under openSUSE, privoxy runs in a chroot jail, directories should be mentioned with respect to this jail, i.e.

Replace

confdir /etc/privoxy logdir /var/log/privoxy

with

confdir /etc logdir /log

Erwin Lam

OK, did that. and now it works on a reboot!!! # chkconfig --list | grep privoxy privoxy 0:off 1:off 2:off 3:on 4:off 5:on 6:off and # ps -ef | grep privoxy privoxy 4375 1 0 09:40 ? 00:00:00 /usr/sbin/privoxy --user privoxy privoxy --pidfile /var/run/privoxy.pid --chroot /etc/config root 5371 5351 0 09:42 pts/0 00:00:00 grep privoxy But now my browser can't get any web pages. But I imaging that is a configuration problem with either my browser or with the privoxy itself. Now I can start it and stop it at will and debug this problem and eventually configure privoxy to my needs. I'll follow up with the results. Thanks a lot you two for getting me going!! Gustav , -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org