Re: IPMI out of management

[victor]

Hello Guys,

I am also able to successfully configure ipmi fencing with cloudstack. 
Also can you guys let me know whether all the proposed features are 
fully covered with the  ipmi out of management.


Regards
Victor

On 08/03/2017 03:35 AM, Rohit Yadav wrote:

Thanks Gabriel, Rodrigo -- good to know this is in use.


Victor - yes it works, there is a ipmisim [1] tool you can test the 
implementation against, as well as real h/w.


[1] https://pypi.python.org/pypi/ipmisim


- Rohit


From: Rodrigo Baldasso 
Sent: Tuesday, August 1, 2017 2:38:28 PM
To: users@cloudstack.apache.org
Subject: Re: IPMI out of management

I'm using here and works fine with my Supermicro servers.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 01/08/2017 09:01:20, victor  wrote:
Hello Guys,

Have anybody able to configure and test ipmi "out of management" with
cloudstack successfully.

Regards

Victor



rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
   
  

Re: Windows Server 2016 - unable to boot ISO for installation

[Cloud List]

Hi Lucian,

Good day to you, and thank you for your reply.

>From what I understand, once the hypervisor is managed by CloudStack (using
cloudstack-agent), we shouldn't use virt-manager to create VMs and all VMs
will have to be created through CloudStack, correct?

I read further and based on below documentation:

https://social.technet.microsoft.com/Forums/en-US/695c8997-52cf-4c30-a3f7-f26a40dc703a/failed-install-of-build-10041-in-the-kvm-virtual-machine-system-thread-exception-not-handled?forum=WinPreview2014Setup

I am using Sandy Bridge CPU and based on the above, it seems that we can
resolve the problem by setting the CPU type as follows: 'core2duo'.

The question is how to change it through CloudStack, can I confirm that we
can do so by following the "Configure CPU model for KVM guest (Optional)"
instruction at below URL?

http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.8/hypervisor/kvm.html

Based on the above instruction, I would need to add some lines on
agent.properties file as follows:

===
guest.cpu.mode=custom
guest.cpu.model=core2duo
===

and then restart CloudStack agent for the changes to take affect. Is it
correct? Please correct me if I'm wrong.

Looking forward to your reply, thank you.

Cheers.

-ip-




On Tue, Aug 1, 2017 at 11:26 PM, Nux!  wrote:

> Hello,
>
> I am not in a position to test, but it should be fairly easy to; just
> power up virt-manager on the said Ubuntu hypervisor and try to create a
> Windows 2016 VM with  
>
> Let us know how it went :)
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Cloud List" 
> > To: "users" 
> > Cc: "dev" 
> > Sent: Tuesday, 1 August, 2017 04:11:06
> > Subject: Re: Windows Server 2016 - unable to boot ISO for installation
>
> > Hi Lucian,
> >
> > Nice to hear from you again. Below is the KVM version (QEMU version, to
> be
> > exact) I am using:
> >
> > # kvm --version
> > QEMU emulator version 2.4.1, Copyright (c) 2003-2008 Fabrice Bellard
> >
> > I am using Ubuntu instead of CentOS for the KVM host, may I know if this
> > affects KVM running on Ubuntu as well? I am using Intel Xeon E5 series
> for
> > the hypervisor hosts, not too sure if it's supported and part of the
> Xeon E
> > series on the list?
> >
> > Looking forward to your reply, thank you.
> >
> > Cheers.
> >
> > -ip-
> >
> >
> > On Tue, Aug 1, 2017 at 12:45 AM, Nux!  wrote:
> >
> >> It could be this
> >> https://access.redhat.com/documentation/en-US/Red_Hat_
> >> Enterprise_Linux/6/html/6.8_Release_Notes/known_issues_
> virtualization.html
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> - Original Message -
> >> > From: "Nux!" 
> >> > To: "users" 
> >> > Cc: "dev" 
> >> > Sent: Monday, 31 July, 2017 16:54:51
> >> > Subject: Re: Windows Server 2016 - unable to boot ISO for installation
> >>
> >> > What version of KVM?
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
> >> >
> >> > - Original Message -
> >> >> From: "Cloud List" 
> >> >> To: "users" 
> >> >> Cc: "dev" 
> >> >> Sent: Monday, 31 July, 2017 03:31:45
> >> >> Subject: Windows Server 2016 - unable to boot ISO for installation
> >> >
> >> >> Dear all,
> >> >>
> >> >> I am using CloudStack 4.8.1.1 with KVM hypervisor. I have downloaded
> >> >> Windows Server 2016 ISO but when I tried to boot up the ISO for
> >> >> installation and template creation, it immediately goes into Blue
> >> Screen /
> >> >> BSOD with below error messages:
> >> >>
> >> >> ===
> >> >> Your PC ran into a problem and needs a restart. We'll restart for
> you.
> >> >>
> >> >> For more information about this issue and possible fixes, visit
> >> >> http://windows.com/stopcode
> >> >>
> >> >> If you call a support person, give them this info:
> >> >> Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED
> >> >> ===
> >> >>
> >> >> and then it will go into restart, hit with the same error and keep on
> >> >> restarting on an infinite loop.
> >> >>
> >> >> I browse around and it seems the error is related to outdated or
> wrong
> >> >> driver (most probably display driver) or due to resources issues.
> Have
> >> >> tried to increase the resources to 8 GB RAM, 4 CPU cores and 60 GB of
> >> disk
> >> >> space, and the problem still persists. Have tried different OS types:
> >> >> "Other PV (64-bit)", "Other (64-bit)" and "Windows Server 2012 R2
> >> >> (64-bit"), and problem still persists.
> >> >>
> >> >> I understand that Windows Server 2016 should work and some people
> have
> >> >> managed to get Windows Server 2016 VM and template up and running
> (see
> >> >> 

Re: IPMI out of management

[Rohit Yadav]

Thanks Gabriel, Rodrigo -- good to know this is in use.


Victor - yes it works, there is a ipmisim [1] tool you can test the 
implementation against, as well as real h/w.


[1] https://pypi.python.org/pypi/ipmisim


- Rohit


From: Rodrigo Baldasso 
Sent: Tuesday, August 1, 2017 2:38:28 PM
To: users@cloudstack.apache.org
Subject: Re: IPMI out of management

I'm using here and works fine with my Supermicro servers.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 01/08/2017 09:01:20, victor  wrote:
Hello Guys,

Have anybody able to configure and test ipmi "out of management" with
cloudstack successfully.

Regards

Victor



rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Unable to start SSVM

[Rodrigo Baldasso]

Yes, it is. I'll try to find out the main reason for that happen and if find a 
way to fix the code, share here.

Thanks.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 11:16:47, Rafael Weingärtner  wrote:
Ah, that is what I wanted to check now ...
I was going to ask you to execute the following SQL:
select v.* from pod_vlan_map vlanMap
join vlan v on v.id = vlanMap.vlan_db_id
where v.removed is null and vlanMap.pod_id = 1

So, now everything is ok for you?

On Wed, Aug 2, 2017 at 11:13 AM, Rodrigo Baldasso
wrote:

> Confirmed: when the pod has more than one vlan on the vlan table, it
> throws this exception error. I've deleted all vlans leaving only the one
> with ID 14 (that i created for this test) and was able to sucessfully
> delete the pod.
>
> Maybe the code doesn't handle more than one match of pod vlans, and
> then show the nullpointer error.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:09:53, Rodrigo Baldasso wrote:
> ID of problematic pod: 1
>
> 4 is the ID of the working pod. However all settings between them are
> identical. The problem seems to be when one pod has *more* than one vlan
> (deleted or not).
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:08:32, Rafael Weingärtner
> wrote:
> What is the ID of the pod you want to remove? 1 or 4?
>
> On Wed, Aug 2, 2017 at 11:03 AM, Rodrigo Baldasso
> wrote:
>
> > Yep: http://prntscr.com/g3gab3
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 11:02:40, Rafael Weingärtner
> > wrote:
> > I mean, I said 14 because this was the one select by you. Can you check
> the
> > VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod
> that
> > you are having problems to remove.
> >
> > On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Interesting; now, can you try to find a vlan with ID=14 in "vlan"
> table?
> > >
> > > On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > > > wrote:
> > >
> > >> Sure: http://prntscr.com/g3g7iu
> > >>
> > >> The last vlan map is the one that I created for testing on the
> > >> problematic pod.
> > >>
> > >> - - - - - - - - - - - - - - - - - - -
> > >>
> > >> Rodrigo Baldasso - LHOST
> > >>
> > >> (51) 9 8419-9861
> > >> - - - - - - - - - - - - - - - - - - -
> > >> On 02/08/2017 10:56:01, Rafael Weingärtner
> > >> wrote:
> > >> Can you also list the table "pod_vlan_map" for all of the "maps" of
> > vlans
> > >> for the given POD?
> > >>
> > >> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> > >> wrote:
> > >>
> > >> > I've created a new vlan/ip pool just for this test (had already
> > removed
> > >> > all ip pool before), the problem persisted.
> > >> >
> > >> > here is how the new vlan looks like in my db:
> > >> >
> > >> > http://prntscr.com/g3fxt1
> > >> >
> > >> > It's pretty equals to the one of the working pod.
> > >> >
> > >> >
> > >> >
> > >> > - - - - - - - - - - - - - - - - - - -
> > >> >
> > >> > Rodrigo Baldasso - LHOST
> > >> >
> > >> > (51) 9 8419-9861
> > >> > - - - - - - - - - - - - - - - - - - -
> > >> > On 02/08/2017 10:21:47, Rafael Weingärtner
> > >> > wrote:
> > >> > Ok,
> > >> >
> > >> > Following the code where the null pointer happens at line 163:
> > >> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
> > >> 4924ac1fb250
> > >> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> > >> >
> > >> > can you list all VLANs in "vlan" table that have the PODid equals
> one
> > of
> > >> > the Pods you want to remove?Also, please filter the already removed
> > >> VLANs.
> > >> >
> > >> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> > >> > wrote:
> > >> >
> > >> > > This pod got somewhat corrupted when I change it's IP pool
> > allocation
> > >> > > cidr. After changing, it didn't started the SSVM's with the
> > >> nullpointer
> > >> > > error that i've send before and now the pod can't be deleted, also
> > >> > throwing
> > >> > > the nullpointer error.
> > >> > >
> > >> > > Thanks.
> > >> > >
> > >> > > - - - - - - - - - - - - - - - - - - -
> > >> > >
> > >> > > Rodrigo Baldasso - LHOST
> > >> > >
> > >> > > (51) 9 8419-9861
> > >> > > - - - - - - - - - - - - - - - - - - -
> > >> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> > >> > > wrote:
> > >> > > Well, looking at the data you posted, the problem should not
> happen.
> > >> > Let´s
> > >> > > take step back. Can you describe briefly what you are trying to
> do,
> > >> and
> > >> > > what problem you are having now?
> > >> > >
> > >> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> > >> > > wrote:
> > >> > >
> > 

Re: Unable to start SSVM

[Rafael Weingärtner]

Ah, that is what I wanted to check now ...
I was going to ask you to execute the following SQL:
select v.* from pod_vlan_map vlanMap
join vlan v on v.id = vlanMap.vlan_db_id
where v.removed is null and vlanMap.pod_id = 1

So, now everything is ok for you?

On Wed, Aug 2, 2017 at 11:13 AM, Rodrigo Baldasso 
wrote:

> Confirmed: when the pod has more than one vlan on the vlan table, it
> throws this exception error. I've deleted all vlans leaving only the one
> with ID 14 (that i created for this test) and was able to sucessfully
> delete the pod.
>
> Maybe the code doesn't handle more than one match of pod <> vlans, and
> then show the nullpointer error.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:09:53, Rodrigo Baldasso  wrote:
> ID of problematic pod: 1
>
> 4 is the ID of the working pod. However all settings between them are
> identical. The problem seems to be when one pod has *more* than one vlan
> (deleted or not).
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:08:32, Rafael Weingärtner 
> wrote:
> What is the ID of the pod you want to remove? 1 or 4?
>
> On Wed, Aug 2, 2017 at 11:03 AM, Rodrigo Baldasso
> wrote:
>
> > Yep: http://prntscr.com/g3gab3
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 11:02:40, Rafael Weingärtner
> > wrote:
> > I mean, I said 14 because this was the one select by you. Can you check
> the
> > VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod
> that
> > you are having problems to remove.
> >
> > On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Interesting; now, can you try to find a vlan with ID=14 in "vlan"
> table?
> > >
> > > On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > > > wrote:
> > >
> > >> Sure: http://prntscr.com/g3g7iu
> > >>
> > >> The last vlan map is the one that I created for testing on the
> > >> problematic pod.
> > >>
> > >> - - - - - - - - - - - - - - - - - - -
> > >>
> > >> Rodrigo Baldasso - LHOST
> > >>
> > >> (51) 9 8419-9861
> > >> - - - - - - - - - - - - - - - - - - -
> > >> On 02/08/2017 10:56:01, Rafael Weingärtner
> > >> wrote:
> > >> Can you also list the table "pod_vlan_map" for all of the "maps" of
> > vlans
> > >> for the given POD?
> > >>
> > >> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> > >> wrote:
> > >>
> > >> > I've created a new vlan/ip pool just for this test (had already
> > removed
> > >> > all ip pool before), the problem persisted.
> > >> >
> > >> > here is how the new vlan looks like in my db:
> > >> >
> > >> > http://prntscr.com/g3fxt1
> > >> >
> > >> > It's pretty equals to the one of the working pod.
> > >> >
> > >> >
> > >> >
> > >> > - - - - - - - - - - - - - - - - - - -
> > >> >
> > >> > Rodrigo Baldasso - LHOST
> > >> >
> > >> > (51) 9 8419-9861
> > >> > - - - - - - - - - - - - - - - - - - -
> > >> > On 02/08/2017 10:21:47, Rafael Weingärtner
> > >> > wrote:
> > >> > Ok,
> > >> >
> > >> > Following the code where the null pointer happens at line 163:
> > >> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
> > >> 4924ac1fb250
> > >> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> > >> >
> > >> > can you list all VLANs in "vlan" table that have the PODid equals
> one
> > of
> > >> > the Pods you want to remove?Also, please filter the already removed
> > >> VLANs.
> > >> >
> > >> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> > >> > wrote:
> > >> >
> > >> > > This pod got somewhat corrupted when I change it's IP pool
> > allocation
> > >> > > cidr. After changing, it didn't started the SSVM's with the
> > >> nullpointer
> > >> > > error that i've send before and now the pod can't be deleted, also
> > >> > throwing
> > >> > > the nullpointer error.
> > >> > >
> > >> > > Thanks.
> > >> > >
> > >> > > - - - - - - - - - - - - - - - - - - -
> > >> > >
> > >> > > Rodrigo Baldasso - LHOST
> > >> > >
> > >> > > (51) 9 8419-9861
> > >> > > - - - - - - - - - - - - - - - - - - -
> > >> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> > >> > > wrote:
> > >> > > Well, looking at the data you posted, the problem should not
> happen.
> > >> > Let´s
> > >> > > take step back. Can you describe briefly what you are trying to
> do,
> > >> and
> > >> > > what problem you are having now?
> > >> > >
> > >> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> > >> > > wrote:
> > >> > >
> > >> > > > Hi Rafael,
> > >> > > >
> > >> > > > I checked this table yesterday and couldn't find nothing
> wrong.. i
> > >> > made a
> > >> > > > line around the vLan of the new pod (that is working). The other
> > >> vLans
> > >> 

Re: Unable to start SSVM

[Rodrigo Baldasso]

Confirmed: when the pod has more than one vlan on the vlan table, it throws 
this exception error. I've deleted all vlans leaving only the one with ID 14 
(that i created for this test) and was able to sucessfully delete the pod.

Maybe the code doesn't handle more than one match of pod <> vlans, and then 
show the nullpointer error.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 11:09:53, Rodrigo Baldasso  wrote:
ID of problematic pod: 1

4 is the ID of the working pod. However all settings between them are 
identical. The problem seems to be when one pod has *more* than one vlan 
(deleted or not).

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 11:08:32, Rafael Weingärtner  wrote:
What is the ID of the pod you want to remove? 1 or 4?

On Wed, Aug 2, 2017 at 11:03 AM, Rodrigo Baldasso
wrote:

> Yep: http://prntscr.com/g3gab3
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:02:40, Rafael Weingärtner
> wrote:
> I mean, I said 14 because this was the one select by you. Can you check the
> VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod that
> you are having problems to remove.
>
> On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
> rafaelweingart...@gmail.com> wrote:
>
> > Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?
> >
> > On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > > wrote:
> >
> >> Sure: http://prntscr.com/g3g7iu
> >>
> >> The last vlan map is the one that I created for testing on the
> >> problematic pod.
> >>
> >> - - - - - - - - - - - - - - - - - - -
> >>
> >> Rodrigo Baldasso - LHOST
> >>
> >> (51) 9 8419-9861
> >> - - - - - - - - - - - - - - - - - - -
> >> On 02/08/2017 10:56:01, Rafael Weingärtner
> >> wrote:
> >> Can you also list the table "pod_vlan_map" for all of the "maps" of
> vlans
> >> for the given POD?
> >>
> >> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> >> wrote:
> >>
> >> > I've created a new vlan/ip pool just for this test (had already
> removed
> >> > all ip pool before), the problem persisted.
> >> >
> >> > here is how the new vlan looks like in my db:
> >> >
> >> > http://prntscr.com/g3fxt1
> >> >
> >> > It's pretty equals to the one of the working pod.
> >> >
> >> >
> >> >
> >> > - - - - - - - - - - - - - - - - - - -
> >> >
> >> > Rodrigo Baldasso - LHOST
> >> >
> >> > (51) 9 8419-9861
> >> > - - - - - - - - - - - - - - - - - - -
> >> > On 02/08/2017 10:21:47, Rafael Weingärtner
> >> > wrote:
> >> > Ok,
> >> >
> >> > Following the code where the null pointer happens at line 163:
> >> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
> >> 4924ac1fb250
> >> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> >> >
> >> > can you list all VLANs in "vlan" table that have the PODid equals one
> of
> >> > the Pods you want to remove?Also, please filter the already removed
> >> VLANs.
> >> >
> >> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> >> > wrote:
> >> >
> >> > > This pod got somewhat corrupted when I change it's IP pool
> allocation
> >> > > cidr. After changing, it didn't started the SSVM's with the
> >> nullpointer
> >> > > error that i've send before and now the pod can't be deleted, also
> >> > throwing
> >> > > the nullpointer error.
> >> > >
> >> > > Thanks.
> >> > >
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > >
> >> > > Rodrigo Baldasso - LHOST
> >> > >
> >> > > (51) 9 8419-9861
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> >> > > wrote:
> >> > > Well, looking at the data you posted, the problem should not happen.
> >> > Let´s
> >> > > take step back. Can you describe briefly what you are trying to do,
> >> and
> >> > > what problem you are having now?
> >> > >
> >> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> >> > > wrote:
> >> > >
> >> > > > Hi Rafael,
> >> > > >
> >> > > > I checked this table yesterday and couldn't find nothing wrong.. i
> >> > made a
> >> > > > line around the vLan of the new pod (that is working). The other
> >> vLans
> >> > > are
> >> > > > from the pod that i'm unable to delete and didn't booted the
> SSVM's.
> >> > They
> >> > > > have the column 'removed' with the date that i deleted them.
> >> > > >
> >> > > > http://prntscr.com/g3eqpr
> >> > > >
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > >
> >> > > > Rodrigo Baldasso - LHOST
> >> > > >
> >> > > > (51) 9 8419-9861
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
> >> > > > wrote:
> >> > > > Rodrigo,
> >> > > >
> >> > > > There is an inconsistency in your database.
> >> > > >
> >> > > > To get this null pointer, the column 

Re: Unable to start SSVM

[Rodrigo Baldasso]

ID of problematic pod: 1

4 is the ID of the working pod. However all settings between them are 
identical. The problem seems to be when one pod has *more* than one vlan 
(deleted or not).

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 11:08:32, Rafael Weingärtner  wrote:
What is the ID of the pod you want to remove? 1 or 4?

On Wed, Aug 2, 2017 at 11:03 AM, Rodrigo Baldasso
wrote:

> Yep: http://prntscr.com/g3gab3
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:02:40, Rafael Weingärtner
> wrote:
> I mean, I said 14 because this was the one select by you. Can you check the
> VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod that
> you are having problems to remove.
>
> On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
> rafaelweingart...@gmail.com> wrote:
>
> > Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?
> >
> > On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > > wrote:
> >
> >> Sure: http://prntscr.com/g3g7iu
> >>
> >> The last vlan map is the one that I created for testing on the
> >> problematic pod.
> >>
> >> - - - - - - - - - - - - - - - - - - -
> >>
> >> Rodrigo Baldasso - LHOST
> >>
> >> (51) 9 8419-9861
> >> - - - - - - - - - - - - - - - - - - -
> >> On 02/08/2017 10:56:01, Rafael Weingärtner
> >> wrote:
> >> Can you also list the table "pod_vlan_map" for all of the "maps" of
> vlans
> >> for the given POD?
> >>
> >> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> >> wrote:
> >>
> >> > I've created a new vlan/ip pool just for this test (had already
> removed
> >> > all ip pool before), the problem persisted.
> >> >
> >> > here is how the new vlan looks like in my db:
> >> >
> >> > http://prntscr.com/g3fxt1
> >> >
> >> > It's pretty equals to the one of the working pod.
> >> >
> >> >
> >> >
> >> > - - - - - - - - - - - - - - - - - - -
> >> >
> >> > Rodrigo Baldasso - LHOST
> >> >
> >> > (51) 9 8419-9861
> >> > - - - - - - - - - - - - - - - - - - -
> >> > On 02/08/2017 10:21:47, Rafael Weingärtner
> >> > wrote:
> >> > Ok,
> >> >
> >> > Following the code where the null pointer happens at line 163:
> >> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
> >> 4924ac1fb250
> >> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> >> >
> >> > can you list all VLANs in "vlan" table that have the PODid equals one
> of
> >> > the Pods you want to remove?Also, please filter the already removed
> >> VLANs.
> >> >
> >> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> >> > wrote:
> >> >
> >> > > This pod got somewhat corrupted when I change it's IP pool
> allocation
> >> > > cidr. After changing, it didn't started the SSVM's with the
> >> nullpointer
> >> > > error that i've send before and now the pod can't be deleted, also
> >> > throwing
> >> > > the nullpointer error.
> >> > >
> >> > > Thanks.
> >> > >
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > >
> >> > > Rodrigo Baldasso - LHOST
> >> > >
> >> > > (51) 9 8419-9861
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> >> > > wrote:
> >> > > Well, looking at the data you posted, the problem should not happen.
> >> > Let´s
> >> > > take step back. Can you describe briefly what you are trying to do,
> >> and
> >> > > what problem you are having now?
> >> > >
> >> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> >> > > wrote:
> >> > >
> >> > > > Hi Rafael,
> >> > > >
> >> > > > I checked this table yesterday and couldn't find nothing wrong.. i
> >> > made a
> >> > > > line around the vLan of the new pod (that is working). The other
> >> vLans
> >> > > are
> >> > > > from the pod that i'm unable to delete and didn't booted the
> SSVM's.
> >> > They
> >> > > > have the column 'removed' with the date that i deleted them.
> >> > > >
> >> > > > http://prntscr.com/g3eqpr
> >> > > >
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > >
> >> > > > Rodrigo Baldasso - LHOST
> >> > > >
> >> > > > (51) 9 8419-9861
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
> >> > > > wrote:
> >> > > > Rodrigo,
> >> > > >
> >> > > > There is an inconsistency in your database.
> >> > > >
> >> > > > To get this null pointer, the column "vlan_type" of table "vlan"
> >> must
> >> > be
> >> > > > null or something unrecognized in the database. Can you check this
> >> > table?
> >> > > >
> >> > > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> >> > > > wrote:
> >> > > >
> >> > > > > Thank you.
> >> > > > >
> >> > > > > This is the log when I try to delete this pod, if it helps.
> >> > > > >
> >> > > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> >> > > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> >> > > 186.250.14.20
> >> > > > > 

Re: Unable to start SSVM

[Rafael Weingärtner]

What is the ID of the pod you want to remove? 1 or 4?

On Wed, Aug 2, 2017 at 11:03 AM, Rodrigo Baldasso 
wrote:

> Yep: http://prntscr.com/g3gab3
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 11:02:40, Rafael Weingärtner 
> wrote:
> I mean, I said 14 because this was the one select by you. Can you check the
> VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod that
> you are having problems to remove.
>
> On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
> rafaelweingart...@gmail.com> wrote:
>
> > Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?
> >
> > On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > > wrote:
> >
> >> Sure: http://prntscr.com/g3g7iu
> >>
> >> The last vlan map is the one that I created for testing on the
> >> problematic pod.
> >>
> >> - - - - - - - - - - - - - - - - - - -
> >>
> >> Rodrigo Baldasso - LHOST
> >>
> >> (51) 9 8419-9861
> >> - - - - - - - - - - - - - - - - - - -
> >> On 02/08/2017 10:56:01, Rafael Weingärtner
> >> wrote:
> >> Can you also list the table "pod_vlan_map" for all of the "maps" of
> vlans
> >> for the given POD?
> >>
> >> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> >> wrote:
> >>
> >> > I've created a new vlan/ip pool just for this test (had already
> removed
> >> > all ip pool before), the problem persisted.
> >> >
> >> > here is how the new vlan looks like in my db:
> >> >
> >> > http://prntscr.com/g3fxt1
> >> >
> >> > It's pretty equals to the one of the working pod.
> >> >
> >> >
> >> >
> >> > - - - - - - - - - - - - - - - - - - -
> >> >
> >> > Rodrigo Baldasso - LHOST
> >> >
> >> > (51) 9 8419-9861
> >> > - - - - - - - - - - - - - - - - - - -
> >> > On 02/08/2017 10:21:47, Rafael Weingärtner
> >> > wrote:
> >> > Ok,
> >> >
> >> > Following the code where the null pointer happens at line 163:
> >> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
> >> 4924ac1fb250
> >> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> >> >
> >> > can you list all VLANs in "vlan" table that have the PODid equals one
> of
> >> > the Pods you want to remove?Also, please filter the already removed
> >> VLANs.
> >> >
> >> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> >> > wrote:
> >> >
> >> > > This pod got somewhat corrupted when I change it's IP pool
> allocation
> >> > > cidr. After changing, it didn't started the SSVM's with the
> >> nullpointer
> >> > > error that i've send before and now the pod can't be deleted, also
> >> > throwing
> >> > > the nullpointer error.
> >> > >
> >> > > Thanks.
> >> > >
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > >
> >> > > Rodrigo Baldasso - LHOST
> >> > >
> >> > > (51) 9 8419-9861
> >> > > - - - - - - - - - - - - - - - - - - -
> >> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> >> > > wrote:
> >> > > Well, looking at the data you posted, the problem should not happen.
> >> > Let´s
> >> > > take step back. Can you describe briefly what you are trying to do,
> >> and
> >> > > what problem you are having now?
> >> > >
> >> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> >> > > wrote:
> >> > >
> >> > > > Hi Rafael,
> >> > > >
> >> > > > I checked this table yesterday and couldn't find nothing wrong.. i
> >> > made a
> >> > > > line around the vLan of the new pod (that is working). The other
> >> vLans
> >> > > are
> >> > > > from the pod that i'm unable to delete and didn't booted the
> SSVM's.
> >> > They
> >> > > > have the column 'removed' with the date that i deleted them.
> >> > > >
> >> > > > http://prntscr.com/g3eqpr
> >> > > >
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > >
> >> > > > Rodrigo Baldasso - LHOST
> >> > > >
> >> > > > (51) 9 8419-9861
> >> > > > - - - - - - - - - - - - - - - - - - -
> >> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
> >> > > > wrote:
> >> > > > Rodrigo,
> >> > > >
> >> > > > There is an inconsistency in your database.
> >> > > >
> >> > > > To get this null pointer, the column "vlan_type" of table "vlan"
> >> must
> >> > be
> >> > > > null or something unrecognized in the database. Can you check this
> >> > table?
> >> > > >
> >> > > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> >> > > > wrote:
> >> > > >
> >> > > > > Thank you.
> >> > > > >
> >> > > > > This is the log when I try to delete this pod, if it helps.
> >> > > > >
> >> > > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> >> > > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> >> > > 186.250.14.20
> >> > > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> >> > > > > 5da00c4952c2=json&_=1501603382823
> >> > > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> >> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
> >> Rolling
> >> > > back
> >> > > > > the transaction: Time = 179 Name = catalina-exec-9; 

Re: Unable to start SSVM

[Rodrigo Baldasso]

Yep: http://prntscr.com/g3gab3

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 11:02:40, Rafael Weingärtner  wrote:
I mean, I said 14 because this was the one select by you. Can you check the
VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod that
you are having problems to remove.

On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner
rafaelweingart...@gmail.com> wrote:

> Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?
>
> On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso
> > wrote:
>
>> Sure: http://prntscr.com/g3g7iu
>>
>> The last vlan map is the one that I created for testing on the
>> problematic pod.
>>
>> - - - - - - - - - - - - - - - - - - -
>>
>> Rodrigo Baldasso - LHOST
>>
>> (51) 9 8419-9861
>> - - - - - - - - - - - - - - - - - - -
>> On 02/08/2017 10:56:01, Rafael Weingärtner
>> wrote:
>> Can you also list the table "pod_vlan_map" for all of the "maps" of vlans
>> for the given POD?
>>
>> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
>> wrote:
>>
>> > I've created a new vlan/ip pool just for this test (had already removed
>> > all ip pool before), the problem persisted.
>> >
>> > here is how the new vlan looks like in my db:
>> >
>> > http://prntscr.com/g3fxt1
>> >
>> > It's pretty equals to the one of the working pod.
>> >
>> >
>> >
>> > - - - - - - - - - - - - - - - - - - -
>> >
>> > Rodrigo Baldasso - LHOST
>> >
>> > (51) 9 8419-9861
>> > - - - - - - - - - - - - - - - - - - -
>> > On 02/08/2017 10:21:47, Rafael Weingärtner
>> > wrote:
>> > Ok,
>> >
>> > Following the code where the null pointer happens at line 163:
>> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
>> 4924ac1fb250
>> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
>> >
>> > can you list all VLANs in "vlan" table that have the PODid equals one of
>> > the Pods you want to remove?Also, please filter the already removed
>> VLANs.
>> >
>> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
>> > wrote:
>> >
>> > > This pod got somewhat corrupted when I change it's IP pool allocation
>> > > cidr. After changing, it didn't started the SSVM's with the
>> nullpointer
>> > > error that i've send before and now the pod can't be deleted, also
>> > throwing
>> > > the nullpointer error.
>> > >
>> > > Thanks.
>> > >
>> > > - - - - - - - - - - - - - - - - - - -
>> > >
>> > > Rodrigo Baldasso - LHOST
>> > >
>> > > (51) 9 8419-9861
>> > > - - - - - - - - - - - - - - - - - - -
>> > > On 02/08/2017 09:24:36, Rafael Weingärtner
>> > > wrote:
>> > > Well, looking at the data you posted, the problem should not happen.
>> > Let´s
>> > > take step back. Can you describe briefly what you are trying to do,
>> and
>> > > what problem you are having now?
>> > >
>> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
>> > > wrote:
>> > >
>> > > > Hi Rafael,
>> > > >
>> > > > I checked this table yesterday and couldn't find nothing wrong.. i
>> > made a
>> > > > line around the vLan of the new pod (that is working). The other
>> vLans
>> > > are
>> > > > from the pod that i'm unable to delete and didn't booted the SSVM's.
>> > They
>> > > > have the column 'removed' with the date that i deleted them.
>> > > >
>> > > > http://prntscr.com/g3eqpr
>> > > >
>> > > > - - - - - - - - - - - - - - - - - - -
>> > > >
>> > > > Rodrigo Baldasso - LHOST
>> > > >
>> > > > (51) 9 8419-9861
>> > > > - - - - - - - - - - - - - - - - - - -
>> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
>> > > > wrote:
>> > > > Rodrigo,
>> > > >
>> > > > There is an inconsistency in your database.
>> > > >
>> > > > To get this null pointer, the column "vlan_type" of table "vlan"
>> must
>> > be
>> > > > null or something unrecognized in the database. Can you check this
>> > table?
>> > > >
>> > > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
>> > > > wrote:
>> > > >
>> > > > > Thank you.
>> > > > >
>> > > > > This is the log when I try to delete this pod, if it helps.
>> > > > >
>> > > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
>> > > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
>> > > 186.250.14.20
>> > > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
>> > > > > 5da00c4952c2=json&_=1501603382823
>> > > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
>> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
>> Rolling
>> > > back
>> > > > > the transaction: Time = 179 Name = catalina-exec-9; called by
>> > > > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
>> > > > > TransactionLegacy.close:656-Transaction.execute:43-
>> > > > Transaction.execute:47-
>> > > > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
>> > > > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
>> > > > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-Aop
>> Utils.
>> > > > > 

Re: Unable to start SSVM

[Rafael Weingärtner]

I mean, I said 14 because this was the one select by you. Can you check the
VLAN table searching by ID (vlan_db_id) from VLAN map table of the pod that
you are having problems to remove.

On Wed, Aug 2, 2017 at 11:00 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?
>
> On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso  > wrote:
>
>> Sure: http://prntscr.com/g3g7iu
>>
>> The last vlan map is the one that I created for testing on the
>> problematic pod.
>>
>> - - - - - - - - - - - - - - - - - - -
>>
>> Rodrigo Baldasso - LHOST
>>
>> (51) 9 8419-9861
>> - - - - - - - - - - - - - - - - - - -
>> On 02/08/2017 10:56:01, Rafael Weingärtner 
>> wrote:
>> Can you also list the table "pod_vlan_map" for all of the "maps" of vlans
>> for the given POD?
>>
>> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
>> wrote:
>>
>> > I've created a new vlan/ip pool just for this test (had already removed
>> > all ip pool before), the problem persisted.
>> >
>> > here is how the new vlan looks like in my db:
>> >
>> > http://prntscr.com/g3fxt1
>> >
>> > It's pretty equals to the one of the working pod.
>> >
>> >
>> >
>> > - - - - - - - - - - - - - - - - - - -
>> >
>> > Rodrigo Baldasso - LHOST
>> >
>> > (51) 9 8419-9861
>> > - - - - - - - - - - - - - - - - - - -
>> > On 02/08/2017 10:21:47, Rafael Weingärtner
>> > wrote:
>> > Ok,
>> >
>> > Following the code where the null pointer happens at line 163:
>> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f166
>> 4924ac1fb250
>> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
>> >
>> > can you list all VLANs in "vlan" table that have the PODid equals one of
>> > the Pods you want to remove?Also, please filter the already removed
>> VLANs.
>> >
>> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
>> > wrote:
>> >
>> > > This pod got somewhat corrupted when I change it's IP pool allocation
>> > > cidr. After changing, it didn't started the SSVM's with the
>> nullpointer
>> > > error that i've send before and now the pod can't be deleted, also
>> > throwing
>> > > the nullpointer error.
>> > >
>> > > Thanks.
>> > >
>> > > - - - - - - - - - - - - - - - - - - -
>> > >
>> > > Rodrigo Baldasso - LHOST
>> > >
>> > > (51) 9 8419-9861
>> > > - - - - - - - - - - - - - - - - - - -
>> > > On 02/08/2017 09:24:36, Rafael Weingärtner
>> > > wrote:
>> > > Well, looking at the data you posted, the problem should not happen.
>> > Let´s
>> > > take step back. Can you describe briefly what you are trying to do,
>> and
>> > > what problem you are having now?
>> > >
>> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
>> > > wrote:
>> > >
>> > > > Hi Rafael,
>> > > >
>> > > > I checked this table yesterday and couldn't find nothing wrong.. i
>> > made a
>> > > > line around the vLan of the new pod (that is working). The other
>> vLans
>> > > are
>> > > > from the pod that i'm unable to delete and didn't booted the SSVM's.
>> > They
>> > > > have the column 'removed' with the date that i deleted them.
>> > > >
>> > > > http://prntscr.com/g3eqpr
>> > > >
>> > > > - - - - - - - - - - - - - - - - - - -
>> > > >
>> > > > Rodrigo Baldasso - LHOST
>> > > >
>> > > > (51) 9 8419-9861
>> > > > - - - - - - - - - - - - - - - - - - -
>> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
>> > > > wrote:
>> > > > Rodrigo,
>> > > >
>> > > > There is an inconsistency in your database.
>> > > >
>> > > > To get this null pointer, the column "vlan_type" of table "vlan"
>> must
>> > be
>> > > > null or something unrecognized in the database. Can you check this
>> > table?
>> > > >
>> > > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
>> > > > wrote:
>> > > >
>> > > > > Thank you.
>> > > > >
>> > > > > This is the log when I try to delete this pod, if it helps.
>> > > > >
>> > > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
>> > > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
>> > > 186.250.14.20
>> > > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
>> > > > > 5da00c4952c2=json&_=1501603382823
>> > > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
>> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
>> Rolling
>> > > back
>> > > > > the transaction: Time = 179 Name = catalina-exec-9; called by
>> > > > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
>> > > > > TransactionLegacy.close:656-Transaction.execute:43-
>> > > > Transaction.execute:47-
>> > > > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
>> > > > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
>> > > > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-Aop
>> Utils.
>> > > > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
>> > > > > invokeJoinpoint:183
>> > > > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
>> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) 

Re: Unable to start SSVM

[Rafael Weingärtner]

Interesting; now, can you try to find a vlan with ID=14 in "vlan" table?

On Wed, Aug 2, 2017 at 10:58 AM, Rodrigo Baldasso 
wrote:

> Sure: http://prntscr.com/g3g7iu
>
> The last vlan map is the one that I created for testing on the problematic
> pod.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 10:56:01, Rafael Weingärtner 
> wrote:
> Can you also list the table "pod_vlan_map" for all of the "maps" of vlans
> for the given POD?
>
> On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
> wrote:
>
> > I've created a new vlan/ip pool just for this test (had already removed
> > all ip pool before), the problem persisted.
> >
> > here is how the new vlan looks like in my db:
> >
> > http://prntscr.com/g3fxt1
> >
> > It's pretty equals to the one of the working pod.
> >
> >
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 10:21:47, Rafael Weingärtner
> > wrote:
> > Ok,
> >
> > Following the code where the null pointer happens at line 163:
> > https://github.com/apache/cloudstack/blob/0e057ad69edab9f1664924ac1fb250
> > 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
> >
> > can you list all VLANs in "vlan" table that have the PODid equals one of
> > the Pods you want to remove?Also, please filter the already removed
> VLANs.
> >
> > On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> > wrote:
> >
> > > This pod got somewhat corrupted when I change it's IP pool allocation
> > > cidr. After changing, it didn't started the SSVM's with the nullpointer
> > > error that i've send before and now the pod can't be deleted, also
> > throwing
> > > the nullpointer error.
> > >
> > > Thanks.
> > >
> > > - - - - - - - - - - - - - - - - - - -
> > >
> > > Rodrigo Baldasso - LHOST
> > >
> > > (51) 9 8419-9861
> > > - - - - - - - - - - - - - - - - - - -
> > > On 02/08/2017 09:24:36, Rafael Weingärtner
> > > wrote:
> > > Well, looking at the data you posted, the problem should not happen.
> > Let´s
> > > take step back. Can you describe briefly what you are trying to do, and
> > > what problem you are having now?
> > >
> > > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> > > wrote:
> > >
> > > > Hi Rafael,
> > > >
> > > > I checked this table yesterday and couldn't find nothing wrong.. i
> > made a
> > > > line around the vLan of the new pod (that is working). The other
> vLans
> > > are
> > > > from the pod that i'm unable to delete and didn't booted the SSVM's.
> > They
> > > > have the column 'removed' with the date that i deleted them.
> > > >
> > > > http://prntscr.com/g3eqpr
> > > >
> > > > - - - - - - - - - - - - - - - - - - -
> > > >
> > > > Rodrigo Baldasso - LHOST
> > > >
> > > > (51) 9 8419-9861
> > > > - - - - - - - - - - - - - - - - - - -
> > > > On 02/08/2017 09:12:36, Rafael Weingärtner
> > > > wrote:
> > > > Rodrigo,
> > > >
> > > > There is an inconsistency in your database.
> > > >
> > > > To get this null pointer, the column "vlan_type" of table "vlan" must
> > be
> > > > null or something unrecognized in the database. Can you check this
> > table?
> > > >
> > > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> > > > wrote:
> > > >
> > > > > Thank you.
> > > > >
> > > > > This is the log when I try to delete this pod, if it helps.
> > > > >
> > > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> > > 186.250.14.20
> > > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > > > > 5da00c4952c2=json&_=1501603382823
> > > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
> Rolling
> > > back
> > > > > the transaction: Time = 179 Name = catalina-exec-9; called by
> > > > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > > > > TransactionLegacy.close:656-Transaction.execute:43-
> > > > Transaction.execute:47-
> > > > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > > > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > > > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > > > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > > > > invokeJoinpoint:183
> > > > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
> > unhandled
> > > > > exception executing api command: [Ljava.lang.String;@1979ff2d
> > > > > java.lang.NullPointerException
> > > > > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > > > > VlanDaoImpl.java:163)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > > > NativeMethodAccessorImpl.java:57)
> > > > > at 

Re: Unable to start SSVM

[Rodrigo Baldasso]

Sure: http://prntscr.com/g3g7iu

The last vlan map is the one that I created for testing on the problematic pod.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 10:56:01, Rafael Weingärtner  wrote:
Can you also list the table "pod_vlan_map" for all of the "maps" of vlans
for the given POD?

On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso
wrote:

> I've created a new vlan/ip pool just for this test (had already removed
> all ip pool before), the problem persisted.
>
> here is how the new vlan looks like in my db:
>
> http://prntscr.com/g3fxt1
>
> It's pretty equals to the one of the working pod.
>
>
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 10:21:47, Rafael Weingärtner
> wrote:
> Ok,
>
> Following the code where the null pointer happens at line 163:
> https://github.com/apache/cloudstack/blob/0e057ad69edab9f1664924ac1fb250
> 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
>
> can you list all VLANs in "vlan" table that have the PODid equals one of
> the Pods you want to remove?Also, please filter the already removed VLANs.
>
> On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> wrote:
>
> > This pod got somewhat corrupted when I change it's IP pool allocation
> > cidr. After changing, it didn't started the SSVM's with the nullpointer
> > error that i've send before and now the pod can't be deleted, also
> throwing
> > the nullpointer error.
> >
> > Thanks.
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 09:24:36, Rafael Weingärtner
> > wrote:
> > Well, looking at the data you posted, the problem should not happen.
> Let´s
> > take step back. Can you describe briefly what you are trying to do, and
> > what problem you are having now?
> >
> > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> > wrote:
> >
> > > Hi Rafael,
> > >
> > > I checked this table yesterday and couldn't find nothing wrong.. i
> made a
> > > line around the vLan of the new pod (that is working). The other vLans
> > are
> > > from the pod that i'm unable to delete and didn't booted the SSVM's.
> They
> > > have the column 'removed' with the date that i deleted them.
> > >
> > > http://prntscr.com/g3eqpr
> > >
> > > - - - - - - - - - - - - - - - - - - -
> > >
> > > Rodrigo Baldasso - LHOST
> > >
> > > (51) 9 8419-9861
> > > - - - - - - - - - - - - - - - - - - -
> > > On 02/08/2017 09:12:36, Rafael Weingärtner
> > > wrote:
> > > Rodrigo,
> > >
> > > There is an inconsistency in your database.
> > >
> > > To get this null pointer, the column "vlan_type" of table "vlan" must
> be
> > > null or something unrecognized in the database. Can you check this
> table?
> > >
> > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> > > wrote:
> > >
> > > > Thank you.
> > > >
> > > > This is the log when I try to delete this pod, if it helps.
> > > >
> > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> > 186.250.14.20
> > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > > > 5da00c4952c2=json&_=1501603382823
> > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling
> > back
> > > > the transaction: Time = 179 Name = catalina-exec-9; called by
> > > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > > > TransactionLegacy.close:656-Transaction.execute:43-
> > > Transaction.execute:47-
> > > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > > > invokeJoinpoint:183
> > > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
> unhandled
> > > > exception executing api command: [Ljava.lang.String;@1979ff2d
> > > > java.lang.NullPointerException
> > > > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > > > VlanDaoImpl.java:163)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > > NativeMethodAccessorImpl.java:57)
> > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > > DelegatingMethodAccessorImpl.java:43)
> > > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > > at org.springframework.aop.support.AopUtils.
> > > > invokeJoinpointUsingReflection(AopUtils.java:317)
> > > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > > > at 

Re: Unable to start SSVM

[Rafael Weingärtner]

Can you also list the table "pod_vlan_map" for all of the "maps" of vlans
for the given POD?

On Wed, Aug 2, 2017 at 10:40 AM, Rodrigo Baldasso 
wrote:

> I've created a new vlan/ip pool just for this test (had already removed
> all ip pool before), the problem persisted.
>
> here is how the new vlan looks like in my db:
>
> http://prntscr.com/g3fxt1
>
> It's pretty equals to the one of the working pod.
>
>
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 10:21:47, Rafael Weingärtner 
> wrote:
> Ok,
>
> Following the code where the null pointer happens at line 163:
> https://github.com/apache/cloudstack/blob/0e057ad69edab9f1664924ac1fb250
> 0ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java
>
> can you list all VLANs in "vlan" table that have the PODid equals one of
> the Pods you want to remove?Also, please filter the already removed VLANs.
>
> On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
> wrote:
>
> > This pod got somewhat corrupted when I change it's IP pool allocation
> > cidr. After changing, it didn't started the SSVM's with the nullpointer
> > error that i've send before and now the pod can't be deleted, also
> throwing
> > the nullpointer error.
> >
> > Thanks.
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 09:24:36, Rafael Weingärtner
> > wrote:
> > Well, looking at the data you posted, the problem should not happen.
> Let´s
> > take step back. Can you describe briefly what you are trying to do, and
> > what problem you are having now?
> >
> > On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> > wrote:
> >
> > > Hi Rafael,
> > >
> > > I checked this table yesterday and couldn't find nothing wrong.. i
> made a
> > > line around the vLan of the new pod (that is working). The other vLans
> > are
> > > from the pod that i'm unable to delete and didn't booted the SSVM's.
> They
> > > have the column 'removed' with the date that i deleted them.
> > >
> > > http://prntscr.com/g3eqpr
> > >
> > > - - - - - - - - - - - - - - - - - - -
> > >
> > > Rodrigo Baldasso - LHOST
> > >
> > > (51) 9 8419-9861
> > > - - - - - - - - - - - - - - - - - - -
> > > On 02/08/2017 09:12:36, Rafael Weingärtner
> > > wrote:
> > > Rodrigo,
> > >
> > > There is an inconsistency in your database.
> > >
> > > To get this null pointer, the column "vlan_type" of table "vlan" must
> be
> > > null or something unrecognized in the database. Can you check this
> table?
> > >
> > > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> > > wrote:
> > >
> > > > Thank you.
> > > >
> > > > This is the log when I try to delete this pod, if it helps.
> > > >
> > > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> > 186.250.14.20
> > > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > > > 5da00c4952c2=json&_=1501603382823
> > > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling
> > back
> > > > the transaction: Time = 179 Name = catalina-exec-9; called by
> > > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > > > TransactionLegacy.close:656-Transaction.execute:43-
> > > Transaction.execute:47-
> > > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > > > invokeJoinpoint:183
> > > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f)
> unhandled
> > > > exception executing api command: [Ljava.lang.String;@1979ff2d
> > > > java.lang.NullPointerException
> > > > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > > > VlanDaoImpl.java:163)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > > NativeMethodAccessorImpl.java:57)
> > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > > DelegatingMethodAccessorImpl.java:43)
> > > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > > at org.springframework.aop.support.AopUtils.
> > > > invokeJoinpointUsingReflection(AopUtils.java:317)
> > > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > > proceed(ReflectiveMethodInvocation.java:150)
> > > > at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> > > > TransactionContextInterceptor.java:34)
> > > > at 

Re: Unable to start SSVM

[Rodrigo Baldasso]

I've created a new vlan/ip pool just for this test (had already removed all ip 
pool before), the problem persisted.

here is how the new vlan looks like in my db:

http://prntscr.com/g3fxt1

It's pretty equals to the one of the working pod.



- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 10:21:47, Rafael Weingärtner  wrote:
Ok,

Following the code where the null pointer happens at line 163:
https://github.com/apache/cloudstack/blob/0e057ad69edab9f1664924ac1fb2500ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java

can you list all VLANs in "vlan" table that have the PODid equals one of
the Pods you want to remove?Also, please filter the already removed VLANs.

On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso
wrote:

> This pod got somewhat corrupted when I change it's IP pool allocation
> cidr. After changing, it didn't started the SSVM's with the nullpointer
> error that i've send before and now the pod can't be deleted, also throwing
> the nullpointer error.
>
> Thanks.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 09:24:36, Rafael Weingärtner
> wrote:
> Well, looking at the data you posted, the problem should not happen. Let´s
> take step back. Can you describe briefly what you are trying to do, and
> what problem you are having now?
>
> On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> wrote:
>
> > Hi Rafael,
> >
> > I checked this table yesterday and couldn't find nothing wrong.. i made a
> > line around the vLan of the new pod (that is working). The other vLans
> are
> > from the pod that i'm unable to delete and didn't booted the SSVM's. They
> > have the column 'removed' with the date that i deleted them.
> >
> > http://prntscr.com/g3eqpr
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 09:12:36, Rafael Weingärtner
> > wrote:
> > Rodrigo,
> >
> > There is an inconsistency in your database.
> >
> > To get this null pointer, the column "vlan_type" of table "vlan" must be
> > null or something unrecognized in the database. Can you check this table?
> >
> > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> > wrote:
> >
> > > Thank you.
> > >
> > > This is the log when I try to delete this pod, if it helps.
> > >
> > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> 186.250.14.20
> > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > > 5da00c4952c2=json&_=1501603382823
> > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling
> back
> > > the transaction: Time = 179 Name = catalina-exec-9; called by
> > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > > TransactionLegacy.close:656-Transaction.execute:43-
> > Transaction.execute:47-
> > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > > invokeJoinpoint:183
> > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> > > exception executing api command: [Ljava.lang.String;@1979ff2d
> > > java.lang.NullPointerException
> > > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > > VlanDaoImpl.java:163)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > NativeMethodAccessorImpl.java:57)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:43)
> > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > at org.springframework.aop.support.AopUtils.
> > > invokeJoinpointUsingReflection(AopUtils.java:317)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:150)
> > > at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> > > TransactionContextInterceptor.java:34)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:161)
> > > at org.springframework.aop.interceptor.
> > > ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.
> java:91)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:172)
> > > at org.springframework.aop.framework.JdkDynamicAopProxy.
> > > invoke(JdkDynamicAopProxy.java:204)
> > > at 

Re: Some things I found out installing on Centos 7

[Ron Wheeler]

+1
This is indicative of why Cloudstack lacks market following.
It does not look like a product that you can bet your career on.
This was discussed at the meeting in Montreal last year but died shortly 
thereafter.


It is probably time to freeze development until the docs and wiki are 
cleaned up.

Won't happen but should.
Unfortunately it takes a team effort to fix this.
There is no doubt that the team has the talent.


Ron

On 02/08/2017 4:12 AM, Eric Green wrote:

First, about me -- I've been administering Linux systems since 1995. No, that's 
not a typo -- that's 22 years. I've also worked for a firewall manufacturer in 
the past, I designed the layer 2 VLAN support for a firewall vendor, so I know 
VLAN's and such. I run a fairly complex production network with multiple 
VLAN's, multiple networks, etc. already, and speak fluent Cisco CLI. In short, 
I'm not an amateur at this networking stuff, but figuring out how Cloudstack 
wanted my CentOS 7 networking to be configured, and doing all the gymnastics to 
make it happen, consumed nearly a week because the documentation simply isn't 
up to date, thorough, or accurate, at least for Centos 7.

So anyhow, my configuration:

Cloudstack 4.9.2.0 from the RPM repository at cloudstack.apt-get.eu

Centos 7 servers with:

2 10gbit Ethernet ports -> bond0

A handful of VLANS:

100 -- from my top of rack switch is sent to my core backbone switch layer 3 
routed to my local network as 10.100.x.x and thru the NAT border firewall and 
router to the Internet. Management.
101 -- same but for 10.101.x.x  -- public.
102 -- same but for 10.102.x.x  -- guest public (see below).
192 -- A video surveillance camera network that is not routed to anywhere, via 
a drop from the core video surveillance POE switch to an access mode port on my 
top of rack switch. Not routed.
200 -- 10 gig drop over to my production racks to my storage network there for 
accessing legacy storage. Not routed. (Legacy storage is not used for 
Cloudstack instance or secondary storage but can be accessed by virtual 
machines being migrated to this rack).
1000-2000 -- VLAN's that exist in my top of rack switch on the Cloudstack rack 
and assigned to my trunk ports to the cloud servers but routed nowhere else, 
for VPC's and such.

Stuck with VLAN's rather than one of the SDN modules like VXNET because a) it's 
the oldest and most likely to be stable, b) compatible with my already-existing 
network hardware and networks (wouldn't have to somehow map a VLAN to a SDN 
virtual network to reach 192 or 200 or create a public 102), and c) least 
complex to set up and configure given my existing top-of-rack switch that does 
VLANs just fine.

Okay, here's how I had to configure Centos 7 to make it work:

enp4s[01] -> bond0 -> bond0.100 -> br100  -- had to create two interface files, 
add them to bond0 bridge, then create a bond0.100 vlan interface, then a br100 bridge,  
for my management network. In
/etc/sysconfig-network-scripts:

# ls ifcfg-*
ifcfg-bond0 ifcfg-bond0.100 ifcfg-br100 ifcfg-enp4s0 ifcfg-enp4s1

(where 4s0 and 4s1 are my 10 gigabit Ethernets).

Don't create anything else. You'll just confuse Cloudstack. Any other 
configuration of the network simply fails to work. In particular, creating 
br101 etc. fails because CloudStack wants to create its own VLANs and  bridges 
and if you traffic label it as br101 it'll try making vlan br101.101 (doesn't 
work, duh). Yes, I know this contradicts every single piece of advice I've seen 
on this list. All I know is that this is what works, while every other piece of 
advice I've seen for labeling the public and private guest networking fails.

When creating the networks in the GUI under Advanced networking, set bond0 as your physical 
network and br100 as the KVM traffic label for the Management network and Storage network 
and give them addresses with VLAN 100 (assuming you're using the same network for both 
management and storage networks, which is what makes sense with my single 10gbit pipe), but 
do *not* set up anything as a traffic label for Guest or Public networks. You will confuse 
the agent greatly. Let it use the default labels. It'll work. It'll set up its on 
bond0. VLAN interface and brbond0- as needed. This violates every 
other piece of advice I've seen for labeling, but this is what actually works with this 
version of Cloudstack and this version of Centos when you're sending everything through a 
VLAN-tagged bond0.

A very important configuration option *not* documented in the installation 
documents:

secstorage.allowed.internal.sites=10.100.0.0/16

(for my particular network).

Otherwise I couldn't upload ISO files to the server from my nginx server that's 
pointing at the NFS directory full of ISO files.

---

Very important guest VM image prep *NOT* in the docs:

Be sure to install / enable / run acpid on Linux guests, otherwise "clean" 
shutdowns can't happen. Turns out Cloudstack on KVM uses the ACPI shutdown functionality 
of 

Re: Unable to start SSVM

[Rafael Weingärtner]

Ok,

Following the code where the null pointer happens at line 163:
https://github.com/apache/cloudstack/blob/0e057ad69edab9f1664924ac1fb2500ca799cfb6/engine/schema/src/com/cloud/dc/dao/VlanDaoImpl.java

can you list all VLANs in "vlan" table that have the PODid equals one of
the Pods you want to remove?Also, please filter the already removed VLANs.

On Wed, Aug 2, 2017 at 9:26 AM, Rodrigo Baldasso 
wrote:

> This pod got somewhat corrupted when I change it's IP pool allocation
> cidr. After changing, it didn't started the SSVM's with the nullpointer
> error that i've send before and now the pod can't be deleted, also throwing
> the nullpointer error.
>
> Thanks.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 09:24:36, Rafael Weingärtner 
> wrote:
> Well, looking at the data you posted, the problem should not happen. Let´s
> take step back. Can you describe briefly what you are trying to do, and
> what problem you are having now?
>
> On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
> wrote:
>
> > Hi Rafael,
> >
> > I checked this table yesterday and couldn't find nothing wrong.. i made a
> > line around the vLan of the new pod (that is working). The other vLans
> are
> > from the pod that i'm unable to delete and didn't booted the SSVM's. They
> > have the column 'removed' with the date that i deleted them.
> >
> > http://prntscr.com/g3eqpr
> >
> > - - - - - - - - - - - - - - - - - - -
> >
> > Rodrigo Baldasso - LHOST
> >
> > (51) 9 8419-9861
> > - - - - - - - - - - - - - - - - - - -
> > On 02/08/2017 09:12:36, Rafael Weingärtner
> > wrote:
> > Rodrigo,
> >
> > There is an inconsistency in your database.
> >
> > To get this null pointer, the column "vlan_type" of table "vlan" must be
> > null or something unrecognized in the database. Can you check this table?
> >
> > On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> > wrote:
> >
> > > Thank you.
> > >
> > > This is the log when I try to delete this pod, if it helps.
> > >
> > > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===
> 186.250.14.20
> > > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > > 5da00c4952c2=json&_=1501603382823
> > > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling
> back
> > > the transaction: Time = 179 Name = catalina-exec-9; called by
> > > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > > TransactionLegacy.close:656-Transaction.execute:43-
> > Transaction.execute:47-
> > > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > > invokeJoinpoint:183
> > > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> > > exception executing api command: [Ljava.lang.String;@1979ff2d
> > > java.lang.NullPointerException
> > > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > > VlanDaoImpl.java:163)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > NativeMethodAccessorImpl.java:57)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:43)
> > > at java.lang.reflect.Method.invoke(Method.java:606)
> > > at org.springframework.aop.support.AopUtils.
> > > invokeJoinpointUsingReflection(AopUtils.java:317)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:150)
> > > at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> > > TransactionContextInterceptor.java:34)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:161)
> > > at org.springframework.aop.interceptor.
> > > ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.
> java:91)
> > > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > > proceed(ReflectiveMethodInvocation.java:172)
> > > at org.springframework.aop.framework.JdkDynamicAopProxy.
> > > invoke(JdkDynamicAopProxy.java:204)
> > > at com.sun.proxy.$Proxy113.listVlansForPodByType(Unknown Source)
> > > at com.cloud.network.NetworkModelImpl.listPodVlans(
> > > NetworkModelImpl.java:797)
> > > at com.cloud.configuration.ConfigurationManagerImpl$1.
> > > doInTransactionWithoutResult(ConfigurationManagerImpl.java:1029)
> > > at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(
> > > 

Re: Unable to start SSVM

[Rodrigo Baldasso]

This pod got somewhat corrupted when I change it's IP pool allocation cidr. 
After changing, it didn't started the SSVM's with the nullpointer error that 
i've send before and now the pod can't be deleted, also throwing the 
nullpointer error.

Thanks.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 09:24:36, Rafael Weingärtner  wrote:
Well, looking at the data you posted, the problem should not happen. Let´s
take step back. Can you describe briefly what you are trying to do, and
what problem you are having now?

On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso
wrote:

> Hi Rafael,
>
> I checked this table yesterday and couldn't find nothing wrong.. i made a
> line around the vLan of the new pod (that is working). The other vLans are
> from the pod that i'm unable to delete and didn't booted the SSVM's. They
> have the column 'removed' with the date that i deleted them.
>
> http://prntscr.com/g3eqpr
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 09:12:36, Rafael Weingärtner
> wrote:
> Rodrigo,
>
> There is an inconsistency in your database.
>
> To get this null pointer, the column "vlan_type" of table "vlan" must be
> null or something unrecognized in the database. Can you check this table?
>
> On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> wrote:
>
> > Thank you.
> >
> > This is the log when I try to delete this pod, if it helps.
> >
> > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START=== 186.250.14.20
> > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > 5da00c4952c2=json&_=1501603382823
> > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling back
> > the transaction: Time = 179 Name = catalina-exec-9; called by
> > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > TransactionLegacy.close:656-Transaction.execute:43-
> Transaction.execute:47-
> > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > invokeJoinpoint:183
> > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> > exception executing api command: [Ljava.lang.String;@1979ff2d
> > java.lang.NullPointerException
> > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > VlanDaoImpl.java:163)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:57)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at org.springframework.aop.support.AopUtils.
> > invokeJoinpointUsingReflection(AopUtils.java:317)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:150)
> > at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> > TransactionContextInterceptor.java:34)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:161)
> > at org.springframework.aop.interceptor.
> > ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:172)
> > at org.springframework.aop.framework.JdkDynamicAopProxy.
> > invoke(JdkDynamicAopProxy.java:204)
> > at com.sun.proxy.$Proxy113.listVlansForPodByType(Unknown Source)
> > at com.cloud.network.NetworkModelImpl.listPodVlans(
> > NetworkModelImpl.java:797)
> > at com.cloud.configuration.ConfigurationManagerImpl$1.
> > doInTransactionWithoutResult(ConfigurationManagerImpl.java:1029)
> > at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(
> > TransactionCallbackNoReturn.java:25)
> > at com.cloud.utils.db.Transaction$2.doInTransaction(
> > Transaction.java:50)
> > at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
> > at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
> > at com.cloud.configuration.ConfigurationManagerImpl.deletePod(
> > ConfigurationManagerImpl.java:1009)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:57)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at 

Re: Unable to start SSVM

[Rafael Weingärtner]

Well, looking at the data you posted, the problem should not happen. Let´s
take step back. Can you describe briefly what you are trying to do, and
what problem you are having now?

On Wed, Aug 2, 2017 at 9:17 AM, Rodrigo Baldasso 
wrote:

> Hi Rafael,
>
> I checked this table yesterday and couldn't find nothing wrong.. i made a
> line around the vLan of the new pod (that is working). The other vLans are
> from the pod that i'm unable to delete and didn't booted the SSVM's. They
> have the column 'removed' with the date that i deleted them.
>
> http://prntscr.com/g3eqpr
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 02/08/2017 09:12:36, Rafael Weingärtner 
> wrote:
> Rodrigo,
>
> There is an inconsistency in your database.
>
> To get this null pointer, the column "vlan_type" of table "vlan" must be
> null or something unrecognized in the database. Can you check this table?
>
> On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
> wrote:
>
> > Thank you.
> >
> > This is the log when I try to delete this pod, if it helps.
> >
> > 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START=== 186.250.14.20
> > -- GET command=deletePod=39e23530-0553-4b54-948d-
> > 5da00c4952c2=json&_=1501603382823
> > 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling back
> > the transaction: Time = 179 Name = catalina-exec-9; called by
> > -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> > TransactionLegacy.close:656-Transaction.execute:43-
> Transaction.execute:47-
> > ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> > invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> > DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> > invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> > invokeJoinpoint:183
> > 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> > (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> > exception executing api command: [Ljava.lang.String;@1979ff2d
> > java.lang.NullPointerException
> > at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> > VlanDaoImpl.java:163)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:57)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at org.springframework.aop.support.AopUtils.
> > invokeJoinpointUsingReflection(AopUtils.java:317)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:150)
> > at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> > TransactionContextInterceptor.java:34)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:161)
> > at org.springframework.aop.interceptor.
> > ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:172)
> > at org.springframework.aop.framework.JdkDynamicAopProxy.
> > invoke(JdkDynamicAopProxy.java:204)
> > at com.sun.proxy.$Proxy113.listVlansForPodByType(Unknown Source)
> > at com.cloud.network.NetworkModelImpl.listPodVlans(
> > NetworkModelImpl.java:797)
> > at com.cloud.configuration.ConfigurationManagerImpl$1.
> > doInTransactionWithoutResult(ConfigurationManagerImpl.java:1029)
> > at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(
> > TransactionCallbackNoReturn.java:25)
> > at com.cloud.utils.db.Transaction$2.doInTransaction(
> > Transaction.java:50)
> > at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
> > at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
> > at com.cloud.configuration.ConfigurationManagerImpl.deletePod(
> > ConfigurationManagerImpl.java:1009)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:57)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:606)
> > at org.springframework.aop.support.AopUtils.
> > invokeJoinpointUsingReflection(AopUtils.java:317)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > at org.springframework.aop.framework.ReflectiveMethodInvocation.
> > proceed(ReflectiveMethodInvocation.java:150)
> > at org.springframework.aop.interceptor.
> 

Re: Unable to start SSVM

[Rodrigo Baldasso]

Hi Rafael,

I checked this table yesterday and couldn't find nothing wrong.. i made a line 
around the vLan of the new pod (that is working). The other vLans are from the 
pod that i'm unable to delete and didn't booted the SSVM's. They have the 
column 'removed' with the date that i deleted them.

http://prntscr.com/g3eqpr

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 02/08/2017 09:12:36, Rafael Weingärtner  wrote:
Rodrigo,

There is an inconsistency in your database.

To get this null pointer, the column "vlan_type" of table "vlan" must be
null or something unrecognized in the database. Can you check this table?

On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso
wrote:

> Thank you.
>
> This is the log when I try to delete this pod, if it helps.
>
> 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START=== 186.250.14.20
> -- GET command=deletePod=39e23530-0553-4b54-948d-
> 5da00c4952c2=json&_=1501603382823
> 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling back
> the transaction: Time = 179 Name = catalina-exec-9; called by
> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-
> ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> invokeJoinpoint:183
> 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> exception executing api command: [Ljava.lang.String;@1979ff2d
> java.lang.NullPointerException
> at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> VlanDaoImpl.java:163)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> TransactionContextInterceptor.java:34)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:161)
> at org.springframework.aop.interceptor.
> ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy113.listVlansForPodByType(Unknown Source)
> at com.cloud.network.NetworkModelImpl.listPodVlans(
> NetworkModelImpl.java:797)
> at com.cloud.configuration.ConfigurationManagerImpl$1.
> doInTransactionWithoutResult(ConfigurationManagerImpl.java:1029)
> at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(
> TransactionCallbackNoReturn.java:25)
> at com.cloud.utils.db.Transaction$2.doInTransaction(
> Transaction.java:50)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
> at com.cloud.configuration.ConfigurationManagerImpl.deletePod(
> ConfigurationManagerImpl.java:1009)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> at org.springframework.aop.interceptor.
> ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy119.deletePod(Unknown Source)
> at org.apache.cloudstack.api.command.admin.pod.
> DeletePodCmd.execute(DeletePodCmd.java:70)
> at 

Re: Unable to start SSVM

[Rafael Weingärtner]

Rodrigo,

There is an inconsistency in your database.

To get this null pointer, the column "vlan_type" of table "vlan" must be
null or something unrecognized in the database. Can you check this table?

On Tue, Aug 1, 2017 at 1:03 PM, Rodrigo Baldasso 
wrote:

> Thank you.
>
> This is the log when I try to delete this pod, if it helps.
>
> 2017-08-01 13:03:01,361 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-9:ctx-262022ac) (logid:91c02e8f) ===START===  186.250.14.20
> -- GET  command=deletePod=39e23530-0553-4b54-948d-
> 5da00c4952c2=json&_=1501603382823
> 2017-08-01 13:03:01,556 DEBUG [c.c.u.d.T.Transaction]
> (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) Rolling back
> the transaction: Time = 179 Name =  catalina-exec-9; called by
> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-
> TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-
> ConfigurationManagerImpl.deletePod:1009-NativeMethodAccessorImpl.
> invoke0:-2-NativeMethodAccessorImpl.invoke:57-
> DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.
> invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.
> invokeJoinpoint:183
> 2017-08-01 13:03:01,667 ERROR [c.c.a.ApiServer]
> (catalina-exec-9:ctx-262022ac ctx-77de8cad) (logid:91c02e8f) unhandled
> exception executing api command: [Ljava.lang.String;@1979ff2d
> java.lang.NullPointerException
> at com.cloud.dc.dao.VlanDaoImpl.listVlansForPodByType(
> VlanDaoImpl.java:163)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> at com.cloud.utils.db.TransactionContextInterceptor.invoke(
> TransactionContextInterceptor.java:34)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:161)
> at org.springframework.aop.interceptor.
> ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy113.listVlansForPodByType(Unknown Source)
> at com.cloud.network.NetworkModelImpl.listPodVlans(
> NetworkModelImpl.java:797)
> at com.cloud.configuration.ConfigurationManagerImpl$1.
> doInTransactionWithoutResult(ConfigurationManagerImpl.java:1029)
> at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(
> TransactionCallbackNoReturn.java:25)
> at com.cloud.utils.db.Transaction$2.doInTransaction(
> Transaction.java:50)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
> at com.cloud.configuration.ConfigurationManagerImpl.deletePod(
> ConfigurationManagerImpl.java:1009)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.springframework.aop.support.AopUtils.
> invokeJoinpointUsingReflection(AopUtils.java:317)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> at org.springframework.aop.interceptor.
> ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> at org.springframework.aop.framework.JdkDynamicAopProxy.
> invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy119.deletePod(Unknown Source)
> at org.apache.cloudstack.api.command.admin.pod.
> DeletePodCmd.execute(DeletePodCmd.java:70)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:709)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:533)
> at 

Some things I found out installing on Centos 7

[Eric Green]

First, about me -- I've been administering Linux systems since 1995. No, that's 
not a typo -- that's 22 years. I've also worked for a firewall manufacturer in 
the past, I designed the layer 2 VLAN support for a firewall vendor, so I know 
VLAN's and such. I run a fairly complex production network with multiple 
VLAN's, multiple networks, etc. already, and speak fluent Cisco CLI. In short, 
I'm not an amateur at this networking stuff, but figuring out how Cloudstack 
wanted my CentOS 7 networking to be configured, and doing all the gymnastics to 
make it happen, consumed nearly a week because the documentation simply isn't 
up to date, thorough, or accurate, at least for Centos 7. 

So anyhow, my configuration:

Cloudstack 4.9.2.0 from the RPM repository at cloudstack.apt-get.eu

Centos 7 servers with:

2 10gbit Ethernet ports -> bond0 

A handful of VLANS:

100 -- from my top of rack switch is sent to my core backbone switch layer 3 
routed to my local network as 10.100.x.x and thru the NAT border firewall and 
router to the Internet. Management.
101 -- same but for 10.101.x.x  -- public.
102 -- same but for 10.102.x.x  -- guest public (see below).
192 -- A video surveillance camera network that is not routed to anywhere, via 
a drop from the core video surveillance POE switch to an access mode port on my 
top of rack switch. Not routed.
200 -- 10 gig drop over to my production racks to my storage network there for 
accessing legacy storage. Not routed. (Legacy storage is not used for 
Cloudstack instance or secondary storage but can be accessed by virtual 
machines being migrated to this rack).
1000-2000 -- VLAN's that exist in my top of rack switch on the Cloudstack rack 
and assigned to my trunk ports to the cloud servers but routed nowhere else, 
for VPC's and such. 

Stuck with VLAN's rather than one of the SDN modules like VXNET because a) it's 
the oldest and most likely to be stable, b) compatible with my already-existing 
network hardware and networks (wouldn't have to somehow map a VLAN to a SDN 
virtual network to reach 192 or 200 or create a public 102), and c) least 
complex to set up and configure given my existing top-of-rack switch that does 
VLANs just fine.

Okay, here's how I had to configure Centos 7 to make it work: 

enp4s[01] -> bond0 -> bond0.100 -> br100  -- had to create two interface files, 
add them to bond0 bridge, then create a bond0.100 vlan interface, then a br100 
bridge,  for my management network. In
/etc/sysconfig-network-scripts: 

# ls ifcfg-*
ifcfg-bond0 ifcfg-bond0.100 ifcfg-br100 ifcfg-enp4s0 ifcfg-enp4s1

(where 4s0 and 4s1 are my 10 gigabit Ethernets).

Don't create anything else. You'll just confuse Cloudstack. Any other 
configuration of the network simply fails to work. In particular, creating 
br101 etc. fails because CloudStack wants to create its own VLANs and  bridges 
and if you traffic label it as br101 it'll try making vlan br101.101 (doesn't 
work, duh). Yes, I know this contradicts every single piece of advice I've seen 
on this list. All I know is that this is what works, while every other piece of 
advice I've seen for labeling the public and private guest networking fails. 

When creating the networks in the GUI under Advanced networking, set bond0 as 
your physical network and br100 as the KVM traffic label for the Management 
network and Storage network and give them addresses with VLAN 100 (assuming 
you're using the same network for both management and storage networks, which 
is what makes sense with my single 10gbit pipe), but do *not* set up anything 
as a traffic label for Guest or Public networks. You will confuse the agent 
greatly. Let it use the default labels. It'll work. It'll set up its on 
bond0. VLAN interface and brbond0- as needed. This violates every 
other piece of advice I've seen for labeling, but this is what actually works 
with this version of Cloudstack and this version of Centos when you're sending 
everything through a VLAN-tagged bond0.

A very important configuration option *not* documented in the installation 
documents:

secstorage.allowed.internal.sites=10.100.0.0/16

(for my particular network). 

Otherwise I couldn't upload ISO files to the server from my nginx server that's 
pointing at the NFS directory full of ISO files.

---

Very important guest VM image prep *NOT* in the docs:

Be sure to install / enable / run acpid on Linux guests, otherwise "clean" 
shutdowns can't happen. Turns out Cloudstack on KVM uses the ACPI shutdown 
functionality of qemu-kvm. Probably does that on other hypervisors too.

---

Now on for that mysterious VLAN 102:

I created a "public" shared network on the 102 vlan for stuff I don't care is 
out in the open. This is a QA lab environment, not a public cloud. So I 
assigned a subnet and a VLAN, ran a VLAN drop over to my main backbone layer 3 
switch (and bopped up to my border firewall and told it about the new subnet 
too so that we could get out to the Internet as needed), and