Thanks again Paul. You were spot on. First of all the 'cloudstack-management' file in '/etc/default' had a datestamp of 2016. After overwriting the file with one I extracted from the cloudstack-management 4.11 rpm my ACS installation started up fine. Glad this is being fixed in 4.11.1. Cheers Osay
On Mon, 4 Jun 2018 at 09:07, Paul Angus <[email protected]> wrote: > Hi Osay, > > I've seen this before, I believe that your 'cloudstack-management' file in > '/etc/default' was upgraded an then overwritten by an old version during > 4.11 installation. > This has been fixed for 4.11.1, the fix for you right now would be to > overwrite that 'cloudstack-management' file with a new version from 4.11.x > > [email protected] > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -----Original Message----- > From: Osay Osman Yuuni <[email protected]> > Sent: 02 June 2018 13:38 > To: [email protected] > Subject: Issue with Upgrade from 4.7.1 to 4.11 > > Hi all, > I'm having an issue with my ACS upgrade. > After reading through the documentation carefully and performing the > pre-requisites, I upgraded my ACS installation from 4.7.0 to 4.7.1 and then > to 4.11. However after the upgrade ACS won't start. On Centos 7 and using > systemctl I get the following error: > > cloudstack-management.service - CloudStack Management Server > Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled; vendor preset: disabled) > Active: failed (Result: exit-code) since Wed 2018-05-30 16:48:22 SAST; > 15s ago > Process: 3199 ExecStart=/usr/bin/jsvc -home ${JAVA_HOME} -user > ${CLOUDSTACK_USER} -cp ${JARS}:${CLASSPATH} -errfile ${LOGDIR}/${NAME}.err > -cwd ${LOGDIR} -pidfile ${CLOUDSTACK_PID} ${JAVA_OPTS} ${BOOTSTRAP_CLASS} > (code=exited, status=1/FAILURE) > Process: 3190 ExecStartPre=/bin/bash -c /bin/systemctl set-environment > JARS=$(ls /usr/share/cloudstack-management/lib/*.jar | tr ' > ' ':' | sed s'/.$//') (code=exited, status=0/SUCCESS) > Process: 3183 ExecStartPre=/bin/bash -c /bin/systemctl set-environment > JAVA_HOME=$( readlink -f $( which java ) | sed s:bin/.*$:: ) (code=exited, > status=0/SUCCESS) > > May 30 16:48:22 cloudmgr1.afdb.org systemd[1]: Starting CloudStack > Management Server... > May 30 16:48:22 cloudmgr1.afdb.org jsvc[3199]: Invalid user name '' > specified > May 30 16:48:22 cloudmgr1.afdb.org systemd[1]: > cloudstack-management.service: control process exited, code=exited > status=1 May 30 16:48:22 cloudmgr1.afdb.org systemd[1]: Failed to start > CloudStack Management Server. > May 30 16:48:22 cloudmgr1.afdb.org systemd[1]: Unit > cloudstack-management.service entered failed state. > May 30 16:48:22 cloudmgr1.afdb.org systemd[1]: > cloudstack-management.service failed. > From what I can see this is linked to the Java service. > > I'm not sure why the invalid user name '' and what it's referring to. > There is no log in the cloudstack management log directory. This means it > dies immediately it is launched. > > Is this something that anyone has come across? Any help? > > Kind regards, > > -- > *Osay Osman YUUNI* | Techno-Geek > > > *Old Kent Drive | Midstream Estate *Office: +27 12 003 6900 | Ext: 8402 | > E-Mail: o <[email protected]>[email protected] > > Mobile: +27 78 090 5501 | Fax: +27866737198 Web: http://www. > <http://www.afdb.org/>yuuniqueenterprises.com > -- *Osay Osman YUUNI* | Techno-Geek *Old Kent Drive | Midstream Estate *Office: +27 12 003 6900 | Ext: 8402 | E-Mail: o <[email protected]>[email protected] Mobile: +27 78 090 5501 | Fax: +27866737198 Web: http://www. <http://www.afdb.org/>yuuniqueenterprises.com
