Re: Frozen pyds install

Georg Bauer wrote:
> Too bad. The only idea I can offer is to move data files you suspect are
> broken out of the var directory and try PyDS starting until the problem
> goes away. That way you can isolate the data file that creates the
> problems and find out which one actually has the problem. I would start
> with these:
> 
> aggregator.data
> eventlog.data
> upstream.data
> downstream.data

It turned out to be aggregator, which I suppose isn't surprising.

> as those have the most "action". Move them somewhere safe, so you can
> move them back, if you need to. And if aggregator.data is broken, you
> can fetch your subscriptions from the saved file, too.

Saved file?  Like a backup?  I never set up any backups :(  Is there 
some other way of getting those out?  I suppose I could find a mk 
browser of some sort.

I tried running mkstats, which is supposed to verify the integrity of 
the file, but it didn't have any problem with the file.  And metakit 
says it's supposed to be safe to kill (which I was doing regularly), 
that it won't damage the database.  But maybe there's other problems.

   Ian