RE: RE: Python 2.3 and aggregator

I temporarily got the same message when examining the XML feed in PyDS
(in configure aggregator), but now it just dies silently. The silent
death scenario is what caused me to downgrade my Metakit and restore
from an older copy (bzip'ed /home), since I assumed it was the
corruption mentioned on the list.

Upon executing pyds-start, the .PyDS/log/etc.log and .PyDS/log/error.log
are touched (date/time changes), but error.log is empty (0 bytes) and
etc.log gives the "Server is  now up and responding" as if everything is
fine.

pyds-start -v does not yield different results. pyds-debug says "No
monitor server is configured!".

Weird. I'm a little too busy up to really poke around on my own right
now. More tomorrow, especially if you can guide me where to look.

-Steve
-----Original Message-----
From: Georg Bauer [mailto:gb-BRhJDZTO+/[email protected]] 
Sent: Wednesday, April 21, 2004 1:30 PM
To: COFFMAN Steven
Cc: pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
Subject: Re: [Pyds-dev] RE: Python 2.3 and aggregator

Hi!

> Ok, last message for the day. Sorry to be so impulsive. It turns out 
> my restoring my old .PyDS had some old aggregated content, and the 
> error DOES still prevent new aggregation.

Hmm - what error do you get now? Still the stuff on None not having
lower()? Or something different?

bye, Georg