[proxyTools-users] Re: [noCensorship] Re: LP

[wayne <wa...@ny...>]

> From: "gstmoderator" <gst...@ho...>
> To: <noc...@fr...>
> Subject: [noCensorship] Re: LP
> 
> > > Reinstalled LP after a move an OS upgrade and ten months or so can't get
> LP to merge new proxies and save new configuration on restart no proxies
> saved and privacy analyzer traces directly to my isp.
> >
> > We'll need some more info.
> >
> > 1) What operating system?
> 
> XP
> >
> > 2) What error messages (if any)? Look at the localProxy log windows
> > to see these.
> >
> 
> None

None?
Strange.

I meant the normal logs in the LP GUI log window. Two windows open 
when you start it, right? One of them is the GUI, the other looks 
like a command window. The 'command window' logs what happens in 
the GUI. It's impossible that there's nothing in this - please look 
again.

A further window opens when you click 'start services'. That one 
logs what happens in the back end.

Posting that huge saved config was pointless. 
There appears to be a heap of stuff missing from it.
Losing the indentation makes it unreadable too.

> > 3) Where exactly are you looking to be able to say 'can't get LP to
> > merge new proxies' and 'no proxies saved'?
> > Which config are you expecting to see these in?
> 
> used autoconfig and test/merge to add proxies put into box above buttons.
> restarted LP using auto, last, saved, User0, wayne-adsl configs, clicked
> update new proxies button says something like complete no proxies merged/no
> proxies to check
> 
> >
> > 4) There's no 'save new configuration' option. What are you
> > referring to? The 'autoconfigure' button sounds like what you want
> > - is that what you are trying? The firewall blocking info and proxy
> > test results will appear in the 'auto' configuration. You should
> > then ask LP to rebuild for that configuration.
> >
> > If you mean 'save running configuration', then that's
> > probably not what you want - it just saves the running info (the
> > stuff LP has learned while you're using it). You can use this next
> > time by choosing the 'saved' configuration.
> 
> meant save running config loaded saved config and no proxies were merged

That's right. 
Did you think they would be, if you 'saved' and reloaded?
Why?
When you load the 'saved' config, LP is running as it was when 
you saved it!
This sounds like it has nothing to do with your problem.

> > The 'test/merge new proxies' button tests the proxies in the field
> > above it (which you may edit) and merges the results to whatever current
> > configuration has been selected. By default, the proxies in the field
> > are initialized by looking in the registry and the environment.
> >
> > Generally, these options use master.pl/exe and statProxy.pl/exe.
> > You could independently verify that these are working by simply
> > running them.
> >
> 
> master.pl opens and tests all proxies as to merge, saves to auto or config I
> use

Since you have the exe, you wouldn't be running master.pl. 
In fact, master doesn't run at all when you click 
'test/merge new proxies'.
Master doesn't actually test proxies (it calls statProxy for that), 
and doesn't do any merging. It's main function is to test the 
firewall blocking.

Let's clarify:
1) you enter proxies into the field above 'test/merge new proxies'
Or you leave the entries that are already there. Use the right format:
proxy.xxx.com:8000, proxy2.yyy.etc:8999
etc. (say).
2) you click 'test/merge new proxies'
3) a window opens (or appears on the task bar?). On XP, I think 
it should have a title containing the command used to run it. 
Warning, I don't have an XP system to test on, so I can't be 
precise here. This might be the area where the problem lies - the 
window/icon may not be appearing at all. I had some XP problems here 
before. If that's the case, I'll need to find an XP system.
4) in that window, you should be able to watch statProxy testing your 
proxies. If it closes too quickly, you probably gave it a bad proxy 
format. If the reason is not obvious, I suggest you run statProxy 
by itself in a command window with the proxy format you used to see 
what error is reported.
5) the merge of these results to a config are done back in the GUI 
(by calling mergeHosts).

I'll wait to hear what the log window contains.

> > Try the 'help' button to get more details.

You did look at this, I guess?

> > 5) Which LP are you using (version number, executable or source)?
> 
> 4.247 exe I think

Damn, that makes things difficult.

> > 6) You might be able to run the GUI window (localProxy.pl or .exe)
> > with debug turned on - later versions only.
> >
> > 7) During the above tests, there are various files created and saved.
> > The easy way to find them is by modification/creation date. See if
> > they contain the proxies you expected. Let us know what happened.
> 
> config-saved attachd

Did you find any files created/modified?

> > 8) PLEASE post some logs!
> 
> tried logging nothing happened

That 'logging' is only effective when the back end has started up.
It increases the verbosity o fthe logs to include all data passing 
through LP.

See above.

> Thnks wayne

--
wa...@ny...
http://proxytools.sourceforge.net/