Core Dump on ./start after system power out
Hello Recently a guy with an pick-axe dug through the mains supply outside our office block. Our server went down cold. After splicing, the server booted up fine. Only now, starting up zope (./start) results in a python core dump : Bad system call. As time is of the essence, I decided to scream for help while I'm trying to fix things myself. I'm about to delete all the .pid files in zopepath/var...can't really imagine it would help...any other bright ideas appreciated. Zope-2.3.0 Python 2.0 FreeBSD 3.5
--On 04 June 2001 14:47 +0200 Gerrie Roos <gerrie@trispen.com> wrote:
Hello
Recently a guy with an pick-axe dug through the mains supply outside our office block. Our server went down cold. After splicing, the server booted up fine. Only now, starting up zope (./start) results in a python core dump : Bad system call.
As time is of the essence, I decided to scream for help while I'm trying to fix things myself. I'm about to delete all the .pid files in zopepath/var...can't really imagine it would help...any other bright ideas appreciated.
Gerrie: I hope you've solved this by now. In case you haven't http://www.zope.org/Members/itamar/CorruptedZODB once saved my bacon under similar circumstances. Paul -- The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK E-mail: paul.browning@bristol.ac.uk URL: http://www.bris.ac.uk/
participants (2)
-
Gerrie Roos -
Paul Browning