On 17-04-2008 09:04:17 +0200, Niels Nes wrote:
On Wed, Apr 16, 2008 at 07:51:29PM -0700, mobigital1 wrote:
after typing this up, I did a \q on mclient, and went back in, at that time this message appeared on the merovingian.log file:
TME 2008-04-16 22:50:11 MSG merovingian[20338]: database 'frdata' already running since 2008-04-16 22:10:44, up min/avg/max: 25111/25111/25111, crash average: 0.00 0.00 0.00 (2-1=0) MSG merovingian[20338]: redirecting client 127.0.0.1:49801 for database 'frdata' to mapi:monetdb://fedora.mydomain.com:50001/
This message doesn't explain the data base corruption.
It seems you hit a bug here. To repeat this problem could you some how describe the data your trying to insert. Which system your using etc. How where you running your monet server etc Maybe you could also create a bug report on sourceforge for this?
One thing from mobigitall's message is unclear to me:
then I stopped the database, and wanted to start it back up to see how quickly it would come up. it took a few minutes to come up while it was comitting uncomitted transactions. When i started it up the space usage looked like this: [snip] There is nothing in the merovingian.log file at all since stop/start of database.
I assume you start your database using merovingian in this case. One thing that I know is that merovingian doesn't wait minutes for a database to come up. Instead it waits for at max 10 seconds. Due to a bug that I fixed yesterday (stable CVS), merovingian would not log anything about the database not starting up within 10 seconds. The intentions of merovingian are to terminate a database that takes to long, however due to the same bug, this didn't happen actually.