cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <shadow...@gmail.com>
Subject Re: [URGENT - HELP NEEDED]
Date Mon, 16 Mar 2015 15:11:41 GMT
FWIW, if your 4.3.2 is the same as what's in the source tree for the
router code, the null pointer indicates that there's no default nic
for one of your guests "Techvee-FileServer". I'd guess that if you
delete/move just that host you may be able to start the router, or at
least get past this. You can also look into the db and see if you can
find its nics in the cloud.nics table and see if there is in fact one
marked default.

On Mon, Mar 16, 2015 at 8:05 AM, Marcus <shadowsor@gmail.com> wrote:
> Looks like the issue is that null pointer in CreateDhcpEntry for
> either "Techvee-FileServer" or the DHCP entry immediately after that.
> It would suggest some inconsistent/unexpected data when creating a
> DHCP entry for one of the guests serviced by this router. It's too bad
> that one bad entry is fatal for the whole router.
>
>
> On Mon, Mar 16, 2015 at 7:16 AM, Andrija Panic <andrija.panic@gmail.com> wrote:
>> Not really - we are painfully migrating stopped VMs, from VPS network
>> (Guest Shared netwotk) to VPCs...
>>
>> MGMT server sends the STOP command to agent, even though the VM was never
>> started, BUT the storage provisioning from template to volume is done...
>>
>> We are also looking into some external help as we speak...
>>
>> On 16 March 2015 at 14:52, Nux! <nux@li.nux.ro> wrote:
>>
>>> Hi,
>>>
>>> Have you managed to get to the bottom of this?
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> ----- Original Message -----
>>> > From: "Andrija Panic" <andrija.panic@gmail.com>
>>> > To: users@cloudstack.apache.org, dev@cloudstack.apache.org
>>> > Sent: Sunday, 15 March, 2015 16:19:07
>>> > Subject: [URGENT - HELP NEEDED]
>>>
>>> > Hi guys,
>>> >
>>> > we have updated the cloudstack from 4.3.0 to 4.3.2 (OS updated right
>>> before
>>> > that, from CentOS 6.5 to CentOS 6.6)
>>> >
>>> > And now I can not start SYSTEM VR - that is used for SHARED GUEST network
>>> > anymore.
>>> > And some VMs are down - and cant be started because they depend on this
>>> > VR...
>>> >
>>> > VPC VRs are created fine, so new VR for VPC are created fine, but this
>>> one
>>> > fro Guest network fails to start:
>>> >
>>> > Here you can see, after agent copies template from secondary storage, to
>>> > primary local storage, it created base image, and backing file - so
>>> storage
>>> > setup seems completed.
>>> >
>>> > Than all out of sudden we have errors:
>>>
>>
>>
>>
>> --
>>
>> Andrija Panić

Mime
View raw message