Page 4 of 4

Re: Rename the service problem

Posted: Tue Mar 10, 2015 1:09 am
by phyo
We did not set max connection limits on the both database.

Method replication: Master to Master

Re: Rename the service problem

Posted: Tue Mar 10, 2015 2:36 pm
by tgriep
Can you post your MYSQL log from both of your MYSQL server's during the time you are having the problem on the Nagios server?

Re: Rename the service problem

Posted: Wed Mar 11, 2015 10:14 pm
by phyo
Server 1
150305 11:04:41 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000286' at position 829942728, relay log './mysqld-relay-bin.000078' position: 11340156
150305 11:04:41 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysqld-bin.000286' at position 829942728
150305 14:44:25 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1315' LIMIT 1
150305 14:44:34 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1313' LIMIT 1
150305 14:44:43 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1202' LIMIT 1
150305 14:44:53 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1204' LIMIT 1
150305 14:54:25 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1330' LIMIT 1
150309 14:39:52 [Note] Error reading relay log event: slave SQL thread was killed
150309 14:39:52 [Note] Slave I/O thread killed while reading event
150309 14:39:52 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000293', position 926676719
150310 12:54:26 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1482' LIMIT 1
150310 14:15:20 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='762' LIMIT 1
150310 14:15:44 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='763' LIMIT 1
150312 11:08:55 [Note] /usr/libexec/mysqld: Normal shutdown

150312 11:08:55 [Note] Event Scheduler: Purging the queue. 0 events
150312 11:08:57 InnoDB: Starting shutdown...
150312 11:09:00 InnoDB: Shutdown completed; log sequence number 0 44253
150312 11:09:00 [Note] /usr/libexec/mysqld: Shutdown complete

150312 11:09:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150312 11:09:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150312 11:09:00 [Warning] 'for replication startup options' is deprecated and will be removed in a future release. Please use ''CHANGE MASTER'' instead.
150312 11:09:00 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
150312 11:09:00 InnoDB: Initializing buffer pool, size = 8.0M
150312 11:09:00 InnoDB: Completed initialization of buffer pool
150312 11:09:00 InnoDB: Started; log sequence number 0 44253
150312 11:09:00 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.
150312 11:09:00 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000293' at position 926676719, relay log './mysqld-relay-bin.000099' position: 926676865
150312 11:09:00 [Note] Event Scheduler: Loaded 0 events
150312 11:09:00 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150312 11:09:00 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysqld-bin.000293' at position 926676719
150312 11:09:40 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
150312 11:09:40 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysqld-bin.000297' at position 739038225
150312 11:09:40 [ERROR] Slave I/O: error reconnecting to master '[email protected]:3306' - retry-time: 60 retries: 86400, Error_code: 2013
150312 11:10:40 [Note] Slave: connected to master '[email protected]:3306',replication resumed in log 'mysqld-bin.000297' at position 739038225
150312 11:10:46 [Note] Slave SQL thread exiting, replication stopped in log 'mysqld-bin.000294' at position 252437662
150312 11:10:46 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000298', position 280122932

Server 2
150305 10:41:39 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000454' at position 1011236979, relay log './mysqld-relay-bin.000078' position: 1011237125
150305 10:41:39 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysqld-bin.000454' at position 1011236979
150305 10:42:27 [Note] Error reading relay log event: slave SQL thread was killed
150305 10:42:27 [Note] Slave I/O thread killed while reading event
150305 10:42:27 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000454', position 1020974587
150305 11:04:46 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000454' at position 1020974587, relay log './mysqld-relay-bin.000079' position: 9737860
150305 11:04:46 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysqld-bin.000454' at position 1020974587
150305 14:44:25 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1315' LIMIT 1
150305 14:44:34 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1313' LIMIT 1
150305 14:44:43 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1202' LIMIT 1
150305 14:44:53 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1204' LIMIT 1
150305 14:54:25 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1330' LIMIT 1
150309 14:40:16 [Note] Error reading relay log event: slave SQL thread was killed
150309 14:40:16 [Note] Slave I/O thread killed while reading event
150309 14:40:16 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000463', position 444506334
150312 11:09:40 [Note] /usr/libexec/mysqld: Normal shutdown

150312 11:09:40 [Note] Event Scheduler: Purging the queue. 0 events
150312 11:09:42 InnoDB: Starting shutdown...
150312 11:09:44 InnoDB: Shutdown completed; log sequence number 0 44233
150312 11:09:44 [Note] /usr/libexec/mysqld: Shutdown complete

150312 11:09:44 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150312 11:09:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150312 11:09:46 [Warning] 'for replication startup options' is deprecated and will be removed in a future release. Please use ''CHANGE MASTER'' instead.
150312 11:09:46 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
150312 11:09:46 InnoDB: Initializing buffer pool, size = 8.0M
150312 11:09:46 InnoDB: Completed initialization of buffer pool
150312 11:09:46 InnoDB: Started; log sequence number 0 44233
150312 11:09:46 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.
150312 11:09:46 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000463' at position 444506334, relay log './mysqld-relay-bin.000106' position: 444506480
150312 11:09:46 [Note] Slave I/O thread: connected to master '[email protected]:3306',replication started in log 'mysqld-bin.000463' at position 444506334
150312 11:09:46 [Note] Event Scheduler: Loaded 0 events
150312 11:09:46 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
150312 11:11:01 [Note] Slave SQL thread exiting, replication stopped in log 'mysqld-bin.000463' at position 668723612
150312 11:11:01 [Note] Slave I/O thread killed while reading event
150312 11:11:01 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000470', position 3057597

Currently we are stopping the mysql replication.

Re: Rename the service problem

Posted: Thu Mar 12, 2015 12:59 pm
by tgriep
Thanks for the reply. We don't support MYSQL replication for NagiosXI.
I couldn't find any definitive fixes to the errors that you posted other than a hint to network issues.

Re: Rename the service problem

Posted: Tue Mar 17, 2015 10:12 pm
by phyo
tgriep wrote:Thanks for the reply. We don't support MYSQL replication for NagiosXI.
I couldn't find any definitive fixes to the errors that you posted other than a hint to network issues.
So how can we configure High Availability with Two Nagios XI?

Re: Rename the service problem

Posted: Wed Mar 18, 2015 10:15 am
by ssax
Here are the available options for HA for Nagios XI.

http://assets.nagios.com/downloads/nagi ... ios-XI.pdf