percona slave mysql processes crashed

Movenium's Avatar

Movenium

04 Jan, 2018 10:37 AM

Hi,

for some reason farmid 20856 slaves wen't down today at 08:45 ... after going trough some logs I found out that master server was rebooted just before

 scalrizer log
2018-01-04 08:42:56+00:00 - INFO - Server is rebooting...
2018-01-04 08:42:56+00:00 - INFO - Stopping service: Instance is going to reboot

Why master server did reboot and further more why did that cause slaves to stop mysql? Was that somekind of bug or do we have to do something to prevent this to happen again? And do you think we need to be worried that slaves could go down again for same reason?

update log said
2018-01-04 08:42:55,123+00:00 - INFO - agent.scalarizr.updateclient - [pid: 23261] UpdateClient terminated
2018-01-04 08:44:16,067+00:00 - INFO - agent.scalarizr.updateclient - [pid: 1297] Starting UpdateClient 6.1.2 (corev2)
2018-01-04 08:44:16,084+00:00 - INFO - agent.scalarizr.updateclient - Starting API on *:8008
2018-01-04 08:44:16,093+00:00 - DEBUG - agent.scalarizr.updateclient - State transition: completed -> completed

Veikko Salminen

  1. Support Staff 1 Posted by Igor Savchenko on 04 Jan, 2018 05:55 PM

    Igor Savchenko's Avatar

    The server was rebooted by Amazon (most likely due to recent vulnerabilities in Intel CPUs).

    What is the current status of your MySQL cluster? All good or slaves are still down?

  2. 2 Posted by Movenium on 05 Jan, 2018 05:24 AM

    Movenium's Avatar

    everything is ok now .. thanks for the answer

  3. Igor Savchenko closed this discussion on 05 Jan, 2018 04:19 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac