Hi, The management server produces no errors when starting as the last entry was the error I first posted. HAProxy shows that port 8080 is UP on both servers but 8250 is DOWN. 3306 is UP as well.
cloudstack-setup-databases shows OK all the way and ends with "CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties". #service cloudstack-management start Starting cloudstack-management: [ OK ] Thanks On Tue, Aug 23, 2016 at 2:54 PM, Glenn Wagner <[email protected]> wrote: > Hi, > > If you are still getting a 404 error that means your management server has > not started correctly , > Can you give us the management server logs to review from both management > servers? > > Can you also give us the output of the cloudstack-setup-databases script > you ran. > > > The GUI listens on port 8080 , are you mapping that in the haproxy ? > > Glenn > > > > > [email protected] > www.shapeblue.com > First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape Town > 7129South Africa > @shapeblue > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Joshua > Sent: Monday, 22 August 2016 4:33 PM > To: [email protected] > Subject: Re: Management Server can't start after upgrade to 4.9.0 > > I corrected this error but I'm still getting a 404 error for tomcat. If it > means anything, there's nothing listening on 8250 either. There are no more > errors in the logs when starting the management server though. > > I've also tried to rerun cloudstack-setup-databases but it's still broken. > > HTTP Status 404 - > ------------------------------ > > *type* Status report > > *message* > > *description* *The requested resource () is not available.* > ------------------------------ > Apache Tomcat/6.0.24 > > On Mon, Aug 22, 2016 at 9:51 PM, Jan Siml <[email protected]> wrote: > > > Hello, > > > > I have noticed the following error in db.properties after upgrade: > > > > db.cloud.secondsBeforeRetryMaster=3600db.cloud.driver=jdbc:mysql > > > > It should be: > > > > db.cloud.secondsBeforeRetryMaster=3600 > > db.cloud.driver=jdbc:mysql > > > > Maybe it's the same cause for you? Afterwards cloudstack-management > > service could be restarted successfully. > > > > Kind regards > > > > Jan > > > > > > > > On 08/22/2016 03:46 PM, Marty Godsey wrote: > > > >> I noticed this step missing as well. I use Ubuntu for my management > >> servers but I know I had to rerun the cloudstack-setup-databases > >> script again without the deploy option to correct. > >> > >> Regards, > >> Marty Godsey > >> > >> -----Original Message----- > >> From: Joshua [mailto:[email protected]] > >> Sent: Monday, August 22, 2016 6:10 AM > >> To: [email protected] > >> Subject: Re: Management Server can't start after upgrade to 4.9.0 > >> > >> The settings look correct in that file. Where do I find this? "DB > >> driver type null is not supported!" > >> > >> On Mon, Aug 22, 2016 at 6:02 PM, Glenn Wagner > >> <[email protected] > >> > > >> wrote: > >> > >> Hi, > >>> > >>> You can have a look at the db.properties file on both your > >>> Management servers > >>> > >>> /etc/cloudstack/management/db.properties > >>> > >>> Thanks > >>> Glenn > >>> > >>> > >>> [email protected] > >>> www.shapeblue.com > >>> First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape > >>> Town 7129South Africa @shapeblue > >>> > >>> > >>> > >>> > >>> -----Original Message----- > >>> From: [email protected] [mailto:[email protected]] On Behalf Of > >>> Joshua > >>> Sent: Monday, 22 August 2016 11:48 AM > >>> To: [email protected] > >>> Subject: Re: Management Server can't start after upgrade to 4.9.0 > >>> > >>> Yes. Everything was followed. > >>> > >>> It seems like it's connecting to the wrong MySQL server (trying for > >>> localhost but it's supposed to connect to a HAProxy balanced "remote" > >>> IP). > >>> > >>> On Mon, Aug 22, 2016 at 5:44 PM, Glenn Wagner > >>> <[email protected]> > >>> wrote: > >>> > >>> Ok did you install the new mysql connector for version 4.9 ? > >>>> > >>>> http://docs.cloudstack.apache.org/projects/cloudstack- > >>>> release-notes/en/4.9.0/upgrade/upgrade-4.8.html# > >>>> install-new-mysql-connector > >>>> > >>>> > >>>> Glenn > >>>> > >>>> > >>>> > >>>> [email protected] > >>>> www.shapeblue.com > >>>> First Floor, Victoria Centre, 7 Victoria Street, Somerset West, > >>>> Cape Town 7129South Africa @shapeblue > >>>> > >>>> > >>>> > >>>> > >>>> -----Original Message----- > >>>> From: [email protected] [mailto:[email protected]] On Behalf Of > >>>> Joshua > >>>> Sent: Monday, 22 August 2016 11:40 AM > >>>> To: [email protected] > >>>> Subject: Re: Management Server can't start after upgrade to 4.9.0 > >>>> > >>>> Hello Glenn, > >>>> > >>>> # cat /etc/*-release > >>>> CentOS release 6.7 (Final) > >>>> LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0- > >>>> n > >>>> oa > >>>> rch > >>>> CentOS release 6.7 (Final) > >>>> CentOS release 6.7 (Final) > >>>> > >>>> Thanks > >>>> Joshua > >>>> > >>>> On Mon, Aug 22, 2016 at 5:07 PM, Glenn Wagner > >>>> <[email protected]> > >>>> wrote: > >>>> > >>>> Morning Joshua, > >>>>> > >>>>> What OS are you using on your Management server nodes? > >>>>> > >>>>> Thanks > >>>>> Glenn > >>>>> > >>>>> > >>>>> [email protected] > >>>>> www.shapeblue.com > >>>>> First Floor, Victoria Centre, 7 Victoria Street, Somerset West, > >>>>> Cape Town 7129South Africa @shapeblue > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> -----Original Message----- > >>>>> From: [email protected] [mailto:[email protected]] On Behalf > >>>>> Of Joshua > >>>>> Sent: Monday, 22 August 2016 10:49 AM > >>>>> To: [email protected] > >>>>> Subject: Management Server can't start after upgrade to 4.9.0 > >>>>> > >>>>> Hi all, > >>>>> > >>>>> I followed the instructions under > >>>>> http://docs.cloudstack.apache.org/projects/cloudstack- > >>>>> release-notes/en/4.9.0/upgrade/upgrade-4.8.html > >>>>> to upgrade form 4.8.0 to 4.9.0 and it seems to have overwritten > >>>>> the default DB connection config. > >>>>> > >>>>> The setup is running two management nodes connecting to a HAProxy > >>>>> balanced Active-Passive Galera cluster. It seems that after the > >>>>> upgrade both management nodes are trying to connect to the local > >>>>> MySQL server > >>>>> (127.0.0.1) which is wrong. Where should I edit the config? > >>>>> > >>>>> Thanks in advance! > >>>>> > >>>>> Paste of log: > >>>>> > >>>>> 2016-08-22 16:23:46,669 ERROR [c.c.u.d.DriverLoader] (main:null) > >>>>> (logid:) DB driver type null is not supported! > >>>>> 2016-08-22 16:23:46,693 WARN [c.c.u.d.T.Transaction] (main:null) > >>>>> (logid:) Unable to load db configuration, using defaults with 5 > >>>>> connections. Falling back on assumed datasource on localhost:3306 > >>>>> using username:password=cloud:cloud. Please check your > >>>>> configuration > >>>>> com.cloud.utils.exception.CloudRuntimeException: DB driver type > >>>>> null is not supported! > >>>>> 2016-08-22 16:23:46,939 ERROR [c.c.u.d.Merovingian2] (main:null) > >>>>> (logid:) Unable to get a new db connection > >>>>> java.sql.SQLException: Access denied for user 'cloud'@'127.0.0.1' > >>>>> (using > >>>>> password: YES) > >>>>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:935) > >>>>> at > >>>>> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithEx > >>>>> c > >>>>> eption(TransactionLegacy.java:202) > >>>>> 2016-08-22 16:23:46,952 WARN > >>>>> [o.a.c.s.m.c.ResourceApplicationContext] > >>>>> (main:null) (logid:) Exception encountered during context > >>>>> initialization - cancelling refresh attempt: > >>>>> org.springframework.beans.factory.BeanCreationException: Error > >>>>> creating bean with name 'lockMasterListener' defined in URL > >>>>> [jar:file:/usr/share/cloudstack-management/webapps/ > >>>>> client/WEB-INF/lib/cloud-server-4.9.0.jar!/META-INF/ > >>>>> cloudstack/system/spring-server-system-context.xml]: > >>>>> Instantiation of bean failed; nested exception is > >>>>> org.springframework.beans.BeanInstantiationException: Could not > >>>>> instantiate bean class [com.cloud.server.LockMasterListener]: > >>>>> Constructor threw exception; nested exception is > >>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to > >>>>> initialize a connection to the database for locking purposes > >>>>> 2016-08-22 16:28:16,582 ERROR [c.c.u.d.DriverLoader] (main:null) > >>>>> (logid:) DB driver type null is not supported! > >>>>> 2016-08-22 16:28:16,602 WARN [c.c.u.d.T.Transaction] (main:null) > >>>>> (logid:) Unable to load db configuration, using defaults with 5 > >>>>> connections. Falling back on assumed datasource on localhost:3306 > >>>>> using username:password=cloud:cloud. Please check your > >>>>> configuration > >>>>> com.cloud.utils.exception.CloudRuntimeException: DB driver type > >>>>> null is not supported! > >>>>> 2016-08-22 16:28:16,811 ERROR [c.c.u.d.Merovingian2] (main:null) > >>>>> (logid:) Unable to get a new db connection > >>>>> java.sql.SQLException: Access denied for user 'cloud'@'127.0.0.1' > >>>>> (using > >>>>> password: YES) > >>>>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) > >>>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:935) > >>>>> at > >>>>> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithEx > >>>>> c > >>>>> eption(TransactionLegacy.java:202) > >>>>> 2016-08-22 16:28:16,822 WARN > >>>>> [o.a.c.s.m.c.ResourceApplicationContext] > >>>>> (main:null) (logid:) Exception encountered during context > >>>>> initialization - cancelling refresh attempt: > >>>>> org.springframework.beans.factory.BeanCreationException: Error > >>>>> creating bean with name 'lockMasterListener' defined in URL > >>>>> [jar:file:/usr/share/cloudstack-management/webapps/ > >>>>> client/WEB-INF/lib/cloud-server-4.9.0.jar!/META-INF/ > >>>>> cloudstack/system/spring-server-system-context.xml]: > >>>>> Instantiation of bean failed; nested exception is > >>>>> org.springframework.beans.BeanInstantiationException: Could not > >>>>> instantiate bean class [com.cloud.server.LockMasterListener]: > >>>>> Constructor threw exception; nested exception is > >>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to > >>>>> initialize a connection to the database for locking purposes > >>>>> > >>>>> > >>>> > >>> >
