The disk is not full yet (%65), but it would seem that a 37GB Data.fs file would be a lot for Zenoss/Zope to have to read through. I have read many threads about trimming database sizes and tried many of the tricks, but neither my MySQL nor my Zope database have shrunk any.

Let me back up... yesterday and today I was getting crash messages from different pages of the Zenoss web interface, and I couldn't trace them to a specific service, so I rebooted the whole server. The web interface never came back.

`zopectl logtail` tells me this:

 

 

zenoss@monitor:~ bin/zopectl logtail
return self.loadEx(oid, version)[:2]
File "/usr/local/zenoss/zenoss/lib/python/ZEO/ClientStorage.py", line 774, in loadEx
self._cache.store(oid, ver, tid, None, data)
File "/usr/local/zenoss/zenoss/lib/python/ZEO/cache.py", line 293, in store
self.fc.add(o)
File "/usr/local/zenoss/zenoss/lib/python/ZEO/cache.py", line 980, in add
available = self._makeroom(size)
File "/usr/local/zenoss/zenoss/lib/python/ZEO/cache.py", line 915, in _makeroom
size, e = self.filemap.pop(ofs)
KeyError: 12

`zopeclt status` says "daemon manager not running". If I start it, it gives me a PID, and the status says "daemon manager running; daemon process not running". Moments later, the process is dead and we're back to "daemon manager not running". In either state, the log ends with the same not-very-helpful info (or maybe it's showing me the wrong logfile?).

Any suggestions for what I can do? We're very dependent on our Zenoss here, so I feel like I'm flying blind all of the sudden.