Problem during restart--"Database in use, unable to com

[jabdulius]

We have PageGate running as a service along with 2 connectors and the web interface. Yesterday, at midnight, after it restarted, no pages were going through.

Weird stuff I noticed from the scheduler log:
8/15/2007 Initiating cleanup routines
8/15/2007 Module Stopped
8/15/2007 12:00:02 AM Module Started
8/15/2007 12:00:03 AM Running cleanup routine
8/15/2007 12:00:03 AM Waiting for server module to pause
8/15/2007 12:00:07 AM Server module paused
8/15/2007 12:00:07 AM Waiting for connectors to pause
8/15/2007 12:00:14 AM Connectors paused
8/15/2007 12:00:14 AM Waiting for interfaces to pause
8/15/2007 12:00:47 AM Timeout... continuing
8/15/2007 12:00:47 AM Attempting to compact database
8/15/2007 12:00:52 AM Database in use, unable to compact
8/15/2007 12:00:52 AM Trimming log files
8/15/2007 12:00:52 AM Checking database for null values
8/15/2007 12:00:52 AM Checking database for invalid group entries and dups
8/15/2007 12:00:52 AM Removing old messages from database
8/15/2007 12:00:52 AM Removing old files from badmsg folder
8/15/2007 12:00:52 AM Resetting database flags
8/15/2007 12:00:52 AM Module resumed

After this, the web interface (what we were using to send pages) never restarted. After we restarted the service, everything worked fine.

Any ideas?

_________________
Karim Varela
Software Development Engineer
www.i-booze.com

[Tech Support]

The only time you'll ever see that particular error pop up is if something has the pagegate.mdb file locked in process. Do you have a nightly backup routine that runs at midnight? Something that would have been accessing, copying, using the database when the cleanup routine attempted to run?

[jabdulius]

We don't have anything external to PageGate that runs at midnight, but there's a decent chance that a page was scheduled at midnight. Could that have been using the database and have caused this problem?

_________________
Karim Varela
Software Development Engineer
www.i-booze.com

[Tech Support]

It's entirely possible. There are very, very rare occasions where a module that hasn't been stopped by the cleanup routine will process a message as the cleanup routine begins, which means that the module is going to be hung in process, which means that the database is going to be hung in process. By very, very are occassions, I mean there's a 1 in 100,00 chance that you'll run into something like this.

[jabdulius]

Well, it just happened again, exactly the same way. So either we're very, very unlucky or there's something wrong with the way PageGate is restarting.

Any other ideas?

Thanks!

_________________
Karim Varela
Software Development Engineer
www.i-booze.com

[Tech Support]

Just to be on the safe side, you may want to tell everyone on your network that messages via PageGate not to send or schedule messages from 11:00 PM to 12:02 AM. That should prevent any accidental module hangups.

[jabdulius]

That is not an option. We must schedule pages 24x7. Please fix.

_________________
Karim Varela
Software Development Engineer
www.i-booze.com

[Tech Support]

Within your PageGate directory, there is an executable called fileversioninfo.exe

If you would, please run that file and email the results to support at notepage dot com