Anyone have any idea why the management service would refuse to start if the DB server is configured as a master for replication?
log_bin=mysql-bin server_id=1 Adding the above the my.cnf file of my DB server, restarting mysql then restarting cloudstack-managment will cause cloudstack to get hung on startup here. 2014-06-09 18:25:33,769 INFO [c.c.u.c.ComponentContext] (main:null) Starting com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_9da5499b 2014-06-09 18:25:33,769 INFO [c.c.u.c.ComponentContext] (main:null) Starting com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_847fb98c 2014-06-09 18:25:33,769 INFO [c.c.u.c.ComponentContext] (main:null) Starting com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_7fce3ee6 2014-06-09 18:25:33,769 INFO [c.c.u.c.ComponentContext] (main:null) Starting com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_d70c9e3c 2014-06-09 18:25:33,769 INFO [c.c.u.c.ComponentContext] (main:null) Starting com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_23d38b1 That is the last few lines of the management-server.log and it will hang there indefinitely. I noticed this on startup as well. 2014-06-09 18:25:16,841 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false 2014-06-09 18:25:17,164 DEBUG [c.c.u.d.ConnectionConcierge] (main:null) Registering a database connection for LockMaster1 2014-06-09 18:25:17,164 INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 345049793560 2014-06-09 18:25:17,175 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 345049793560 2014-06-09 18:25:17,206 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@63c8e4ae 2014-06-09 18:25:17,207 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. 2014-06-09 18:25:17,254 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) Checking to see if the database is at a version before it was the version table is created 2014-06-09 18:25:17,295 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.3.0 Code Version = 4.3.0 2014-06-09 18:25:17,296 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version and code version matches so no upgrade needed. The management server talking to the DB server at least enough to check the version; and mysql from the command line on the management server works fine as well. This line caught my attention. 2014-06-09 18:25:16,841 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false Is there something I need to set when using mysql replication specific to cloudstack? I do not see anything in the documentation on this other than setting up basic replication. if I comment out the above two lines in my.cnf and restart the management server it fires up just fine. I don’t get how enabling bin log would make a difference at all. Any help or explication for this strange issue would be appreciated. - Steve Searles
