First you should do `tail webx.log` to see if the server is on/off and if there are any error messages. When I looked I saw that there was a corrupted database. In the future, after we try to clean the database up, corruption shouldn't occur again, at least, not as easily. I used to see corrupted databases before 3.1, but now I don't anymore.

However, when a database is messed up for whatever reason, usually you can stop the server, rename webx.db to something like webx.db.save and then restart the server. If there is a webxdb.1 and webxroll.1 file, the server will restart using webxdb.1 as the database but not allow access until all the changes stored in the text file webxroll.1 are executed. This should bring the database current to where webx.db was before the crash -- the server creates a new webx.db file as a replacement. If webxdb.1 is corrupt, well then you have a problem anyhow.

For some reason, following this procedure failed, so then I went to plan B.

I renamed webx.db.save back to webx.db, put an empty file named "ignorecorrupted" in the directory and started the server again. The existence of an empty file with the name ignorecorrupted in it tells the server to ignore the corrupted record and just start again. You can also put in a file named "fixallpages" which can try to fix things. So if it starts up successfully, you might lose some data that was entered on your site.

Anyhow, I backed up with the repack option which does some cleaning up, but I'm moving your database to the staging server where I will do an export and import of the database. This should result in a totally clean database.