Hey Erik, in the log is just written, that the server crash because they can't connect the MySQL-instance.
>From the mysql.log: InnoDB: Progress in percents: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 53014, file name ./mysql-bin.000012 140217 9:44:37 InnoDB: Started; log sequence number 0 532327347 140217 9:44:37 [Note] Recovering after a crash using mysql-bin 140217 9:44:37 [Note] Starting crash recovery... 140217 9:44:37 [Note] Crash recovery finished. 140217 9:44:37 [Note] Event Scheduler: Loaded 0 events 140217 9:44:37 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.71-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution -----Ursprüngliche Nachricht----- Von: Erik Weber [mailto:terbol...@gmail.com] Gesendet: Montag, 17. Februar 2014 10:45 An: users@cloudstack.apache.org Betreff: Re: MySQL-Server on Management-Node On Mon, Feb 17, 2014 at 10:39 AM, Kmiotek, Daniel <daniel.kmio...@astiga.com > wrote: > Hi! > > After two days of running CloudStack the MySQL-Daemon crashed and I > must move the PID. > Then I must restart the MySQL- und CloudStack-Management-Daemon. > How can I prevent the crash? > > Anything in the logs? -- Erik
