mysql stops responding overnight
Posted by: onlinebendigo (---.gw.connect.com.au)
Date: May 27, 2008 04:17PM

hello can any one help

mysql stops responding overnight any Ideas?
I believe it may be to no traffic for 5 hrs?


don't know help please

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: toivo (---.nsw.bigpond.net.au)
Date: May 27, 2008 04:29PM

Hi,

That is odd, the service should never stop unless you stop that service or all services from the WAMP icon in the System Tray.

Do you by any chance have a power saving setting set to ON on the server? If it is set to Advanced in BIOS or Windows, turn it off completely in both places.

Regards,

toivo
Sydney, Australia

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: stevenmartin99 (---.b-ras1.blp.dublin.eircom.net)
Date: May 27, 2008 04:31PM

no reason for this to happen

try this lil app i made,,, download here>>> [pampserver.com]

unzip it ,

then set up a scheduled task in start>programfiles>accessoires>sysytem tools


get it to run

endwamp.bat every hour during the nighrt maybe..


i know its not a great solution but i think its maybe ur pc thats couasing the problem more then wamp

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: onlinebendigo (---.gw.connect.com.au)
Date: May 27, 2008 04:34PM

cool Will try

It is only data base that stops I am using php nuke evo

I have no power setting in server 2003 enabled will re boot and get back to you I am using the new wamp didi not have this problem prior


Thanks for your continual support you guy bring the meaning to the internet

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: onlinebendigo (---.gw.connect.com.au)
Date: May 28, 2008 10:42AM

Dead on awesome bat file did not crash last night run it ever 4.5hrs as Serve stops responding after 5hrs

You guys are good all you need to do now is do a noob install to include a mail web server and interface ie include hmail in the program??????


thankyou all great product will donate once i make some money

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: toivo (---.nsw.bigpond.net.au)
Date: May 28, 2008 11:56AM

It would be interesting to know what is recorded in the MySQL log when it stops responding. Could you have a look and post the relevant lines here. The file is c:\wamp\logs\mysql.log.

Regards,

toivo
Sydney, Australia

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: onlinebendigo (---.gw.connect.com.au)
Date: May 28, 2008 12:06PM

080526 22:14:53 InnoDB: Error: page 354 log sequence number 0 25114308
InnoDB: is in the future! Current system log sequence number 0 13398245.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:19:34 [Note] wampmysqld: Normal shutdown

080526 22:19:34 InnoDB: Starting shutdown...
080526 22:19:36 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:19:36 [Note] wampmysqld: Shutdown complete

080526 22:19:38 InnoDB: Started; log sequence number 0 13398255
080526 22:19:38 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:19:38 [ERROR] Aborting

080526 22:19:38 InnoDB: Starting shutdown...
080526 22:19:41 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:19:41 [Note] wampmysqld: Shutdown complete

080526 22:19:55 InnoDB: Started; log sequence number 0 13398255
080526 22:19:55 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:19:55 [ERROR] Aborting

080526 22:19:55 InnoDB: Starting shutdown...
080526 22:19:58 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:19:58 [Note] wampmysqld: Shutdown complete

080526 22:20:38 InnoDB: Started; log sequence number 0 13398255
080526 22:20:38 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:20:38 [ERROR] Aborting

080526 22:20:38 InnoDB: Starting shutdown...
080526 22:20:40 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:20:40 [Note] wampmysqld: Shutdown complete

080526 22:20:57 InnoDB: Started; log sequence number 0 13398255
080526 22:20:57 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:20:57 [ERROR] Aborting

080526 22:20:57 InnoDB: Starting shutdown...
080526 22:21:00 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:21:00 [Note] wampmysqld: Shutdown complete

080526 22:21:34 InnoDB: Started; log sequence number 0 13398255
080526 22:21:34 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:21:34 [ERROR] Aborting

080526 22:21:34 InnoDB: Starting shutdown...
080526 22:21:36 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:21:36 [Note] wampmysqld: Shutdown complete

080526 22:22:20 InnoDB: Started; log sequence number 0 13398255
080526 22:22:20 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080526 22:22:20 [ERROR] Aborting

080526 22:22:20 InnoDB: Starting shutdown...
080526 22:22:22 InnoDB: Shutdown completed; log sequence number 0 13398255
080526 22:22:22 [Note] wampmysqld: Shutdown complete

080526 22:23:52 InnoDB: Started; log sequence number 0 13398255
080526 22:23:52 [Note] wampmysqld: ready for connections.
Version: '5.0.51b-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
080526 22:23:58 InnoDB: Error: page 63 log sequence number 0 23997735
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:23:58 InnoDB: Error: page 60 log sequence number 0 23997735
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:24:52 InnoDB: Error: page 351 log sequence number 0 25114346
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:24:52 InnoDB: Error: page 352 log sequence number 0 25114280
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:24:52 InnoDB: Error: page 353 log sequence number 0 25114294
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:24:52 InnoDB: Error: page 354 log sequence number 0 25114308
InnoDB: is in the future! Current system log sequence number 0 13398265.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:32:33 InnoDB: Error: page 336 log sequence number 0 27782158
InnoDB: is in the future! Current system log sequence number 0 13399356.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080526 22:32:33 InnoDB: Error: page 54 log sequence number 0 27782158
InnoDB: is in the future! Current system log sequence number 0 13399356.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 8:08:14 InnoDB: Error: page 344 log sequence number 0 23550085
InnoDB: is in the future! Current system log sequence number 0 13426083.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 9:00:57 InnoDB: Error: page 329 log sequence number 0 23309353
InnoDB: is in the future! Current system log sequence number 0 13426503.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 13:57:23 [Note] wampmysqld: Normal shutdown

080527 13:57:25 [Warning] wampmysqld: Forcing close of thread 2621 user: 'scottmacrae'

080527 13:57:25 [Warning] wampmysqld: Forcing close of thread 2620 user: 'scottmacrae'

080527 13:57:25 [Warning] wampmysqld: Forcing close of thread 146 user: 'scottmacrae'

080527 13:57:25 InnoDB: Starting shutdown...
080527 13:57:27 InnoDB: Shutdown completed; log sequence number 0 13433094
080527 13:57:27 [Note] wampmysqld: Shutdown complete

080527 13:58:24 InnoDB: Started; log sequence number 0 13433094
080527 13:58:24 [Note] wampmysqld: ready for connections.
Version: '5.0.51b-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
080527 14:00:16 InnoDB: Error: page 54 log sequence number 0 27782158
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:00:16 InnoDB: Error: page 59 log sequence number 0 25107019
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:00:16 InnoDB: Error: page 60 log sequence number 0 23997735
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:00:16 InnoDB: Error: page 63 log sequence number 0 23997735
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:00:26 InnoDB: Error: page 336 log sequence number 0 27782158
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:07:01 InnoDB: Error: page 351 log sequence number 0 25114346
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:07:01 InnoDB: Error: page 352 log sequence number 0 25114280
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:07:01 InnoDB: Error: page 353 log sequence number 0 25114294
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080527 14:07:01 InnoDB: Error: page 354 log sequence number 0 25114308
InnoDB: is in the future! Current system log sequence number 0 13433634.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080528 8:33:16 InnoDB: Error: page 344 log sequence number 0 23550085
InnoDB: is in the future! Current system log sequence number 0 14339181.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080528 9:03:24 InnoDB: Error: page 329 log sequence number 0 23309353
InnoDB: is in the future! Current system log sequence number 0 14339811.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.
080528 9:10:29 InnoDB: Error: page 325 log sequence number 0 23295523
InnoDB: is in the future! Current system log sequence number 0 14341542.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: [dev.mysql.com]
InnoDB: for more information.

Options: ReplyQuote
Re: mysql stops responding overnight
Posted by: onlinebendigo (---.gw.connect.com.au)
Date: May 28, 2008 12:07PM

dont make sense to me

Options: ReplyQuote


Sorry, only registered users may post in this forum.