As a follow up to my previous post, I have seen cases where the system started
successfully, but failed to obtains its hostname from the DNS server. I had to
manually update the /etc/resolve.conf file and add the nameserver record, and
then restart the cloudstack-manager and cloudstack-agent.
A
I just completed a fresh installation of 4.2.1 on CentOS 6.5 with both the
management and the agent running on a single host. The plan is to keep things
simple as this setup will be used for development rather than hosting
production level services. After the initial setup everything looked grea
Hi Paul,
Thanks for the tip.
Kind Regards
Amin
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: Friday, 21 March 2014 6:29 PM
To: users@cloudstack.apache.org
Subject: RE: CloudStack 4.2.1 XenServer version support
Hi Amir,
Will 4.3.x support XenServer 6.2 in 'upgraded' man
Hi Alena,
thank you for your help.
The query returns no rows, i.e. nics.removed was not null, but I removed
the row though to see what happens: a new virtual router was created
which also couldn't be started due to the same NPE. I reverted the
change by restoring from the dump.
I have to mention
Before making changes in DB, try to decrease the expung interval and delay
interval to very low value, restart management service. This way the VM expung
process will be faster and eventually address the issue.
Sent from my iPhone
> On 22 Mar 2014, at 8:58 am, "Umair Azam" wrote:
>
> SELECT *
