From: SourceForge.net <no...@so...> - 2013-11-01 19:56:32
|
Support Requests item #3614990, was opened at 2013-09-09 14:11 Message generated for change (Comment added) made by gvantass You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3614990&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: startup Group: 3.0.21 >Status: Open Priority: 5 Private: No Submitted By: Geordon (gvantass) Assigned to: Ian Silvester (diem) Summary: Package not working on OSX Mountain Lion Initial Comment: I just installed the OSX 10.8.3 version of Privoxy by package and configured my network proxy for Safari as outlined in the instruction. However, there seems to be something not working right with the proxy. When I try to go to the config page, the browser can't connect to the proxy. When I look for Privoxy in the process list, there is nothing there: Enso:~ gvantass$ ps -ef|Grep -i privo 501 7612 393 0 3:35PM ttys000 0:00.00 Grep -i privo Enso:~ gvantass$ I have turned off the Mac firewall, trying to see if that was interfering, but that doesn't help, either. I'm kind of wondering if there is a missing config file somewhere, so would appreciate some guidance as to where those would be. Thanks! ---------------------------------------------------------------------- >Comment By: Geordon (gvantass) Date: 2013-11-01 12:56 Message: Hi again, Ian. Sorry it's taken me so long to get back to you. Life (and a death. :( ) happened, but I've mostly fought clear for a bit. :D Attached privoxy_log_long_list with the info as requested (If I understood correctly). ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-10-22 05:51 Message: Hi Geordon, This ticket is with you at the moment - could you read through my latest comments and supply the listing I've asked for? Cheers, Ian ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-10-15 06:41 Message: Hi Geordon, Sorry to hear you've had to go to Brew (though pleased to hear they've got a 3.0.21 release there!) but this has given me an idea of the cause! The differences between the two plists are: 1. user/group Privoxy runs as The Brew version will have Privoxy running as either you or root (depending on where the plist is kept). Neither is optimal from a security perspective. 2. use of the -no-daemon option If I understand it correctly this prevents Privoxy from detaching itself from launchd's control. Not crucial but 'cleaner' to have it remain controlled by launchd. 3. specifying the logfile explicitly Now then, I suspect that it is this that is causing the error though it's not clear why, a priori. Could you send a screenshot of a 'long' listing of /var/log/privoxy? The install log claims that this was created correctly but we shall see.. Cheers, Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-10-14 21:43 Message: Ian, I did some semi-random Google searching and I think I stumbled upon a fix. There seems to be a problem with the provided plist file that prevents Privoxy from starting up. Sidenote: I successfully installed Privoxy to my OSX via "homebrew" (http://brew.sh) but it didn't include a plist. The brew installation of Privoxy installs into as my user account, as /usr/local/Cellar/privoxy rather with a link to /usr/local/sbin/privoxy so that special permissions are not required. Anyway, the plist that I was able to use with brew is a little old, but works better than the one included with the OSX install package. ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-10-14 21:43 Message: [This is a canned message:] Your support request has been received by the Privoxy team, but in order to look into the problem we need more information than you provided. Please check the following list and add any missing information that is applicable to your problem in a new comment to this item: * the exact Privoxy version (if you got the source from CVS, please also give the date;) * if you aren't using an official build that was released by the Privoxy Team, you should mention that as well. * whether or not you are using Privoxy's default configuration (for example if you changed the configuration to chain Privoxy with Tor) * the operating system and version that you're using * the name, version and platform of the browser you were using when the problem occurred * The URL of the page on which you encountered the problem * the exact steps that are necessary to reproduce the problem. (If it's not reliably reproducible: any other information that might be helpful to identify the source of the problem, like log or config file excerpts) Thanks in advance! ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-10-14 19:48 Message: One further thought; have you tried uninstalling (using the supplied script) and reinstalling from scratch? Ian ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-10-14 19:46 Message: Hi Geordon, Yes, I'm aware this is with me. I've been busy with other work and not had much time to spend on it. So far all I have been able to establish is that indeed the errors thrown by launchd (e.g. "Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory") do mean exactly that - that it is erroring out due to a bad file path. I don't know whether it is that launchd cannot find Privoxy (or its config file) or that Privoxy is throwing the error and passing it back to launchd. The screenshots you've sent suggest to me that launchd is configured correctly and , since Privoxy runs from the command line that doesn't seem to be the problem either, so I admit that I am somewhat at a loss at this point. That's all I can tell you for now; if I get a brainwave I'll report back on this ticket (which I'll keep open since the issue remains unsolved). Sorry it's not better news, Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-10-14 19:16 Message: Ian, are you still out there? I haven't heard word from you in a few weeks and I still can't get Privoxy to work right. ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-10-03 15:00 Message: Ian, I haven't gotten anything back from you yet. ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-24 17:55 Message: Ian, I added permission.png that shows the output of the requested directory listings. Thanks! ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-24 07:03 Message: No problem Geordon, Could you also send screenshots of directory listings of: /usr/local/sbin /Library/LaunchDaemons/org.ijbswa.privoxy.plist At this point my Googling suggests that the error in Console is either down to permissions of the launchd plist or privoxy itself, or an error thrown out by Privoxy itself when started by launchd. The screenshots will help rule out the former. Cheers, Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-23 21:06 Message: I think that I missed your last update, Ian. Forgive me. There were no error messages when manually un/loading the plist file via sudo Console messages attached plist file attached. ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-17 10:38 Message: Okay so at least it runs when run directly, so it must be something to do with invoking it as a LaunchDaemon. As an admin, please execute: /bin/launchctl unload /Library/LaunchDaemons/org.ijbswa.privoxy.plist then: /bin/launchctl load /Library/LaunchDaemons/org.ijbswa.privoxy.plist and then send me: - a terminal window screenshot (only if any errors are displayed) - a copy of the messages logged in Console - your install.log - /Library/LaunchDaemons/org.ijbswa.privoxy.plist The reason by the way that it wanted the config file in the dir where you ran it from (the ownership tells me you moved it there?) is because it only looks in the CWD when the config path and file are not specified on the command line, so in fact no symlink is required. Cheers, Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-17 09:55 Message: After some file movement gymnastics, I got Privoxy to start from the command line. However, it wanted to see the config file in /Applications/Privoxy I did a little looking around, and am left wondering if the config file in /Apps/Privoxy should be a symlink to the one in /usr/local/etc/privoxy ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-16 11:13 Message: Hi Geordon, What result do you get if you run Privoxy directly from the command line? It'll not want to start due to being the wrong user, but I'm keen to see what the log contains. Cheers, Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-13 21:52 Message: Took me a bit to get the launchctl logging figured out, but I think I got what you're looking for in the "privoxy start log" file attached. For some reason, SourceForge doesn't like my (empty) Privoxy log file, keeps telling me that the file can't be more than 256k ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-13 18:14 Message: Okay so definitely do the two things I suggested: - enable logging as per my previous reply and attach a log to your next post - if Privoxy is at least being called and then failing to start this log should tell us why. - have a poke in Console and see if you can find an actual error code for the failed launchdaemon start Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-13 11:15 Message: Oh, nothing of the sort, Ian. I meant that I changed the network preference settings to look for/not look for the proxy on 127.0.0.1:8118 This morning, it would seem that there is no Privoxy running again I get the "can't connect to proxy server" page when trying to go to the config page. Then, when I look for the process I get this: Enso:LaunchDaemons gvantass$ ps -ef|Grep privoxy 501 94704 10973 0 12:47PM ttys000 0:00.00 Grep privoxy Enso:LaunchDaemons gvantass$ launchctl load org.ijbswa.privoxy.plist org.ijbswa.privoxy: Already loaded Enso:LaunchDaemons gvantass$ Unloading and reloading the .plist doesn't start the proxy again. So I rebooted but Privoxy didn't coma back up, nor can I manually start it. Truth be told, I'm stumped. ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-13 06:06 Message: Hi Geordon, Okay then there's two things to do: - enable Privoxy logging (as described here: http://www.privoxy.org/user-manual/contact.html) and send us a log extract - take a look in your system logs using Console - this will contain whatever error is causing the launchitem to fail (although it does look like a Privoxy internal error) I'm interested in your comment regarding "resetting the proxy for localhost and port" . Does this mean you had reconfigured the address Privoxy listens on? Perhaps the error is that it could not bind to that address/port? Ian ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-12 23:36 Message: Further info: I did a full reboot and Privoxy did not auto start. However, I can force load it (launchctl load org.ijbswa.privoxy.plist) and it comes up. Also, now, if I re-set the proxy for localhost and port, Privoxy config comes up. So, something doesn't seem to like starting itself, it seems. ---------------------------------------------------------------------- Comment By: Geordon (gvantass) Date: 2013-09-12 23:19 Message: I couldn't figure out how to scale the screen cap down to an acceptable size at 1:00 AM (in the middle of 6 chapters for the week. Ugh. College. :D ), so I uploaded it to my Dropbox: https://www.dropbox.com/s/0y6sod3h62nu5ni/privoxy.png I *do* have the privoxy process running at this time, after a complete fresh uninstall/reinstall of the package. I don't know if it's useful, but I am also running DNSCrypt and OpenDNS on the desktop that I want to install Privoxy on. ---------------------------------------------------------------------- Comment By: Ian Silvester (diem) Date: 2013-09-10 11:53 Message: Hi Geordon, Could you screenshot the error you get when trying to browse to the config page? Also in /Applications/Privoxy there should be a link to the install log file - could you attach this to the ticket too? Thanks, Ian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=3614990&group_id=11118 |