RE: Upgrading to PyDS 0.7 on Windows

Hi!

Just a note: you might want to subscribe to pyds-users, too, so I don't
need to manually approve your messages ;-)

> 2004-02-02 21:39:46   |   upstream   |   Background thread exception 
> exceptions.IOError: unsupported XML-RPC protocolException instance 
> __dict__: {'errno': None, 'args': ('unsupported XML-RPC protocol',), 
> 'strerror': None, 'filename': None}

Weird. This looks like something the other end raised, or maybe the
response was broken.

> This error entry is sandwiched between what look like successful pings 
> to blo.gs, weblogs.com, and technorati. I say "what look like
successful 
> pings" because the pinging is occurring, but I am not clear that the 

So it should be the local community server answering. But the problem
is, you don't have a local community server. Maybe that's the problem :)

Do you have your local community server enabled in the PingTool
preferences? If yes, better disable it, as you do FTP upstreaming and
your community server isn't actually available.

> result is correct - in other words, each ping site is responding, but 
> with responses that I am not expecting. For example, weblogs.com is 
> telling me that it only accepts one ping per half hour and that I've 
> already recently pinged.

That's normal for weblogs.com - it often tells you that. Usually your
site is already listed, though. Sometimes it takes up to 5 Minutes that
your recent ping shows up on weblogs.com.

> But I do not see my site listed in the recent 
> changes. I don't know enough yet about technorati or blo.gs to verify
> if my ping has gotten thru or not.

blo.gs just lists you on their homepage, as would do weblogs.com.
Technorati does whatever technorati does - I assume it's pulling your
RSS feed or your pages to see what links are there.

> What problem is the error above indicating? Is it affecting my pings?

It shouldn't. Errors with pinging just block this one ping, other pings
still go through. So just disable the local community server if it is
enabled and try again with weblogs.com. Wait some minutes to check
wether it shows up on weblogs.com (or check with blo.gs, they are
updating faster).

You could add an additional ping server in the PingTool preferences with
the RPC url set to <http://pycs.net/RPC2> and the type set to the
default weblogs.com ping (not the extended one) - this would ping
pycs.net and would allow Phil to see what your system sends. And since
pycs.net change list is much smaller, you can better see wether your
pings are ok.

bye, Georg