|
Re: mysql protocol problems - monit 4.5.1: msg#00034monitoring.monit.general
as you can see, there is nothing to suggest a problem. the reason it is restarting is because of monit not being able to connect and doing a restart. here is my mysqld.log for the last day: 050812 20:23:54 mysqld started 050812 20:23:54 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution A mysqld process already exists at Fri Aug 12 20:24:15 CDT 2005 A mysqld process already exists at Sat Aug 13 10:48:59 CDT 2005 050813 10:55:23 [Note] /usr/libexec/mysqld: Normal shutdown 050813 10:55:23 InnoDB: Starting shutdown... 050813 10:55:24 InnoDB: Shutdown completed; log sequence number 0 43644 050813 10:55:24 [Note] /usr/libexec/mysqld: Shutdown complete 050813 10:55:24 mysqld ended 050813 10:55:25 mysqld started 050813 10:55:25 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 10:55:36 [Note] /usr/libexec/mysqld: Normal shutdown 050813 10:55:36 InnoDB: Starting shutdown... 050813 10:55:38 InnoDB: Shutdown completed; log sequence number 0 43644 050813 10:55:38 [Note] /usr/libexec/mysqld: Shutdown complete 050813 10:55:38 mysqld ended 050813 10:55:39 mysqld started 050813 10:55:39 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 10:57:25 [Note] /usr/libexec/mysqld: Normal shutdown 050813 10:57:25 InnoDB: Starting shutdown... 050813 10:57:27 InnoDB: Shutdown completed; log sequence number 0 43644 050813 10:57:27 [Note] /usr/libexec/mysqld: Shutdown complete 050813 10:57:27 mysqld ended 050813 10:57:28 mysqld started 050813 10:57:28 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 10:59:28 [Note] /usr/libexec/mysqld: Normal shutdown 050813 10:59:28 InnoDB: Starting shutdown... 050813 10:59:31 InnoDB: Shutdown completed; log sequence number 0 43644 050813 10:59:31 [Note] /usr/libexec/mysqld: Shutdown complete 050813 10:59:31 mysqld ended 050813 10:59:31 mysqld started 050813 10:59:31 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 11:01:31 [Note] /usr/libexec/mysqld: Normal shutdown 050813 11:01:31 InnoDB: Starting shutdown... 050813 11:01:34 InnoDB: Shutdown completed; log sequence number 0 43644 050813 11:01:34 [Note] /usr/libexec/mysqld: Shutdown complete 050813 11:01:34 mysqld ended 050813 11:01:34 mysqld started 050813 11:01:34 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 11:03:34 [Note] /usr/libexec/mysqld: Normal shutdown 050813 11:03:34 InnoDB: Starting shutdown... 050813 11:03:37 InnoDB: Shutdown completed; log sequence number 0 43644 050813 11:03:37 [Note] /usr/libexec/mysqld: Shutdown complete 050813 11:03:37 mysqld ended 050813 11:03:37 mysqld started 050813 11:03:38 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 050813 12:52:32 [Note] /usr/libexec/mysqld: Normal shutdown 050813 12:52:32 InnoDB: Starting shutdown... 050813 12:52:35 InnoDB: Shutdown completed; log sequence number 0 43644 050813 12:52:35 [Note] /usr/libexec/mysqld: Shutdown complete 050813 12:52:35 mysqld ended 050813 12:52:36 mysqld started 050813 12:52:36 InnoDB: Started; log sequence number 0 43644 /usr/libexec/mysqld: ready for connections. Version: '4.1.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution maybe the monit docs should state exactly what needs to be changed for it to work. so what needs to be set/changed? i simply do not know. steve On Sat, Aug 13, 2005 at 09:49:05PM +0200, Martin Pala wrote: > For mysql test to succeed, it is also needed to set access on mysql > side, otherwise monit request can be refused - you should check mysql > logs for errors ... > > Martin > > unruhtech wrote: > >here is what i am getting in my log file: > > > >[CDT Aug 13 12:55:10] MYSQL: error receiving login response -- Resource > >temporarily unavailable > >[CDT Aug 13 12:55:10] 'mysql' failed protocol test [MYSQL] at > >INET[192.168.1.34:3306]. > > > >here is my monitrc entry (pretty much right out of the docs): > > > >check process mysql with pidfile /var/run/mysqld/mysqld.pid > > group database > > mode active > > start program = "/etc/init.d/mysqld start" > > stop program = "/etc/init.d/mysqld stop" > > if failed host 192.168.1.34 port 3306 protocol mysql then restart > > if 5 restarts within 5 cycles then timeout > > > >running on FC4 and using monit 4.5.1 > > > >is this a mysql config problem (no clue what) or a monit problem? > >ideas? > > > >thanks, > >steve > > > > > >-- > >To unsubscribe: > >http://lists.nongnu.org/mailman/listinfo/monit-general > > > -- > To unsubscribe: > http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: mysql protocol problems - monit 4.5.1: 00034, Martin Pala |
|---|---|
| Next by Date: | Re: mysql protocol problems - monit 4.5.1: 00034, Martin Pala |
| Previous by Thread: | Re: mysql protocol problems - monit 4.5.1i: 00034, Martin Pala |
| Next by Thread: | Re: mysql protocol problems - monit 4.5.1: 00034, Martin Pala |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |