Good to hear. Glad I could lend another pair of eyes.
On Mon, Mar 16, 2015 at 9:19 AM, Andrija Panic <andrija.panic@gmail.com> wrote:
> FIXED !!!
>
> Thanks a lot Marcus, this is the second time you saved me from the deep
> $$it..
>
> Only 1 VM that had only 1 NIC and not set to default in DB  so just after
> changing that default_nic=1, destroyed the VR, and new one was recreated.
>
> Thanks a lot for help !
>
>
> On 16 March 2015 at 16:52, Andrija Panic <andrija.panic@gmail.com> wrote:
>
>> I will thanks a lot Marcus for hints...
>>
>> On 16 March 2015 at 16:49, Marcus <shadowsor@gmail.com> wrote:
>>
>>> Ok, just watch for those createdhcpentry mgmt server logs. Perhaps
>>> they're just triggered by you trying to fix the situation by
>>> migrating, but the original issue was something else entirely.
>>>
>>> On Mon, Mar 16, 2015 at 8:44 AM, Andrija Panic <andrija.panic@gmail.com>
>>> wrote:
>>> > I did migrate and also changed accounts, unsucessfully, so some bugs
>>> > definitively or my specific setup...
>>> >
>>> > Thanks, I' fixing this now and will let you know.
>>> >
>>> > On 16 March 2015 at 16:42, Marcus <shadowsor@gmail.com> wrote:
>>> >
>>> >> Yes, each VM should have at least one default nic, so if there's only
>>> >> one nic it should be set to default. Take a db backup first, of
>>> >> course, before messing with it. Any idea how it may have happened? Do
>>> >> you migrate VMs between networks ever?
>>> >>
>>> >> On Mon, Mar 16, 2015 at 8:39 AM, Andrija Panic <
>>> andrija.panic@gmail.com>
>>> >> wrote:
>>> >> > Ok, so if the VM has only 1 VM  and default_nic=0, then I need
to
>>> change
>>> >> > all of them to default_nic=1... ?
>>> >> >
>>> >> >
>>> >> > On 16 March 2015 at 16:38, Marcus <shadowsor@gmail.com> wrote:
>>> >> >
>>> >> >> VMs can have multiple nics and be on multiple networks. If
you set a
>>> >> >> nic as default, it becomes the network that the vm has its
default
>>> >> >> route on. Every VM should have a default nic, and if it doesn't
I
>>> >> >> wonder how it might have happened (maybe a specific combination
of
>>> >> >> add/delete nic triggered a bug?). You should set a default
nic for
>>> >> >> every VM that might be missing one, and see if that gets your
router
>>> >> >> up.
>>> >> >>
>>> >> >> On Mon, Mar 16, 2015 at 8:34 AM, Andrija Panic <
>>> andrija.panic@gmail.com
>>> >> >
>>> >> >> wrote:
>>> >> >> > Hi Marcus,
>>> >> >> >
>>> >> >> > Thanks a lot fot hint
>>> >> >> >
>>> >> >> > True, I have the 0 as the value for some reason in database,
for
>>> >> couple
>>> >> >> of
>>> >> >> > NICs....
>>> >> >> > select * from nics where ip4_address like "46.232%" and
>>> broadcast_uri
>>> >> =
>>> >> >> > "vlan://500" and default_nic = 0;
>>> >> >> >
>>> >> >> > results: http://pastebin.com/rDAe2RY9
>>> >> >> >
>>> >> >> > or down there...
>>> >> >> >
>>> >> >> > This TechveeFileServer server is already running (still
not dead)
>>> >> and I
>>> >> >> > can see 1 NIC from UI...
>>> >> >> >
>>> >> >> > Should I reset all of these to 1 ?
>>> >> >> > What is the purpose of this field default_nic = 0.
>>> >> >> >
>>> >> >> > vlan://500 in my case limits results only to the network
for this
>>> VR
>>> >> that
>>> >> >> > is having problems...
>>> >> >> >
>>> >> >> > Any suggestions ?
>>> >> >> >
>>> >> >> > "id" "uuid" "instance_id" "mac_address" "ip4_address"
"netmask"
>>> >> "gateway"
>>> >> >> > "ip_type" "broadcast_uri" "network_id" "mode" "state"
"strategy"
>>> >> >> > "reserver_name" "reservation_id" "device_id" "update_time"
>>> >> >> "isolation_uri"
>>> >> >> > "ip6_address" "default_nic" "vm_type" "created" "removed"
>>> >> "ip6_gateway"
>>> >> >> > "ip6_cidr" "secondary_ip" "display_nic"
>>> >> >> > "2816" "5066bc3adbec4789aa423b9eb8f50bb4" "1795"
>>> >> "06:70:0a:00:00:ac"
>>> >> >> > "46.232.180.101" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150204
>>> >> >> > 23:06:23" "vlan://500" \N "0" "User" "20150204 20:41:05"
>>> "20150204
>>> >> >> > 22:06:23" \N \N "0" "1"
>>> >> >> > "3132" "c8a5f98e566340e3ac031ac3545eaa83" "1958"
>>> >> "06:fc:c2:00:00:ad"
>>> >> >> > "46.232.180.102" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150303
>>> >> >> > 15:45:47" "vlan://500" \N "0" "User" "20150218 15:50:35"
>>> "20150303
>>> >> >> > 14:45:47" \N \N "0" "1"
>>> >> >> > "3139" "f5a4122922674615912863fbce69bb01" "1962"
>>> >> "06:d7:ac:00:00:ae"
>>> >> >> > "46.232.180.103" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150219
>>> >> >> > 03:10:45" "vlan://500" \N "0" "User" "20150219 00:09:02"
>>> "20150219
>>> >> >> > 02:10:45" \N \N "0" "1"
>>> >> >> > "707" "99afa70a39d546858fc09857fdc77c90" "511"
>>> "06:b5:72:00:00:72"
>>> >> >> > "46.232.180.144" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"0"
>>> "20140127
>>> >> >> > 14:38:52" "vlan://500" \N "0" "User" "20140127 11:29:08"
>>> "20140127
>>> >> >> > 13:38:52" \N \N "0" "1"
>>> >> >> > "1580" "bf56315eb4c3433888d93013ab2e2c37" "1088"
>>> >> "06:1d:90:00:00:72"
>>> >> >> > "46.232.180.144" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140723
>>> >> >> > 10:15:18" "vlan://500" \N "0" "User" "20140717 19:14:06"
>>> "20140723
>>> >> >> > 08:15:18" \N \N "0" "1"
>>> >> >> > "3799" "712cbcb6097f4555a73be8c2a5bd557f" "2306"
>>> >> "06:33:ac:00:00:77"
>>> >> >> > "46.232.180.149" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150316
>>> >> >> > 12:41:11" "vlan://500" \N "0" "User" "20150316 09:50:25"
>>> "20150316
>>> >> >> > 11:41:11" \N \N "0" "1"
>>> >> >> > "3817" "3599d1446cdc488b8c9d5837c7f612ac" "2311"
>>> >> "06:8a:ac:00:00:77"
>>> >> >> > "46.232.180.149" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150316
>>> >> >> > 13:02:59" "vlan://500" \N "0" "User" "20150316 11:49:31"
>>> "20150316
>>> >> >> > 12:02:59" \N \N "0" "1"
>>> >> >> > "1581" "47cfe113218c4a60a108584d64cd16ed" "1089"
>>> >> "06:c2:c4:00:00:7a"
>>> >> >> > "46.232.180.152" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140723
>>> >> >> > 10:16:12" "vlan://500" \N "0" "User" "20140717 19:14:43"
>>> "20140723
>>> >> >> > 08:16:12" \N \N "0" "1"
>>> >> >> > "1582" "dae4b3cfe2b24cbc960e77d2e854fffa" "1090"
>>> >> "06:1c:78:00:00:7c"
>>> >> >> > "46.232.180.154" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140723
>>> >> >> > 10:16:32" "vlan://500" \N "0" "User" "20140717 19:30:44"
>>> "20140723
>>> >> >> > 08:16:32" \N \N "0" "1"
>>> >> >> > "435" "5c3703952b704c8cb710eab4151b14ab" "252"
>>> "06:96:4e:00:00:8e"
>>> >> >> > "46.232.180.172" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140113
>>> >> >> > 23:25:44" "vlan://500" \N "0" "User" "20131024 23:16:11"
>>> "20140113
>>> >> >> > 22:25:44" \N \N "0" "1"
>>> >> >> > "2820" "feee7c33c72341e38583bcbfc4e257b1" "1797"
>>> >> "06:be:24:00:00:8e"
>>> >> >> > "46.232.180.172" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Reserved" "Create" "DirectNetworkGuru" \N "1"
"20150204
>>> >> >> 22:54:29"
>>> >> >> > "vlan://500" \N "0" "User" "20150204 21:54:29" \N \N
\N "0" "1"
>>> >> >> > "1813" "df725af812ed4c27b52151d1d465326d" "1213"
>>> >> "06:cd:d6:00:00:97"
>>> >> >> > "46.232.180.181" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140902
>>> >> >> > 11:06:56" "vlan://500" \N "0" "User" "20140902 09:03:11"
>>> "20140902
>>> >> >> > 09:06:56" \N \N "0" "1"
>>> >> >> > "2897" "aab5d282e9d54c4f91c9bfae88f404d6" "1304"
>>> >> "06:6e:0c:00:00:9c"
>>> >> >> > "46.232.180.186" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Reserved" "Create" "DirectNetworkGuru" \N "0"
"20150211
>>> >> >> 14:32:00"
>>> >> >> > "vlan://500" \N "0" "User" "20150211 13:31:59" \N \N
\N "0" "1"
>>> >> >> > "2235" "30865e2e083e4e8abccfc24bf403dece" "1488"
>>> >> "06:b8:b4:00:00:a1"
>>> >> >> > "46.232.180.191" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20141202
>>> >> >> > 14:58:11" "vlan://500" \N "0" "User" "20141202 13:31:08"
>>> "20141202
>>> >> >> > 13:58:11" \N \N "0" "1"
>>> >> >> > "2642" "233d03e4360f4bbe8b9c882468bc9c7b" "1706"
>>> >> "06:f8:36:00:00:a7"
>>> >> >> > "46.232.180.197" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150121
>>> >> >> > 19:46:10" "vlan://500" \N "0" "User" "20150121 17:27:13"
>>> "20150121
>>> >> >> > 18:46:10" \N \N "0" "1"
>>> >> >> > "1631" "54ee2677c502489dbdd244e7d4937020" "1102"
>>> >> "06:ac:4e:00:00:54"
>>> >> >> > "46.232.180.205" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140723
>>> >> >> > 12:33:59" "vlan://500" \N "0" "User" "20140723 09:47:24"
>>> "20140723
>>> >> >> > 10:33:59" \N \N "0" "1"
>>> >> >> > "1634" "db10636e458a40b287892bb1778ff50a" "1108"
>>> >> "06:46:d8:00:00:54"
>>> >> >> > "46.232.180.205" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20140723
>>> >> >> > 16:54:11" "vlan://500" \N "0" "User" "20140723 10:41:03"
>>> "20140723
>>> >> >> > 14:54:11" \N \N "0" "1"
>>> >> >> > "204" "8bd10db8cb454e438d0a9319be5b29be" "102"
>>> "06:7c:54:00:00:35"
>>> >> >> > "46.232.180.222" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Allocated" "Create" "DirectNetworkGuru" \N "2"
"20150316
>>> >> >> 12:25:41"
>>> >> >> > "vlan://500" \N "0" "User" "20130308 14:54:59" \N \N
\N "0" "1"
>>> >> >> > "3814" "4267a18629084fbe9ca4dbc654c0d37c" "2312"
>>> >> "06:c9:e0:00:00:3a"
>>> >> >> > "46.232.180.227" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20150316
>>> >> >> > 13:03:42" "vlan://500" \N "0" "User" "20150316 11:46:38"
>>> "20150316
>>> >> >> > 12:03:42" \N \N "0" "1"
>>> >> >> > "29" "35f48fcb722f49f59a6d584f92cb197b" "14"
>>> "06:b1:30:00:00:2a"
>>> >> >> > "46.232.180.241" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "206"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20130111
>>> >> >> > 02:11:18" "vlan://500" \N "0" "User" "20130111 01:06:41"
>>> "20130111
>>> >> >> > 01:11:18" \N \N "0" "1"
>>> >> >> > "25" "674ded1ff70545cca538611aa2b1ea48" "12"
>>> "06:12:88:00:00:2b"
>>> >> >> > "46.232.180.242" "255.255.255.0" "46.232.180.1" "Ip4"
"vlan://500"
>>> >> "206"
>>> >> >> > "Dhcp" "Deallocating" "Create" "DirectNetworkGuru" \N
"1"
>>> "20130111
>>> >> >> > 01:35:20" "vlan://500" \N "0" "User" "20130111 00:28:40"
>>> "20130111
>>> >> >> > 00:35:20" \N \N "0" "1"
>>> >> >> > "2953" "51002a530500473285db111804ac5f40" "1871"
>>> >> "06:02:a8:00:00:e2"
>>> >> >> > "46.232.180.39" "255.255.255.0" "46.232.180.1" "Ip4" "vlan://500"
>>> >> "212"
>>> >> >> > "Dhcp" "Reserved" "Create" "DirectNetworkGuru" \N "1"
"20150212
>>> >> >> 14:16:23"
>>> >> >> > "vlan://500" \N "0" "User" "20150212 13:16:20" \N \N
\N "0" "1"
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > On 16 March 2015 at 16:11, Marcus <shadowsor@gmail.com>
wrote:
>>> >> >> >
>>> >> >> >> FWIW, if your 4.3.2 is the same as what's in the source
tree for
>>> the
>>> >> >> >> router code, the null pointer indicates that there's
no default
>>> nic
>>> >> >> >> for one of your guests "TechveeFileServer". I'd guess
that if
>>> you
>>> >> >> >> delete/move just that host you may be able to start
the router,
>>> or at
>>> >> >> >> least get past this. You can also look into the db
and see if
>>> you can
>>> >> >> >> find its nics in the cloud.nics table and see if there
is in
>>> fact one
>>> >> >> >> marked default.
>>> >> >> >>
>>> >> >> >> On Mon, Mar 16, 2015 at 8:05 AM, Marcus <shadowsor@gmail.com>
>>> wrote:
>>> >> >> >> > Looks like the issue is that null pointer in
CreateDhcpEntry
>>> for
>>> >> >> >> > either "TechveeFileServer" or the DHCP entry
immediately after
>>> >> that.
>>> >> >> >> > It would suggest some inconsistent/unexpected
data when
>>> creating a
>>> >> >> >> > DHCP entry for one of the guests serviced by
this router. It's
>>> too
>>> >> bad
>>> >> >> >> > that one bad entry is fatal for the whole router.
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> > On Mon, Mar 16, 2015 at 7:16 AM, Andrija Panic
<
>>> >> >> andrija.panic@gmail.com>
>>> >> >> >> wrote:
>>> >> >> >> >> Not really  we are painfully migrating stopped
VMs, from VPS
>>> >> network
>>> >> >> >> >> (Guest Shared netwotk) to VPCs...
>>> >> >> >> >>
>>> >> >> >> >> MGMT server sends the STOP command to agent,
even though the
>>> VM
>>> >> was
>>> >> >> >> never
>>> >> >> >> >> started, BUT the storage provisioning from
template to volume
>>> is
>>> >> >> done...
>>> >> >> >> >>
>>> >> >> >> >> We are also looking into some external help
as we speak...
>>> >> >> >> >>
>>> >> >> >> >> On 16 March 2015 at 14:52, Nux! <nux@li.nux.ro>
wrote:
>>> >> >> >> >>
>>> >> >> >> >>> Hi,
>>> >> >> >> >>>
>>> >> >> >> >>> Have you managed to get to the bottom
of this?
>>> >> >> >> >>>
>>> >> >> >> >>> 
>>> >> >> >> >>> Sent from the Delta quadrant using Borg
technology!
>>> >> >> >> >>>
>>> >> >> >> >>> Nux!
>>> >> >> >> >>> www.nux.ro
>>> >> >> >> >>>
>>> >> >> >> >>>  Original Message 
>>> >> >> >> >>> > From: "Andrija Panic" <andrija.panic@gmail.com>
>>> >> >> >> >>> > To: users@cloudstack.apache.org,
dev@cloudstack.apache.org
>>> >> >> >> >>> > Sent: Sunday, 15 March, 2015 16:19:07
>>> >> >> >> >>> > Subject: [URGENT  HELP NEEDED]
>>> >> >> >> >>>
>>> >> >> >> >>> > Hi guys,
>>> >> >> >> >>> >
>>> >> >> >> >>> > we have updated the cloudstack from
4.3.0 to 4.3.2 (OS
>>> updated
>>> >> >> right
>>> >> >> >> >>> before
>>> >> >> >> >>> > that, from CentOS 6.5 to CentOS
6.6)
>>> >> >> >> >>> >
>>> >> >> >> >>> > And now I can not start SYSTEM VR
 that is used for SHARED
>>> >> GUEST
>>> >> >> >> network
>>> >> >> >> >>> > anymore.
>>> >> >> >> >>> > And some VMs are down  and cant
be started because they
>>> >> depend on
>>> >> >> >> this
>>> >> >> >> >>> > VR...
>>> >> >> >> >>> >
>>> >> >> >> >>> > VPC VRs are created fine, so new
VR for VPC are created
>>> fine,
>>> >> but
>>> >> >> >> this
>>> >> >> >> >>> one
>>> >> >> >> >>> > fro Guest network fails to start:
>>> >> >> >> >>> >
>>> >> >> >> >>> > Here you can see, after agent copies
template from
>>> secondary
>>> >> >> >> storage, to
>>> >> >> >> >>> > primary local storage, it created
base image, and backing
>>> file
>>> >> 
>>> >> >> so
>>> >> >> >> >>> storage
>>> >> >> >> >>> > setup seems completed.
>>> >> >> >> >>> >
>>> >> >> >> >>> > Than all out of sudden we have errors:
>>> >> >> >> >>>
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >> 
>>> >> >> >> >>
>>> >> >> >> >> Andrija Panić
>>> >> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > 
>>> >> >> >
>>> >> >> > Andrija Panić
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > 
>>> >> >
>>> >> > Andrija Panić
>>> >>
>>> >
>>> >
>>> >
>>> > 
>>> >
>>> > Andrija Panić
>>>
>>
>>
>>
>> 
>>
>> Andrija Panić
>>
>
>
>
> 
>
> Andrija Panić
