SEO

In my mysql server err file the following messages is repeated over
and over again evry 3 seconds. What is wrong?

Number of processes running now: 0
080421 10:35:55 mysqld restarted
080421 10:35:55 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...
080421 10:35:55 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43655.
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
080421 10:35:55 InnoDB: Started; log sequence number 0 43655
080421 10:35:55 [Note] Recovering after a crash using mysql-bin
080421 10:35:55 [Note] Starting crash recovery...
080421 10:35:55 [Note] Crash recovery finished.
080421 10:35:55 [Note] /opt/db/mysql/libexec/mysqld: ready for
connections.
Version: '5.0.21-log' socket: '/tmp/mysql.sock' port: 3306 Source
distribution

On Mon, 21 Apr 2008 01:48:32 -0700 (PDT), Mattias wrote:
> In my mysql server err file the following messages is repeated over
> and over again evry 3 seconds. What is wrong?
>
> Number of processes running now: 0
> 080421 10:35:55 mysqld restarted
> 080421 10:35:55 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...
> 080421 10:35:55 InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 43655.
> InnoDB: Doing recovery: scanned up to log sequence number 0 43655
> 080421 10:35:55 InnoDB: Started; log sequence number 0 43655
> 080421 10:35:55 [Note] Recovering after a crash using mysql-bin
> 080421 10:35:55 [Note] Starting crash recovery...
> 080421 10:35:55 [Note] Crash recovery finished.
> 080421 10:35:55 [Note] /opt/db/mysql/libexec/mysqld: ready for
> connections.
> Version: '5.0.21-log' socket: '/tmp/mysql.sock' port: 3306 Source
> distribution

Is it always "Number of processes running now: 0"?

--
The greatest dangers to liberty lurk in insidious encroachment by men of
zeal, well-meaning but without understanding. -Justice Louis D. Brandeis

Yes, allways 0.

I'v got the database to start again now. But I have no idea why! This
is what I did.

I am on a debian linux system. I had mysql 5.0.21 installed. I had
downloaded the sourcecode and compiled it on the machine. I installed
into /opt/db/mysql. Then suddenly this happend that it restated allthe
time, evry 3 seconds or so.

I deleted the directory
rm -rf /opt/db/mysql
and killed all processes.

Then i made a make install again from the souce directory.

Stared it again. The same problem.

REpeaded the delete of the directory and installed version 5.1
instead. Same problem. Stoped the server again and used debian
command:

apt-get install mysql-server

However that failed on my machine.

Then I stated mysqld in the /opt/db/mysql directory.
Now it works. I don't know why.

All I can do now is to hope that it does not happen again.

I am not out of disc space.

$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 73G 3.4G 66G 5% /
tmpfs 116M 0 116M 0% /lib/init/rw
udev 10M 24K 10M 1% /dev
tmpfs 116M 0 116M 0% /dev/shm

Here are som more from the log file so you can see the repeeted error
message.

Number of processes running now: 0
080421 11:32:12 mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
080421 11:32:12 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...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
080421 11:32:12 InnoDB: Starting an apply batch of log records to the
database.
...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
19 20 21
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
45 46 47 48
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
72 73 74 7
5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
99
InnoDB: Apply batch completed
080421 11:32:13 InnoDB: Started; log sequence number 0 43655
080421 11:32:13 [Note] Recovering after a crash using mysql-bin
080421 11:32:13 [Note] Starting crash recovery...
080421 11:32:13 [Note] Crash recovery finished.
080421 11:32:13 [Note] /opt/db/mysql/libexec/mysqld: ready for
connections.
Version: '5.0.51a-log' socket: '/tmp/mysql.sock' port: 3306 Source
distributi
on

Number of processes running now: 0
080421 11:32:14 mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
080421 11:32:14 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...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
080421 11:32:14 InnoDB: Starting an apply batch of log records to the
database.
...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
19 20 21
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
45 46 47 48
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
72 73 74 7
5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
99
InnoDB: Apply batch completed
080421 11:32:14 InnoDB: Started; log sequence number 0 43655
080421 11:32:14 [Note] Recovering after a crash using mysql-bin
080421 11:32:14 [Note] Starting crash recovery...
080421 11:32:14 [Note] Crash recovery finished.
080421 11:32:14 [Note] /opt/db/mysql/libexec/mysqld: ready for
connections.
Version: '5.0.51a-log' socket: '/tmp/mysql.sock' port: 3306 Source
distributi
on

Number of processes running now: 0
080421 11:32:15 mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
080421 11:32:15 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...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
080421 11:32:15 InnoDB: Starting an apply batch of log records to the
database.
...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
19 20 21
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
45 46 47 48
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
72 73 74 7
5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
99
InnoDB: Apply batch completed
080421 11:32:15 InnoDB: Started; log sequence number 0 43655
080421 11:32:15 [Note] Recovering after a crash using mysql-bin
080421 11:32:15 [Note] Starting crash recovery...
080421 11:32:15 [Note] Crash recovery finished.
080421 11:32:15 [Note] /opt/db/mysql/libexec/mysqld: ready for
connections.
Version: '5.0.51a-log' socket: '/tmp/mysql.sock' port: 3306 Source
distributi
on