Mysql shutdown automatically

Mysql shutdown automatically

am 04.11.2010 16:42:17 von Paras pradhan

Hi,

I found that mysql server stops and starts automatically from time to
time. I am not sure what is causing this.

Log:
-

100923 18:51:29 mysqld started
100923 18:51:29 InnoDB: Started; log sequence number 0 43655
100923 18:51:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution
100928 0:14:28 [Note] /usr/libexec/mysqld: Normal shutdown

100928 0:15:33 InnoDB: Starting shutdown...
100928 0:15:34 InnoDB: Shutdown completed; log sequence number 0 43655
100928 0:15:34 [Note] /usr/libexec/mysqld: Shutdown complete

100928 00:15:34 mysqld ended

100928 00:16:42 mysqld started
100928 0:16:42 InnoDB: Started; log sequence number 0 43655
100928 0:16:43 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution
101103 22:28:24 [Note] /usr/libexec/mysqld: Normal shutdown

A mysqld process already exists at Wed Nov 3 22:29:25 CDT 2010
101103 22:29:47 InnoDB: Starting shutdown...
101103 22:29:48 InnoDB: Shutdown completed; log sequence number 0 43655
101103 22:29:48 [Note] /usr/libexec/mysqld: Shutdown complete

101103 22:29:48 mysqld ended

101104 00:47:08 mysqld started
101104 0:47:08 InnoDB: Started; log sequence number 0 43655
101104 0:47:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77' socket: '/var/lib/mysql/mysql.sock' port: 3306
Source distribution
--


I don't see any CPU, mem or other resource overloaded.

Mysql version is mysql-server-5.0.77-4.el5_5.4


Thanks!
Paras.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: Mysql shutdown automatically

am 04.11.2010 17:42:31 von Paras pradhan

I don't see any thing written dmesg and message releated to this.

Does this have to do something with performance tuning? or can be
tuned to make better.

my.cnf looks:

[mysqld]
key_buffer =3D 128M
sort_buffer =3D 1M
join_buffer =3D 1M
max_allowed_packet =3D 8M
max_heap_table_size =3D 16M
table_cache =3D 1024
sort_buffer_size =3D 8M
read_buffer_size =3D 1M
read_rnd_buffer_size =3D 768K
myisam_sort_buffer_size =3D 48M
thread_cache_size =3D 512
query_cache_type =3D 1
query_cache_limit =3D 4M
query_cache_size =3D 512M
tmp_table_size =3D 16M
thread_concurrency =3D 8
max_write_lock_count =3D 1 #To force MySQL to temporarily elevate the
priority of all SELECT statements that are waiting for a table after a
specific number of inserts to the table occur. This allows READ loc
ks after a certain number of WRITE locks.
low_priority_updates =3D 1
max-connections=3D300

[isamchk]
key_buffer =3D 64M
sort_buffer =3D 64M
read_buffer =3D 16M
write_buffer =3D 16M

[myisamchk]
key_buffer =3D 64M
sort_buffer =3D 64M
read_buffer =3D 16M
write_buffer =3D 16M


This mysql is a backend to the php based webmail client and has
normally around 100 concurrent users.

I don't see CPU and Mem crossing 15% by mysqld even at peak times.

Thanks!
Paras.

On Thu, Nov 4, 2010 at 10:50 AM, Michael Dykman wrote:
> Check dmsg or the contents of /var/log/messages for hardware/system
> notifications. =A0I would guess some fatal error is shutting down mysql
> hard and mysql_safe is bringing it right back up again (which is it's
> job).
>
> =A0- michael dykman
>
>
> On Thu, Nov 4, 2010 at 11:42 AM, Paras pradhan w=
rote:
>> Hi,
>>
>> I found that mysql server stops and starts automatically from time to
>> time. I am not sure what is causing this.
>>
>> Log:
>> -
>>
>> 100923 18:51:29 =A0mysqld started
>> 100923 18:51:29 =A0InnoDB: Started; log sequence number 0 43655
>> 100923 18:51:30 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.77' =A0socket: '/var/lib/mysql/mysql.sock' =A0port: 3306
>> Source distribution
>> 100928 =A00:14:28 [Note] /usr/libexec/mysqld: Normal shutdown
>>
>> 100928 =A00:15:33 =A0InnoDB: Starting shutdown...
>> 100928 =A00:15:34 =A0InnoDB: Shutdown completed; log sequence number 0 4=
3655
>> 100928 =A00:15:34 [Note] /usr/libexec/mysqld: Shutdown complete
>>
>> 100928 00:15:34 =A0mysqld ended
>>
>> 100928 00:16:42 =A0mysqld started
>> 100928 =A00:16:42 =A0InnoDB: Started; log sequence number 0 43655
>> 100928 =A00:16:43 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.77' =A0socket: '/var/lib/mysql/mysql.sock' =A0port: 3306
>> Source distribution
>> 101103 22:28:24 [Note] /usr/libexec/mysqld: Normal shutdown
>>
>> A mysqld process already exists at =A0Wed Nov 3 22:29:25 CDT 2010
>> 101103 22:29:47 =A0InnoDB: Starting shutdown...
>> 101103 22:29:48 =A0InnoDB: Shutdown completed; log sequence number 0 436=
55
>> 101103 22:29:48 [Note] /usr/libexec/mysqld: Shutdown complete
>>
>> 101103 22:29:48 =A0mysqld ended
>>
>> 101104 00:47:08 =A0mysqld started
>> 101104 =A00:47:08 =A0InnoDB: Started; log sequence number 0 43655
>> 101104 =A00:47:08 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.77' =A0socket: '/var/lib/mysql/mysql.sock' =A0port: 3306
>> Source distribution
>> --
>>
>>
>> I don't see any CPU, mem or other resource overloaded.
>>
>> Mysql version is mysql-server-5.0.77-4.el5_5.4
>>
>>
>> Thanks!
>> Paras.
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: =A0 =A0http://lists.mysql.com/mysql?unsub=3Dmdykman@gmai=
l.com
>>
>>
>
>
>
> --
> =A0- michael dykman
> =A0- mdykman@gmail.com
>
> =A0May the Source be with you.
>

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg