Hi, We had this discussion a while back regarding the management nodes fencing when the MySQL deamon is disconnected and session state is lost. I believe recovery was going to be implemented in later versions of CS. If you would like to review the conversation please see below "management server DB timeout" http://mail-archives.apache.org/mod_mbox/cloudstack-users/201401.mbox/%3c52e00f0d.6090...@cloudops.com%3E
There is also: http://mail-archives.apache.org/mod_mbox/cloudstack-users/201311.mbox/%3cd2ee6b3265ad864eb3ea4f5c670d256f273ce...@exdfo01l-crp-06.webmdhealth.net%3E You may want to consider setting up HA for the MySQL daemon, cloudstack currently sees MySQL as a dependency (because MySQL is it's datasource) so fencing is the expected behaviour. The management server simply doesn't have the information available to operate. If setting up HA (with synced session states) is not feasible, you may also consider my crontab script mentioned in the first link. This will restart the cloudstack-management service which the script detects the management server is no longer running (tested on Ubuntu 12.04). Hope this helps, Marty On Mon, Feb 17, 2014 at 10:42 AM, Kmiotek, Daniel <daniel.kmio...@astiga.com > wrote: > 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 >
