051109 12:19:17  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 170 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
051109 12:19:20  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 170 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
051109 12:19:23  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051109 12:19:23  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 935255564.
InnoDB: Doing recovery: scanned up to log sequence number 0 935255564
InnoDB: Last MySQL binlog file position 0 0, file name 
051109 12:19:24  InnoDB: Started; log sequence number 0 935255564
051109 12:19:24 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051109 12:40:38 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051109 12:40:38  InnoDB: Starting shutdown...
051109 12:40:40  InnoDB: Shutdown completed; log sequence number 0 935255564
051109 12:40:40 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051109 12:40:49  InnoDB: Started; log sequence number 0 935255564
051109 12:40:49 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:43051110  9:45:43 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:45:50051110  9:45:50 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:37051110  9:46:37 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:46:40051110  9:46:40 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:02051110  9:57:02 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:05051110  9:57:05 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:17051110  9:57:17 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:19051110  9:57:19 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:39051110  9:57:39 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:39051110  9:57:39 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:56051110  9:57:56 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:57:56051110  9:57:56 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051110  9:58:08051110  9:58:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:04:08051111  9:04:08 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:55:57051111  9:55:57 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:00051111  9:56:00 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:00051111  9:56:00 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:19051111  9:56:19 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:19051111  9:56:19 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:27051111  9:56:27 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:27051111  9:56:27 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:56051111  9:56:56 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:56:56051111  9:56:56 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:15051111  9:57:15 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:18051111  9:57:18 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:18051111  9:57:18 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:25  InnoDB: Error: table `aareg/firma` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:27051111  9:57:27 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:31  InnoDB: Error: table `aareg/firma` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:32051111  9:57:32 [ERROR] Cannot find table aareg/person from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:37051111  9:57:37 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111  9:57:37051111  9:57:37 [ERROR] Cannot find table aareg/aakjoring from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:05:21051111 10:05:21 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:05:21051111 10:05:21 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:07:15051111 10:07:15 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:07:15051111 10:07:15 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:31051111 10:08:31 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:31051111 10:08:31 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:33051111 10:08:33 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:33051111 10:08:33 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:45051111 10:08:45 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:45051111 10:08:45 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:49051111 10:08:49 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:08:49051111 10:08:49 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:10:54 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051111 10:10:54  InnoDB: Starting shutdown...
051111 10:10:58  InnoDB: Shutdown completed; log sequence number 0 935255574
051111 10:10:58 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051111 10:27:13  InnoDB: Started; log sequence number 0 935255574
051111 10:27:13 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051111 10:28:14051111 10:28:14 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:28:14051111 10:28:14 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:31:00051111 10:31:00 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:31:00051111 10:31:00 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:35:04051111 10:35:04 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:35:04051111 10:35:04 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:46:45051111 10:46:45 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:46:45051111 10:46:45 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:46:47051111 10:46:47 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051111 10:46:47051111 10:46:47 [ERROR] Cannot find table aareg/firma from the internal data dictionary
of InnoDB though the .frm file for the table exists. Maybe you
have deleted and recreated InnoDB data files but have forgotten
to delete the corresponding .frm files of InnoDB tables, or you
have moved .frm files to another database?
Look from section 15.1 of http://www.innodb.com/ibman.html
how you can resolve the problem.

051122  6:15:40  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051122  6:15:44  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 935258590.
InnoDB: Doing recovery: scanned up to log sequence number 0 935258590
InnoDB: Last MySQL binlog file position 0 0, file name 
051122  6:15:44  InnoDB: Started; log sequence number 0 935258590
051122  6:15:45 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051122 17:32:41 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051122 17:32:41  InnoDB: Starting shutdown...
051122 17:32:43  InnoDB: Shutdown completed; log sequence number 0 935258590
051122 17:32:43 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051123  7:12:04  InnoDB: Started; log sequence number 0 935258590
051123  7:12:06 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051130  9:35:47 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130  9:45:47 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130  9:55:47 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130 10:05:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130 10:15:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130 10:25:48 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_82.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051130 10:30:47 [Warning] Warning: Enabling keys got errno 28, retrying
051201  9:38:31 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\test\#sql-2c0_b1.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051201  9:42:31 [Warning] Warning: Enabling keys got errno 28, retrying
051205 13:49:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051205 13:59:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051205 14:09:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051205 14:19:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051205 14:29:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051205 14:39:07 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg\person.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051206 10:25:59 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 10:25:59  InnoDB: Starting shutdown...
051206 10:26:01  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 10:26:01 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 10:28:17  InnoDB: Started; log sequence number 0 935277249
051206 10:28:17 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 10:47:48 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 10:47:48  InnoDB: Starting shutdown...
051206 10:47:51  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 10:47:51 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 10:47:53  InnoDB: Started; log sequence number 0 935277249
051206 10:47:53 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 10:50:24 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 10:50:24  InnoDB: Starting shutdown...
051206 10:50:25  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 10:50:25 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 10:50:34  InnoDB: Started; log sequence number 0 935277249
051206 10:50:34 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 10:52:18 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 10:52:18  InnoDB: Starting shutdown...
051206 10:52:20  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 10:52:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 10:56:38  InnoDB: Started; log sequence number 0 935277249
051206 10:56:38 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 11:05:46 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 11:05:46  InnoDB: Starting shutdown...
051206 11:05:48  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 11:05:48 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 11:05:52  InnoDB: Started; log sequence number 0 935277249
051206 11:05:52 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 11:11:26 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 11:11:26  InnoDB: Starting shutdown...
051206 11:11:28  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 11:11:28 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 11:11:30  InnoDB: Started; log sequence number 0 935277249
051206 11:11:30 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 11:16:50 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 11:16:50  InnoDB: Starting shutdown...
051206 11:16:52  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 11:16:52 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 11:17:28  InnoDB: Started; log sequence number 0 935277249
051206 11:17:28 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 12:20:37 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 12:20:37  InnoDB: Starting shutdown...
051206 12:20:40  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 12:20:40 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 12:22:04  InnoDB: Started; log sequence number 0 935277249
051206 12:22:04 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 12:23:41 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 12:23:41  InnoDB: Starting shutdown...
051206 12:23:42  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 12:23:42 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 12:23:44  InnoDB: Started; log sequence number 0 935277249
051206 12:23:45 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 12:25:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 12:25:20  InnoDB: Starting shutdown...
051206 12:25:23  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 12:25:23 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 12:25:25  InnoDB: Started; log sequence number 0 935277249
051206 12:25:25 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 12:26:27 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 12:26:27  InnoDB: Starting shutdown...
051206 12:26:30  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 12:26:30 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 12:30:35  InnoDB: Started; log sequence number 0 935277249
051206 12:30:35 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 13:07:43 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 13:07:44  InnoDB: Starting shutdown...
051206 13:07:45  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 13:07:45 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 13:09:00  InnoDB: Started; log sequence number 0 935277249
051206 13:09:00 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 14:12:45 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 14:12:45  InnoDB: Starting shutdown...
051206 14:12:46  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 14:12:46 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 14:12:48  InnoDB: Started; log sequence number 0 935277249
051206 14:12:48 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051206 14:15:25 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051206 14:15:25  InnoDB: Starting shutdown...
051206 14:15:26  InnoDB: Shutdown completed; log sequence number 0 935277249
051206 14:15:26 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051206 14:18:29  InnoDB: Started; log sequence number 0 935277249
051206 14:18:29 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051207 12:39:57 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051207 12:39:59 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 36  user: 'steinar'

051207 12:39:59  InnoDB: Starting shutdown...
051207 12:40:01  InnoDB: Shutdown completed; log sequence number 0 935277249
051207 12:40:01 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051207 12:56:17  InnoDB: Started; log sequence number 0 935277249
051207 12:56:18 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051207 12:57:50 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051207 12:57:50  InnoDB: Starting shutdown...
051207 12:57:52  InnoDB: Shutdown completed; log sequence number 0 935277249
051207 12:57:52 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051207 12:57:54  InnoDB: Started; log sequence number 0 935277249
051207 12:57:54 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051209 15:07:24  InnoDB: Started; log sequence number 0 935277249
051209 15:07:24 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051212 14:19:52  InnoDB: Started; log sequence number 0 935277249
051212 14:19:53 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051212 15:48:23  InnoDB: Started; log sequence number 0 935277249
051212 15:48:23 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051212 15:49:54  InnoDB: Started; log sequence number 0 935277249
051212 15:49:54 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051213  8:26:27  InnoDB: Started; log sequence number 0 935277249
051213  8:26:27 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051213  8:32:23 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hjelpeserver-bin' to avoid this problem.
051213  8:32:24  InnoDB: Started; log sequence number 0 935277249
051213  8:32:24 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt-log'  socket: ''  port: 3306  Official MySQL binary
051213  9:35:04 [Warning] Aborted connection 4 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051213 10:28:11 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hjelpeserver-bin' to avoid this problem.
051213 10:28:11  InnoDB: Started; log sequence number 0 935277249
051213 10:28:11 [Note] Recovering after a crash using hjelpeserver-bin
051213 10:28:11 [Note] Starting crash recovery...
051213 10:28:11 [Note] Crash recovery finished.
051213 10:28:11 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt-log'  socket: ''  port: 3306  Official MySQL binary
051213 12:45:18 [Warning] Aborted connection 3 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051213 12:45:18 [Warning] Aborted connection 4 to db: 'information_schema' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051213 12:45:37 [Warning] Aborted connection 6 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051213 12:45:37 [Warning] Aborted connection 7 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051214  9:55:16 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051214  9:55:17  InnoDB: Starting shutdown...
051214  9:55:18  InnoDB: Shutdown completed; log sequence number 0 935277259
051214  9:55:18 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051214  9:56:57 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hjelpeserver-bin' to avoid this problem.
051214  9:56:58  InnoDB: Started; log sequence number 0 935277259
051214  9:57:04 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt-log'  socket: ''  port: 3306  Official MySQL binary
051214 11:30:11 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051214 11:30:11  InnoDB: Starting shutdown...
051214 11:30:13  InnoDB: Shutdown completed; log sequence number 0 935277259
051214 11:30:13 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051214 12:07:39 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hjelpeserver-bin' to avoid this problem.
051214 12:07:40  InnoDB: Started; log sequence number 0 935277259
051214 12:07:46 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt-log'  socket: ''  port: 3306  Official MySQL binary
051215 11:17:19 [Warning] Aborted connection 3 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 11:24:57 [Warning] Aborted connection 14 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 11:24:57 [Warning] Aborted connection 15 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:17:29 [Warning] Aborted connection 18 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:17:29 [Warning] Aborted connection 17 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:39:29 [Warning] Aborted connection 20 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:39:29 [Warning] Aborted connection 21 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:51:40 [Warning] Aborted connection 23 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:51:40 [Warning] Aborted connection 22 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:54:23 [Warning] Aborted connection 25 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 12:54:23 [Warning] Aborted connection 24 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:04:25 [Warning] Aborted connection 29 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:04:25 [Warning] Aborted connection 28 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:34:59 [Warning] Aborted connection 39 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:34:59 [Warning] Aborted connection 38 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:36:34 [Warning] Aborted connection 41 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:36:34 [Warning] Aborted connection 40 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:36:39 [Warning] Aborted connection 43 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:36:39 [Warning] Aborted connection 42 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:46:57 [Warning] Aborted connection 44 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:46:57 [Warning] Aborted connection 45 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:47:46 [Warning] Aborted connection 30 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 13:53:32 [Warning] Aborted connection 47 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:53:32 [Warning] Aborted connection 46 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:54:24 [Warning] Aborted connection 49 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:54:24 [Warning] Aborted connection 48 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:56:28 [Warning] Aborted connection 50 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:56:28 [Warning] Aborted connection 51 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:59:24 [Warning] Aborted connection 53 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 13:59:24 [Warning] Aborted connection 52 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:07:17 [Warning] Aborted connection 55 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:07:17 [Warning] Aborted connection 54 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:08:48 [Warning] Aborted connection 56 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:08:48 [Warning] Aborted connection 57 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:09:59 [Warning] Aborted connection 59 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:10:38 [Warning] Aborted connection 62 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:10:38 [Warning] Aborted connection 61 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:16:42 [Warning] Aborted connection 63 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 14:18:24 [Warning] Aborted connection 70 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:18:24 [Warning] Aborted connection 71 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:42:48 [Warning] Aborted connection 72 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 14:42:48 [Warning] Aborted connection 73 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:20:40 [Warning] Aborted connection 93 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:20:40 [Warning] Aborted connection 92 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:26:08 [Warning] Aborted connection 94 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:26:08 [Warning] Aborted connection 95 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:26:36 [Warning] Aborted connection 77 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:26:36 [Warning] Aborted connection 87 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:26:36 [Warning] Aborted connection 97 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:26:36 [Warning] Aborted connection 98 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:26:36 [Warning] Aborted connection 78 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:27:38 [Warning] Aborted connection 74 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 15:29:30 [Warning] Aborted connection 99 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:29:30 [Warning] Aborted connection 100 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:31:57 [Warning] Aborted connection 108 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:31:57 [Warning] Aborted connection 107 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:34:58 [Warning] Aborted connection 109 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:34:58 [Warning] Aborted connection 110 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:36:23 [Warning] Warning: Enabling keys got errno 137, retrying
051215 15:37:39 [Warning] Aborted connection 102 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 15:37:39 [Warning] Aborted connection 103 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 15:37:39 [Warning] Aborted connection 104 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 15:38:41 [Warning] Aborted connection 114 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:38:41 [Warning] Aborted connection 113 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 15:41:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:41:32 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:41:36 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:41:36 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:42:24 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:42:24 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:43:22 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:43:22 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:43:42 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:43:42 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 15:53:34 [Warning] Warning: Enabling keys got errno 137, retrying
051215 15:54:50 [Warning] Aborted connection 132 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 15:55:56 [Warning] Warning: Enabling keys got errno 137, retrying
051215 15:56:36 [Warning] Aborted connection 136 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051215 16:02:57 [Warning] Aborted connection 148 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 16:02:57 [Warning] Aborted connection 149 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051215 16:08:50 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:08:50 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:08:53 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:08:53 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:09:15 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:09:15 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:02 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:02 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:02 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:02 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:10:09 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Table '.\aareg2\firma' is marked as crashed and last (automatic?) repair failed
051215 16:15:41 [Warning] Aborted connection 120 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051215 23:39:00 [Warning] Aborted connection 116 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
051216  0:00:08 [Warning] Aborted connection 117 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
051216  0:02:25 [Warning] Aborted connection 145 to db: 'unconnected' user: 'root' host: 'hjelpeserver.felleskontoret.local' (Got timeout reading communication packets)
051216  0:10:46 [Warning] Aborted connection 141 to db: 'aareg' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051216  0:12:27 [Warning] Aborted connection 158 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051216  0:22:54 [Warning] Aborted connection 140 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051216 17:29:30 [Warning] Aborted connection 160 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051216 18:02:17 [Warning] Aborted connection 165 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051216 21:30:45 [Warning] Aborted connection 161 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051219 10:44:52 [Warning] Aborted connection 181 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 10:44:52 [Warning] Aborted connection 179 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 10:49:51 [Warning] Aborted connection 186 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 10:49:51 [Warning] Aborted connection 185 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 11:25:40 [Warning] Aborted connection 192 to db: 'mytest' user: 'root' host: 'localhost' (Got an error reading communication packets)
051219 11:25:40 [Warning] Aborted connection 188 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051219 11:25:40 [Warning] Aborted connection 189 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051219 11:55:36 [Warning] Aborted connection 210 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 11:55:36 [Warning] Aborted connection 209 to db: 'mytest' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 11:55:36 [Warning] Aborted connection 206 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051219 20:01:12 [Warning] Aborted connection 213 to db: 'mytest' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051219 20:03:57 [Warning] Aborted connection 214 to db: 'aareg' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051219 20:05:24 [Warning] Aborted connection 219 to db: 'aareg' user: 'root' host: 'hjelpeserver.felleskontoret.local' (Got timeout reading communication packets)
051220 10:47:49 [Warning] Aborted connection 224 to db: 'mytest' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051220 10:47:49 [Warning] Aborted connection 226 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051220 11:01:20 [Warning] Aborted connection 236 to db: 'mytest' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051220 12:40:03 [Warning] Aborted connection 242 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051220 16:14:56 [Warning] Aborted connection 244 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051220 20:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 20:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 20:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 20:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 20:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 21:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:09:40 [Warning] Aborted connection 247 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051220 22:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 22:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051220 23:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:03:54 [Warning] Aborted connection 246 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051221  0:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  0:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  1:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:34:33 [Warning] Aborted connection 260 to db: 'aareg' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051221  2:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  2:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  3:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  4:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  5:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  6:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  7:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:11:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:21:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:31:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:41:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  8:51:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  9:01:46 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\aareg2\#sql-2c4_109.MYD' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221  9:09:57 [Warning] Aborted connection 268 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:11:46 [Warning] Warning: Enabling keys got errno 28, retrying
051221  9:14:29 [Warning] Aborted connection 271 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:15:01 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051221  9:15:03 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 265  user: 'root'

051221  9:15:03  InnoDB: Starting shutdown...
051221  9:15:04  InnoDB: Shutdown completed; log sequence number 0 935285340
051221  9:15:04 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051221  9:15:17 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hjelpeserver-bin' to avoid this problem.
051221  9:15:17  InnoDB: Started; log sequence number 0 935285340
051221  9:15:17 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt-log'  socket: ''  port: 3306  Official MySQL binary
051221  9:32:15 [Warning] Aborted connection 26 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:32:15 [Warning] Aborted connection 2 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:32:15 [Warning] Aborted connection 24 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:32:15 [Warning] Aborted connection 27 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221  9:39:41 [Warning] Aborted connection 23 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 12:16:00 [Warning] Aborted connection 37 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 12:29:51 [Warning] Aborted connection 42 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 12:32:03 [Warning] Aborted connection 48 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 12:38:22 [Warning] Aborted connection 29 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221 12:38:22 [Warning] Aborted connection 46 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051221 13:25:40 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\hjelpeserver-bin.000021' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221 13:35:40 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\hjelpeserver-bin.000021' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221 13:45:40 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Disk is full writing '.\hjelpeserver-bin.000021' (Errcode: 28). Waiting for someone to free space... Retry in 60 secs
051221 13:56:34 [Warning] Aborted connection 55 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 15:54:54 [Warning] Aborted connection 64 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051221 16:41:45 [Warning] Aborted connection 70 to db: 'mytest' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051222  0:26:43 [Warning] Aborted connection 51 to db: 'aareg2' user: 'root' host: 'localhost' (Got timeout reading communication packets)
051222 10:08:55 [Warning] Aborted connection 81 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051222 10:08:55 [Warning] Aborted connection 80 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051222 18:06:09 [Warning] Aborted connection 83 to db: 'styresak' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
051222 18:21:19 [Warning] Aborted connection 82 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
051222 18:22:32 [Warning] Aborted connection 84 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
051223  8:34:29 [Warning] Aborted connection 88 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051223  9:08:45 [Warning] Aborted connection 90 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051223 10:49:04 [Warning] Aborted connection 92 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051228  8:26:30 [Warning] Aborted connection 95 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228  8:26:30 [Warning] Aborted connection 97 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228  8:26:30 [Warning] Aborted connection 96 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228  8:50:49 [Warning] Aborted connection 103 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228  8:50:49 [Warning] Aborted connection 105 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228  8:50:49 [Warning] Aborted connection 104 to db: 'aareg' user: 'root' host: 'localhost' (Got an error reading communication packets)
051228 10:27:56 [Warning] Aborted connection 106 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051228 12:06:19  InnoDB: Started; log sequence number 0 935285340
051228 12:06:20 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051228 12:07:30 [Warning] Aborted connection 1 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051228 14:05:22 [Warning] Aborted connection 3 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051228 14:05:22 [Warning] Aborted connection 6 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051228 14:13:15 [Warning] Aborted connection 11 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 10:03:37 [Warning] Aborted connection 14 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 10:03:37 [Warning] Aborted connection 15 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 10:08:27 [Warning] Aborted connection 19 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 10:08:27 [Warning] Aborted connection 20 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 10:30:48 [Warning] Aborted connection 21 to db: 'information_schema' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
051229 12:01:42  InnoDB: Started; log sequence number 0 935285340
051229 12:01:42 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051229 12:05:13 [Warning] Aborted connection 3 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 12:05:13 [Warning] Aborted connection 4 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 12:35:22 [Warning] Aborted connection 18 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 12:35:22 [Warning] Aborted connection 20 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 12:35:29 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051229 12:35:31 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 14  user: 'root'

051229 12:35:31 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 13  user: 'root'

051229 12:35:31 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 9  user: 'root'

051229 12:35:31 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 8  user: 'root'

051229 12:35:31 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 7  user: 'root'

051229 12:35:31  InnoDB: Starting shutdown...
051229 12:35:33  InnoDB: Shutdown completed; log sequence number 0 935285340
051229 12:35:33 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051229 12:35:46  InnoDB: Started; log sequence number 0 935285340
051229 12:35:46 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051229 12:36:54 [Warning] Aborted connection 2 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 12:38:34 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

051229 12:38:36  InnoDB: Starting shutdown...
051229 12:38:38  InnoDB: Shutdown completed; log sequence number 0 935285340
051229 12:38:38 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

051229 12:38:43  InnoDB: Started; log sequence number 0 935285340
051229 12:38:43 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
051229 14:01:52 [Warning] Aborted connection 2 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 14:01:52 [Warning] Aborted connection 6 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
051229 21:14:04 [Warning] Aborted connection 12 to db: 'unconnected' user: 'root' host: 'hjelpeserver.felleskontoret.local' (Got timeout reading communication packets)
051230 11:46:58 [Warning] Aborted connection 15 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051230 13:33:54 [Warning] Aborted connection 18 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051230 13:34:04 [Warning] Aborted connection 20 to db: 'aareg' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
051231  0:13:51 [Warning] Aborted connection 21 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got timeout reading communication packets)
060101 14:42:45 [Warning] Aborted connection 16 to db: 'test' user: 'lorents' host: 'wxpdemo.felleskontoret.local' (Got a packet bigger than 'max_allowed_packet' bytes)
060102  9:54:54 [Warning] Aborted connection 24 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060102  9:54:54 [Warning] Aborted connection 29 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060102  9:54:54 [Warning] Aborted connection 25 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060102 12:58:55 [Warning] Aborted connection 39 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060102 16:47:04 [Warning] Aborted connection 35 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060102 16:47:04 [Warning] Aborted connection 37 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060103 10:34:45 [Warning] Aborted connection 44 to db: 'aareg' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060103 10:34:45 [Warning] Aborted connection 45 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 10:09:47 [Warning] Aborted connection 51 to db: 'test' user: 'lorents' host: 'wxplorents.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 58 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 59 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 61 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 62 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 57 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 55 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:01:04 [Warning] Aborted connection 60 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)
060104 11:18:43  InnoDB: Started; log sequence number 0 935285340
060104 11:18:43 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
060104 11:52:55 [Warning] Aborted connection 11 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 11:57:13  InnoDB: Started; log sequence number 0 935285340
060104 11:57:13 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
060104 12:28:24  InnoDB: Started; log sequence number 0 935285340
060104 12:28:24 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.15-nt'  socket: ''  port: 3306  Official MySQL binary
060104 12:55:23 [Warning] Aborted connection 2 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 12:55:23 [Warning] Aborted connection 1 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 13:23:16 [Warning] Aborted connection 21 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 13:23:16 [Warning] Aborted connection 18 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 13:23:16 [Warning] Aborted connection 20 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 13:30:13 [Warning] Aborted connection 25 to db: 'aareg2' user: 'root' host: 'localhost' (Got an error reading communication packets)
060104 13:41:25 [Warning] Aborted connection 32 to db: 'aareg2' user: 'steinar' host: 'wxpsteinar.felleskontoret.local' (Got an error reading communication packets)