cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Indra Pramana <in...@sg.or.id>
Subject Re: Upgrading from 4.1.1 to 4.2.0, cloudstack-sysvmadm fails to execute
Date Mon, 23 Sep 2013 15:10:13 GMT
Dear Simon and all,

Managed to use "--force-reinstall true" option to force reinstall the
cloudstack-management.

However, same issue persists after reinstallation. Error message on
management-server.log file:

====
2013-09-23 23:06:17,884 ERROR [web.context.ContextLoader] (main:null)
Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'apiDBUtils': Injection of autowired dependencies failed;
nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: private com.cloud.region.ha.GlobalLoadBalancingRulesService
com.cloud.api.ApiDBUtils.gslbService; nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No
matching bean of type [com.cloud.region.ha.GlobalLoadBalancingRulesService]
found for dependency: expected at least 1 bean which qualifies as autowire
candidate for this dependency. Dependency annotations:
{@javax.inject.Inject()}
====

Anyone can advise what could be the problem?

- Anyone can provide me an APT repo for me to try installing CloudStack
4.2, to eliminate the possibility of issue on my build?
- Could it be database issue? Need to revert back to 4.1.1 format before
re-trying?

Any advice is greatly appreciated.

Thank you.




On Mon, Sep 23, 2013 at 10:59 PM, Indra Pramana <indra@sg.or.id> wrote:

> Hi Simon and all,
>
> I tried to rebuild/recompile from the beginning.
>
> How to force my Cloudstack management server to perform the update? It
> says it's already the newest version:
>
> root@cs-mgmt-01:/var/log/cloudstack/management# apt-get install
> cloudstack-management
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> cloudstack-management is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
>
> Looking forward to your reply, thank you,
>
> Cheers.
>
>
>
> On Mon, Sep 23, 2013 at 10:34 PM, Indra Pramana <indra@sg.or.id> wrote:
>
>> Hi Simon,
>>
>> Yes, I downloaded the source from the URL given by Animesh when he
>> started the last vote.
>>
>> [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>>
>> which is this file:
>>
>>
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/apache-cloudstack-4.2.0-src.tar.bz2
>>
>> I then compiled it as follows. No error during compilation / build.
>>
>> mvn clean install -P developer,systemvm
>> dpkg-buildpackage -uc -us
>> (to create the *.deb packages)
>>
>> Setting up APT repo:
>>
>> dpkg-scanpackages . /dev/null | tee Packages | gzip -9 > Packages.gz
>>
>> I then follow the instruction on the PDF file provided by Radhika and
>> some addition of notes by Abhinav to perform the upgrade.
>>
>> I am using Ubuntu 12.04.3 LTS for the CloudStack management server as
>> well as the KVM hosts. The MySQL database is hosted on a separated server.
>>
>> Do you think my built got some issues? Need to recompile and rebuild?
>>
>> Looking forward to your reply, thank you.
>>
>> Cheers.
>>
>>
>> On Mon, Sep 23, 2013 at 10:15 PM, Simon Weller <sweller@ena.com> wrote:
>>
>>> Indra,
>>>
>>>
>>> Can you supply some more information about your installation? Is this
>>> built from source and installed, or packaged? What distro are you running?
>>> Any other errors during installation or build?
>>>
>>> ----- Original Message -----
>>>
>>> From: "Indra Pramana" <indra@sg.or.id>
>>> To: dev@cloudstack.apache.org
>>> Cc: users@cloudstack.apache.org
>>> Sent: Monday, September 23, 2013 8:46:55 AM
>>> Subject: Re: Upgrading from 4.1.1 to 4.2.0, cloudstack-sysvmadm fails to
>>> execute
>>>
>>> Hi Simon,
>>>
>>> Thank you for your e-mail.
>>>
>>> I think I haven't set this. However, I am not able to access the GUI at
>>> all
>>> now. Seems that my upgrade itself failed?
>>>
>>> cloudstack-management service is running but I cannot access the GUI.
>>> Error
>>> messages on the management-server log file:
>>>
>>> http://pastebin.com/0FP9itAf
>>>
>>> Can advise?
>>>
>>> Looking forward to your reply, thank you.
>>>
>>> Cheers.
>>>
>>>
>>>
>>>
>>> On Mon, Sep 23, 2013 at 9:36 PM, Simon Weller <sweller@ena.com> wrote:
>>>
>>> > Indra,
>>> >
>>> >
>>> > Have you enabled the "integration.api.port" under Global Settings menu
>>> in
>>> > CS management GUI? If not, set it to 8096, restart management and see
>>> if
>>> > the problem goes away.
>>> >
>>> >
>>> > - Si
>>> >
>>> > ----- Original Message -----
>>> >
>>> > From: "Indra Pramana" <indra@sg.or.id>
>>> > To: users@cloudstack.apache.org, dev@cloudstack.apache.org
>>> > Cc: "Radhika Puthiyetath" <radhika.puthiyetath@citrix.com>
>>> > Sent: Monday, September 23, 2013 8:22:28 AM
>>> > Subject: Upgrading from 4.1.1 to 4.2.0, cloudstack-sysvmadm fails to
>>> > execute
>>> >
>>> > Dear all,
>>> >
>>> > I am currently in the midst of upgrading my CloudStack 4.1.1 to 4.2.0.
>>> > Everything went smooth after I followed the instruction from the PDF
>>> file
>>> > provided by Radhika and some addition of notes by Abhinav, except on
>>> the
>>> > last step:
>>> >
>>> > When I tried to run the cloudstack-sysvmadm script:
>>> >
>>> > nohup cloudstack-sysvmadm -d [DB-SERVER-IP] -u cloud -p[DB-PASSWORD]
>>> -a >
>>> > sysvm.log 2>&1 &
>>> >
>>> > Content of sysvm.log:
>>> >
>>> > =====
>>> > nohup: ignoring input
>>> > /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No
>>> such
>>> > file or directory
>>> >
>>> > Stopping and starting 1 secondary storage vm(s)...
>>> > curl: (7) couldn't connect to host
>>> > ERROR: Failed to stop secondary storage vm with id 1902
>>> >
>>> > Done stopping and starting secondary storage vm(s)
>>> >
>>> > Stopping and starting 1 console proxy vm(s)...
>>> > curl: (7) couldn't connect to host
>>> > ERROR: Failed to stop console proxy vm with id 1903
>>> >
>>> > Done stopping and starting console proxy vm(s) .
>>> >
>>> > Stopping and starting 2 running routing vm(s)...
>>> > curl: (7) couldn't connect to host
>>> > 2
>>> > curl: (7) couldn't connect to host
>>> > 2
>>> > Done restarting router(s).
>>> > =====
>>> >
>>> > Content of cloud.log:
>>> >
>>> > ======
>>> > Stopping and starting 1 secondary storage vm(s)...
>>> > INFO: Stopping secondary storage vm with id 1902
>>> > ERROR: Failed to stop secondary storage vm with id 1902
>>> > Done stopping and starting secondary storage vm(s).
>>> > Stopping and starting 1 console proxy vm(s)...
>>> > INFO: Stopping console proxy with id 1903
>>> > ERROR: Failed to stop console proxy vm with id 1903
>>> > Done stopping and starting console proxy vm(s) .
>>> > Stopping and starting 2 running routing vm(s)...
>>> > INFO: Restarting router with id 1930
>>> > INFO: Restarting router with id 1931
>>> > ERROR: Failed to restart domainRouter with id 1930
>>> > ERROR: Failed to restart domainRouter with id 1931
>>> > Done restarting router(s).
>>> > =====
>>> >
>>> > It seems that the script fails to restart the system VMs (1 SSVM, 1
>>> CPVM
>>> > and 2 VRs). Anything I have done wrong or have missed out?
>>> >
>>> > After the upgrade, I am still not able to access the CloudStack GUI
>>> with
>>> > this error message:
>>> >
>>> > =====
>>> > HTTP Status 404 -
>>> >
>>> > type Status report
>>> >
>>> > message
>>> >
>>> > description The requested resource () is not available.
>>> > Apache Tomcat/6.0.35
>>> > =====
>>> >
>>> > Anyone can help and assist? :)
>>> >
>>> > Looking forward to your reply, thank you.
>>> >
>>> > Cheers.
>>> >
>>> >
>>>
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message