Re: Frozen pyds install
Georg Bauer <gb-BRhJDZTO+/[email protected]> Wed, 17 Mar 2004 18:52:38 +0100
| Newsgroups | gmane.comp.python.pyds.user |
|---|---|
| Message-ID | <r02010100-1028-E1B9EACF783B11D8A517000A9573A72A@[10.0.0.145]> |
Hi! > I've been having problems where pyds would periodically freeze up,=20 > sometimes spiking CPU usage. When this happens I usually have to kill=20 > (-9) the server and restart it, and then it's okay. It doesn't seem to=20 > be based on anything I'm doing, so I'm assuming it's the aggregator. There might be still a problem with feeds with very large item numbers and the aggregator - it doesn't handle those feeds very good. Especially if you already have large amounts of postings for that feed in the aggregator database. > Anyway, just recently it stopped coming up successfully. Well, it=20 Woops. You could start it with pyds-start -f -v to see what it does when starting up and how far it comes. This will show you more details on what happens within PyDS. pyds-start -f -v -e will even echo all eventlog messages to stdout. That's especially helpfull if you can't access the eventlog any more. > So I assume there's some bad persistent data in there. Is there any=20 > good way to find out where, or to remove data? I'd be okay with=20 Every tool has it's own database in ~/.PyDS/var/ - so you can just delete those databases where you suspect broken content. But tools usually keep setting and items in their database - so if you remove aggregator.data, you will lose your subscriptions. Do you use the backup feature? If yes, you can just set up a new instance and pull in your backup with pyds-restore. Other options would include stopping PyDS and just using Metakit and Python to look at the database files directly. Phil did post some repair script once, you might find it on his "second post" blog or in the PyCS mailing list archives (PyCS uses the same database). If you use Metakit to directly access the data files, you can use the introspection stuff from Metakit to look at your data and for example pull out the subscriptions from the data file. I currently don't have any repair scripts ready, but if somebody builds some tools, send them in for inclusion in the distribution. bye, Georg