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 = 128M sort_buffer = 1M join_buffer = 1M max_allowed_packet = 8M max_heap_table_size = 16M table_cache = 1024 sort_buffer_size = 8M read_buffer_size = 1M read_rnd_buffer_size = 768K myisam_sort_buffer_size = 48M thread_cache_size = 512 query_cache_type = 1 query_cache_limit = 4M query_cache_size = 512M tmp_table_size = 16M thread_concurrency = 8 max_write_lock_count = 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 = 1 max-connections=300 [isamchk] key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 16M [myisamchk] key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 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 <mdyk...@gmail.com> wrote: > Check dmsg or the contents of /var/log/messages for hardware/system > notifications. I 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). > > - michael dykman > > > On Thu, Nov 4, 2010 at 11:42 AM, Paras pradhan <pradhanpa...@gmail.com> wrote: >> 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=mdyk...@gmail.com >> >> > > > > -- > - michael dykman > - mdyk...@gmail.com > > May 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=arch...@jab.org
