Hi. I am running SuSE (Pro) 9.0, and have have used YaST (Install and Remove Software module) to install Privoxy (version 3.0.2). However, Privoxy does not start (as it is supposed to) upon boot up (+ there's no mention of it in /var/log/boot.msg), and any attempt to reach any web site via my browser (= Konqueror configured for proxy http://127.0.0.1 at port 8118) fails with the message "Could not connect to host Proxy 127.0.0.1 at Port 8118". I have successfully installed and used various versions of Privoxy under SuSE 7.3, 8.0 and 8.2, and I do not know why I can't get it to work under 9.0. Has anyone else her encountered this problem and discovered how to cure it? All ideas will be gratefully received (but note that creating an empty /etc/rc.config file -- which was necessary to get Privoxy working under SuSE 8.2 -- does NOT help). Michael Alachouzos alacos@equitonica.org http://equitonica.org Date (dd/mm/yyyy) = 11/25/03
* SMD Alachouzos
I am running SuSE (Pro) 9.0, and have have used YaST (Install and Remove Software module) to install Privoxy (version 3.0.2).
However, Privoxy does not start (as it is supposed to) upon boot up (+ there's no mention of it in /var/log/boot.msg), and any attempt to reach any web site via my browser (= Konqueror configured for proxy http://127.0.0.1 at port 8118) fails with the message "Could not connect to host Proxy 127.0.0.1 at Port 8118".
I have successfully installed and used various versions of Privoxy under SuSE 7.3, 8.0 and 8.2, and I do not know why I can't get it to work under 9.0. Has anyone else her encountered this problem and discovered how to cure it?
All ideas will be gratefully received (but note that creating an empty /etc/rc.config file -- which was necessary to get Privoxy working under SuSE 8.2 -- does NOT help).
Appears that you do not have privoxy running. You need to start as root: /usr/sbin/privoxy /etc/privoxy/config Privoxy provides the connection at 8118. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Tue, 25 Nov 2003 15:57:12 -0500, Patrick Shanahan wrote:
�Appears that you do not have privoxy running. �You need to start as �root: �/usr/sbin/privoxy /etc/privoxy/config
�Privoxy provides the connection at 8118.
Yes -- but my problem is precisely that it doesn't start running. It's meant to start automatically at boot-up, but this just doesn't happen. Do you know what file(s) to configure/edit -- and how -- in order to get it to start? SMD (Michael) Alachouzos alacos@equitonica.org http://equitonica.org Date (dd/mm/yyyy) = 11/25/03
* SMD Alachouzos
On Tue, 25 Nov 2003 15:57:12 -0500, Patrick Shanahan wrote:
?Appears that you do not have privoxy running. ?You need to start as ?root: ?/usr/sbin/privoxy /etc/privoxy/config
?Privoxy provides the connection at 8118.
Yes -- but my problem is precisely that it doesn't start running. It's meant to start automatically at boot-up, but this just doesn't happen. Do you know what file(s) to configure/edit -- and how -- in order to get it to start?
Please configure your editor to provide line breaks <75 chars. tks Since it needs the route to the config file provided, I start it in /etc/init.d/boot.local, but this is for SuSE 8.1. I don't know about SUSE 9.0, but will soon. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Tuesday 25 November 2003 15:42 pm, SMD (Michael) Alachouzos wrote:
Hi.
I am running SuSE (Pro) 9.0, and have have used YaST (Install and Remove Software module) to install Privoxy (version 3.0.2).
However, Privoxy does not start (as it is supposed to) upon boot up (+ there's no mention of it in /var/log/boot.msg), and any attempt to reach any web site via my browser (= Konqueror configured for proxy http://127.0.0.1 at port 8118) fails with the message "Could not connect to host Proxy 127.0.0.1 at Port 8118".
I have successfully installed and used various versions of Privoxy under SuSE 7.3, 8.0 and 8.2, and I do not know why I can't get it to work under 9.0. Has anyone else her encountered this problem and discovered how to cure it?
All ideas will be gratefully received (but note that creating an empty /etc/rc.config file -- which was necessary to get Privoxy working under SuSE 8.2 -- does NOT help).
Simple... Yast --> system --> run level editor --> privoxy --> enable -- +---------------------------------------------------------------------------- + + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 11/25/03 17:08 + +---------------------------------------------------------------------------- + "The only race worth winning is the human race."
On Tue, 25 Nov 2003 17:09:04 -0500, Bruce Marshall wrote:
Yast --> system --> run level editor --> privoxy --> enable
Gosh -- getting Privoxy started really WAS that simple! Thank-you very much. (I had been puzzling over this for ages). However, Privoxy now reports "No such domain", and that the domain name "could not be resolved", regardless of what URL has been entered in the browser's address line. So it's actually useless at the moment, until I can get that fixed. Are you by any chance able to help with that as well? Regards, Michael Alachouzos alacos@equitonica.org http://equitonica.org Date (dd/mm/yyyy) = 11/26/03
* SMD Alachouzos
On Tue, 25 Nov 2003 17:09:04 -0500, Bruce Marshall wrote:
Yast --> system --> run level editor --> privoxy --> enable
Gosh -- getting Privoxy started really WAS that simple! Thank-you very much. (I had been puzzling over this for ages).
However, Privoxy now reports "No such domain", and that the domain name "could not be resolved", regardless of what URL has been entered in the browser's address line. So it's actually useless at the moment, until I can get that fixed. Are you by any chance able to help with that as well?
Privoxy must be told where to load its config file. The above _will_ start privoxy on boot but does not satisfy your needs. Initiate '/usr/sbin/privoxy /etc/privoxy/config' in your /etc/init.d/boot.local file, or find a way to pass the location of it's config file to it. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Tue, Nov 25, 2003 at 11:51:22PM -0500, Patrick Shanahan wrote: : > However, Privoxy now reports "No such domain", and that the domain name : > "could not be resolved", regardless of what URL has been entered in the : > browser's address line. So it's actually useless at the moment, until I : > can get that fixed. Are you by any chance able to help with that as : > well? : : Privoxy must be told where to load its config file. The above _will_ : start privoxy on boot but does not satisfy your needs. : : Initiate '/usr/sbin/privoxy /etc/privoxy/config' in your : /etc/init.d/boot.local file, or find a way to pass the location of it's : config file to it. This is incorrect advice, please don't follow it. Privoxy is already a fully installed package w/appropriate init.d entries. Tell me what you see when you do the following: ls -al /var/lib/privoxy/etc/hosts My guess is that the perms on the file will be 0600. They should be 0644. Try 'rcprivoxy restart' and see if that corrects the issue. If so, please let me know. I thought that I may have screwed something up. If you're seeing the same issue please let me know. I''m planning to file a bug report if I can verify that it's not just me. --Jerry -- "Barbie would also be tired of Microsoft's licensing bullshit." -- Maury Cesterino, Chief Software Architect, Mattel, Inc.
On Wed, 26 Nov 2003 00:58:32 -0500, Jerry A! wrote:
�Tell me what you see when you do the following: �ls -al /var/lib/privoxy/etc/hosts
�My guess is that the perms on the file will be 0600. �They should �be 0644.
Actually, I think they're 677 -- but I'm not sure, as I don't know what a "perm" is! Here's the full text of what I got when I executed the command you suggested (above): -rw-r--r-- 1 root root 677 Nov 26 04:41 /var/lib/privoxy/etc/hosts
�Try 'rcprivoxy restart' and see if that corrects the�issue.
It does (albeit only until the next reboot, not permanently), provided that I am connected to the Internet when I do the 'rcprivoxy restart'. (Doing the command first and then connecting afterwards is no good).
�I''m planning to file a bug report if I can verify that it's not�just me.
Clearly, that's a good idea. Meanwhile, do you know of anything which I can do to fix the problem on a permanent basis (i.e. so that I don't have to do 'rcprivoxy restart' every time)? Regards, and thanks very much for your help Michael Alachouzos alacos@equitonica.org http://equitonica.org Date (dd/mm/yyyy) = 11/26/03
On Wed, 26 Nov 2003 00:58:32 -0500, Jerry A! wrote:
�Tell me what you see when you do the following: �ls -al /var/lib/privoxy/etc/hosts
�My guess is that the perms on the file will be 0600. �They should �be 0644.
Actually, Jerry, after some research I really can't see what's wrong with -rw-r--r-- (which is what I got). So I don't see why it is that Privoxy only works OK after a 'rcprivoxy restart'. Have you submitted your bug report yet? (And, if so, to whom? i.e. Do you think this is a Privoxy bug, or a SuSE bug?) I'm going to remove myself from the mailing list now, as the amount of email coming to me from it is HUGE. But I'll check the thread on the website later today (and thereafter every so often) to see if there's any further comment/response from you -- and if you want to contact me individually re the bug report etc you can email me at alacos@equitonica.org SMD (Michael) Alachouzos alacos@equitonica.org http://equitonica.org Date (dd/mm/yyyy) = 11/27/03
participants (4)
-
Bruce Marshall -
Jerry A! -
Patrick Shanahan -
SMD Alachouzos