RE: ACS 4.9.2 with VMware 5.5

2017-03-15 Thread Ciobanu Cristian
Thank you very much!!! I figured out how to fix, I forgot to add VLAN.


Regards,
Cristian

-Original Message-
From: Sergey Levitskiy [mailto:sergey.levits...@autodesk.com] 
Sent: Wednesday, March 15, 2017 7:39 PM
To: users@cloudstack.apache.org
Subject: Re: ACS 4.9.2 with VMware 5.5

The  root cause is below which is most likely due to not specifying VLAN range 
during zone creation. 
Can you post result for the following DB queries?

select * from cloud.networsk where id=218; select * from cloud.vlan where 
network_id=218; select count(*) from cloud.user_ip_address where vlan_db_id in 
(select id from cloud.vlan where network_id=218) and state=’Free’
select id,name,data_center_id, vnet from cloud.physical_network


2017-03-15 10:41:25,855 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-48:ctx-9013c76a job-140/job-142 ctx-213d798a) 
(logid:918eb10d) Cleaning up because we're unable to implement the network 
Ntwk[218|Guest|11]

2017-03-15 10:41:25,881 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-48:ctx-9013c76a job-140/job-142 ctx-213d798a) 
(logid:918eb10d) Insufficient capacity
com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to 
allocate vnet as a part of network Ntwk[218|Guest|11] implement Scope=interface 
com.cloud.dc.DataCenter; id=3
at 
com.cloud.network.guru.GuestNetworkGuru.allocateVnet(GuestNetworkGuru.java:289)
at 
com.cloud.network.guru.GuestNetworkGuru.implement(GuestNetworkGuru.java:319)
at 
com.cloud.network.guru.ExternalGuestNetworkGuru.implement(ExternalGuestNetworkGuru.java:132)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1011)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:950)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1314)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:997)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4605)
at sun.reflect.GeneratedMethodAccessor302.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)








On 3/15/17, 9:08 AM, "Ciobanu Cristian"  wrote:

Hello ,

   Please see : 
https://drive.google.com/file/d/0B2xyGcnD30FVcFZZa1FvTmZtRWc/view?usp=sharing I 
suggest to check on the last part of this log.


Thank you
 Cristian

-Original Message-
From: Sergey Levitskiy [mailto:sergey.levits...@autodesk.com] 
Sent: Wednesday, March 15, 2017 5:35 PM
To: users@cloudstack.apache.org
Subject: Re: ACS 4.9.2 with VMware 5.5

Can you extract full test of exception for management server logs and post 
here? Ideally please save the full management log on e.g. dropbox and add the 
link as well.

On 3/15/17, 8:21 AM, "Ciobanu Cristian"  wrote:

Hello,

 

 Today I have did another test, but now with VMware 5.5  and ACS 
4.9.2
configured with advanced networking, everything looks ok, except I'm not
able to deploy any VM.

 

SSVM - OK

Proxy Console - OK

VPC - OK

Tier - OK

Templates ready - OK

 

Deploy instance - NOT OK

 

  I also have 2 environments  with ACS 4.5.2 and VMware 5.5 configured 
with
basic and advanced networking everything works perfectly there.

 

 

  Can I get confirmation if anyone tested ACS 4.9.2 with VMware 5.5 ? 

 

 Logs related to this issue - http://pastebin.com/tM6ZBfDp

===

[root@acs management]# grep -r i-2-20-VM --color

apilog.log:2017-03-15 10:41:28,423 INFO  [a.c.c.a.ApiServer]
(catalina-exec-18:ctx-7ec54fca ctx-250a55aa) (logid:76a929db) (userId=2
accountId=2 sessionId=051314C1FA5E08E86DC0373970EE42D9) 86.125.237.148 
--
GET

command=listVirtualMachines=b7cbfcea-f13e-4954-b1e1-f7d067f64293
=json&_=148956710 200

{"listvirtualmachinesresponse":{"count":1,"virtualmachine":[{"id":"b7cbfcea-

f13e-4954-b1e1-f7d067f64293","name":"VM-b7cbfcea-f13e-4954-b1e1-f7d067f64293

","displayname":"VM-b7cbfcea-f13e-4954-b1e1-f7d067f64293","account":"admin",

"userid":"46a435ea-095d-11e7-811f-000c2929469d","username":"admin","domainid


Re: SystemVM can't start

2017-03-15 Thread Rafael Weingärtner
The answer is in my previous email, last line:

> You can check if there is something wrong in state.db by passing the
> contents of it in an XML validator. There will probably be some broken XML
> tags there.
>

Last time I faced this problem, I put the host in maintenance, powered off
or migrate host's VMs, then I opened the file with an XML validator, found
the entries that were corrupted and removed them. Then  I replaced the old
state.db file with this modified file. Afterward, reboot the server and
everything should be ok.

No need to tell you to do a backup of things, check hypervisors
community…., right?
http://discussions.citrix.com/topic/241761-help-power-failed-now-xapi-will-not-start/



On Wed, Mar 15, 2017 at 2:05 PM, Fabiano A. Souza 
wrote:

> Very thanks Rafael. I was already imagining that this would be the
> problem. Do you know any way to fix this problem in XenServer?
>
> By your experience do you believe that recreating the pool in XenServer
> will correct this problem?
>
> Again thanks so much for your help.
>
> ---
> FABIANO A. SOUZA
> _Assistência e Consultoria em TI_
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br
>
> Em 15/03/2017 14:36, Rafael Weingärtner escreveu:
>
> > Looking at the log from your XenServer, and as I said before the problem
> is
> > not in ACS.
> >
> > This kind of log entries:
> >
> > Db_exn.DBCache_NotFound("missing row", "VBD",
> >
> >> "OpaqueRef:e1136dfc-cdbc-ba21-3eb8-94838cc75030")
> >
> > or
> >
> >> D:424e469aca54 failed with exception Db_exn.DBCache_NotFound("missing
> >> row", "task",
> >
> > indicate a problem in the hypervisor metadata. In your case, XenServer
> uses
> > a file called state.db. This file contains metadata in XML format.
> Probably
> > your force reboot corrupted some entries there (I have already had
> similar
> > problems before). You can check if there is something wrong in state.db
> by
> > passing the contents of it in a XML validator. There will probably be
> some
> > broken XML tags there.
> >
> > On Wed, Mar 15, 2017 at 12:15 PM, Fabiano A. Souza <
> f.so...@fdsouza.com.br>
> > wrote:
> >
> >> Yes. I set up the DataCenter with the Advanced Network configuration.
> >>
> >> I'm attaching XenServer file log detailed sample.
> >>
> >> Thank you so much for your help.
> >> ---
> >>
> >> *Fabiano A. Souza*
> >> *Assistência e Consultoria em TI*
> >> f.so...@fdsouza.com.br
> >> http://www.fdsouza.com.br
> >>
> >> Em 15/03/2017 12:52, Rafael Weingärtner escreveu:
> >>
> >> I am not sure if this is a complete destroy and if ACS re-uses something
> >> from the old VMs.
> >>
> >> From your logs,
> >>
> >> VIF.unplug
> >> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
> >>
> >> This probably happened because when the VM was being created and the VIF
> >> was not created in the hypervisor. There are probably other error log
> >> entries before this one. From your other log:
> >>
> >> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> >>
> >> It is clear that there is something wrong in your XenServer. If you
> want us
> >> to help you, you need to provide a more log entries (not scattered
> bits).
> >> Also, in the XenServer logs, there will be plenty of exceptions there
> >> regarding this problem.
> >> You said that user VMs are working. I am guessing you have an advanced
> >> networking set up. Maybe the Guest network was not affected, but the
> >> Management or Storage network configuration in the XenServer may be
> >> affected by some misconfiguration/corruption that happened during the
> >> force-reboot.
> >>
> >> On Wed, Mar 15, 2017 at 11:42 AM, Fabiano A. Souza
>  >>
> >> The ACS is trying to do this itself.
> >>
> >> ACS create, trying start, after error stop and destroy the systemvms
> >> instance. The instance name or ID is being incremented at each attempt
> >> to create these instances (s-300-VM, s-301-VM...).
> >>
> >> ---
> >> FABIANO A. SOUZA
> >> _Assistência e Consultoria em TI_
> >> f.so...@fdsouza.com.br
> >> http://www.fdsouza.com.br
> >>
> >> Em 15/03/2017 12:27, Rafael Weingärtner escreveu:
> >>
> >> You said you forced a reboot. It looks like something got corrupted in
> >>
> >> your
> >>
> >> host.
> >>
> >> I would not do some drastic measure like destroying pool.
> >>
> >> Have you tried to destroy the system VMs and then let ACS re-create
> them?
> >>
> >> On Wed, Mar 15, 2017 at 11:23 AM, Fabiano A. Souza <
> >>
> >> f.so...@fdsouza.com.br>
> >>
> >> wrote:
> >>
> >> Hi Rafael
> >>
> >> I have some other Guest (Windows/Linux) include VRs that works normally.
> >> Only systemvms has problem to deploy. I use one pool with two XenServer
> >> 7 host. In xenresource.log I see this error below.
> >>
> >> Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
> 

Re: SystemVM can't start

2017-03-15 Thread Fabiano A. Souza
Very thanks Rafael. I was already imagining that this would be the
problem. Do you know any way to fix this problem in XenServer? 

By your experience do you believe that recreating the pool in XenServer
will correct this problem? 

Again thanks so much for your help.

---
FABIANO A. SOUZA
_Assistência e Consultoria em TI_
f.so...@fdsouza.com.br
http://www.fdsouza.com.br 

Em 15/03/2017 14:36, Rafael Weingärtner escreveu:

> Looking at the log from your XenServer, and as I said before the problem is
> not in ACS.
> 
> This kind of log entries:
> 
> Db_exn.DBCache_NotFound("missing row", "VBD", 
> 
>> "OpaqueRef:e1136dfc-cdbc-ba21-3eb8-94838cc75030")
> 
> or
> 
>> D:424e469aca54 failed with exception Db_exn.DBCache_NotFound("missing
>> row", "task",
> 
> indicate a problem in the hypervisor metadata. In your case, XenServer uses
> a file called state.db. This file contains metadata in XML format. Probably
> your force reboot corrupted some entries there (I have already had similar
> problems before). You can check if there is something wrong in state.db by
> passing the contents of it in a XML validator. There will probably be some
> broken XML tags there.
> 
> On Wed, Mar 15, 2017 at 12:15 PM, Fabiano A. Souza 
> wrote:
> 
>> Yes. I set up the DataCenter with the Advanced Network configuration.
>> 
>> I'm attaching XenServer file log detailed sample.
>> 
>> Thank you so much for your help.
>> ---
>> 
>> *Fabiano A. Souza*
>> *Assistência e Consultoria em TI*
>> f.so...@fdsouza.com.br
>> http://www.fdsouza.com.br
>> 
>> Em 15/03/2017 12:52, Rafael Weingärtner escreveu:
>> 
>> I am not sure if this is a complete destroy and if ACS re-uses something
>> from the old VMs.
>> 
>> From your logs,
>> 
>> VIF.unplug
>> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
>> 
>> This probably happened because when the VM was being created and the VIF
>> was not created in the hypervisor. There are probably other error log
>> entries before this one. From your other log:
>> 
>> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
>> 
>> It is clear that there is something wrong in your XenServer. If you want us
>> to help you, you need to provide a more log entries (not scattered bits).
>> Also, in the XenServer logs, there will be plenty of exceptions there
>> regarding this problem.
>> You said that user VMs are working. I am guessing you have an advanced
>> networking set up. Maybe the Guest network was not affected, but the
>> Management or Storage network configuration in the XenServer may be
>> affected by some misconfiguration/corruption that happened during the
>> force-reboot.
>> 
>> On Wed, Mar 15, 2017 at 11:42 AM, Fabiano A. Souza 
>> > 
>> The ACS is trying to do this itself.
>> 
>> ACS create, trying start, after error stop and destroy the systemvms
>> instance. The instance name or ID is being incremented at each attempt
>> to create these instances (s-300-VM, s-301-VM...).
>> 
>> ---
>> FABIANO A. SOUZA
>> _Assistência e Consultoria em TI_
>> f.so...@fdsouza.com.br
>> http://www.fdsouza.com.br
>> 
>> Em 15/03/2017 12:27, Rafael Weingärtner escreveu:
>> 
>> You said you forced a reboot. It looks like something got corrupted in
>> 
>> your
>> 
>> host.
>> 
>> I would not do some drastic measure like destroying pool.
>> 
>> Have you tried to destroy the system VMs and then let ACS re-create them?
>> 
>> On Wed, Mar 15, 2017 at 11:23 AM, Fabiano A. Souza <
>> 
>> f.so...@fdsouza.com.br>
>> 
>> wrote:
>> 
>> Hi Rafael
>> 
>> I have some other Guest (Windows/Linux) include VRs that works normally.
>> Only systemvms has problem to deploy. I use one pool with two XenServer
>> 7 host. In xenresource.log I see this error below.
>> 
>> Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
>> :::80|dispatch:VIF.unplug D:6cce7f031461|backtrace] VIF.unplug
>> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
>> row", "VIF", "OpaqueRef:20e49fbf-5c92-ef21-805b-13b1997e326e")
>> 
>> Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
>> :::80|dispatch:VIF.unplug D:b37f4fd2de0c|backtrace] VIF.unplug
>> R:fcca316e07d3 failed with exception Db_exn.DBCache_NotFound("missing
>> row", "VIF", "OpaqueRef:4d7c3a36-982a-825e-e71f-8978108ec56b")
>> 
>> I'm thinking remove the hosts from CloudStack and destroy pool. Create
>> again the pool and re-attach them again on CloudStack configuration. Do
>> you believe that can I have problem to start the guests instance after
>> that?
>> 
>> ---
>> FABIANO A. SOUZA
>> _Assistência e Consultoria em TI_
>> f.so...@fdsouza.com.br
>> http://www.fdsouza.com.br
>> 
>> Em 15/03/2017 11:28, Rafael Weingärtner escreveu:
>> 
>> This is not an Apache CloudStack (ACS) problem per se.
>> "HOST_CANNOT_ATTACH_NETWOR"
>> Something is wrong with your hosts. Are all of the networks of yours
>> 
>> hosts working? is everything in place as ACS expects?
>> 
>> On Wed, Mar 15, 2017 at 10:26 AM, 

Re: Not able to setup source-nat for a regular router yet

2017-03-15 Thread Gabriel Beims Bräscher
As far as I know, the log exists for a long time. However, I am not 
aware of potential issues.


Hope that someone can share his/her wisdom on this one.


Cheers, Gabriel.


Em 15/03/2017 13:10, Jeff Hair escreveu:

It's coming from the config scripts on the routers, yes. This is version
4.9.2.0 (it's a fork, but should be similar enough to vanilla). I'm not
necessarily noticing problems with it. Connectivity from public IPs on
Isolated networks seem to be working. I'm just wondering what this message
means, and if it can cause problems.

Jeff

On Wed, Mar 15, 2017 at 4:07 PM, Gabriel Beims Bräscher <
gabr...@autonomiccs.com.br> wrote:


Hi Jeff,

Could you please provide more details (e.g. CloudStack version, CloudStack
management log)?
Seems that the log came from [1]. I will check on it.

[1] https://github.com/apache/cloudstack/blob/master/systemvm/
patches/debian/config/opt/cloud/bin/cs/CsAddress.py

Cheers,
Gabriel.


Em 15/03/2017 07:21, Jeff Hair escreveu:


Hi,

I'm seeing this message in the logs when detaching IPs with
disableStaticNat. This is on a network without redundant routers. What
exactly dose "Not able to setup source-nat for a regular router yet" mean?
Does this cause functionality problems for non-redundant routers?

Jeff






VM Data and root VHD missing after storage migration

2017-03-15 Thread Tejas Sheth
Hi,

  We have xenserver 6.2 with cloudstack 4.3.1. We had initiated the data
disk migration from one primary storage to another. after the operation we
were not able to start the VM.

  when we checked the xenserver storage, we were not able to find the VHD
in any of the primary storage.

  Its a strange behavior i have seen first time, since the production data
is missing we need to identify the root cause of the same.

NOTE: Even Root disk is also not available in any of the storage hence we
are not able to power on the VM at all.

 we have checked database where metadata is available in database about the
root and data disk.

  following error captured when we start the vm with Data disk.
2017-03-09 11:49:26,964 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-203:ctx-ff911f73) Catch Exception: class
com.xensource.xenapi.Types$UuidInvalid due to The uuid you supplied was
invalid.

Thanks


Re: ACS 4.9.2 with VMware 5.5

2017-03-15 Thread Sergey Levitskiy
The  root cause is below which is most likely due to not specifying VLAN range 
during zone creation. 
Can you post result for the following DB queries?

select * from cloud.networsk where id=218;
select * from cloud.vlan where network_id=218;
select count(*) from cloud.user_ip_address where vlan_db_id in (select id from 
cloud.vlan where network_id=218) and state=’Free’
select id,name,data_center_id, vnet from cloud.physical_network


2017-03-15 10:41:25,855 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-48:ctx-9013c76a job-140/job-142 ctx-213d798a) 
(logid:918eb10d) Cleaning up because we're unable to implement the network 
Ntwk[218|Guest|11]

2017-03-15 10:41:25,881 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-48:ctx-9013c76a job-140/job-142 ctx-213d798a) 
(logid:918eb10d) Insufficient capacity 
com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to 
allocate vnet as a part of network Ntwk[218|Guest|11] implement Scope=interface 
com.cloud.dc.DataCenter; id=3
at 
com.cloud.network.guru.GuestNetworkGuru.allocateVnet(GuestNetworkGuru.java:289)
at 
com.cloud.network.guru.GuestNetworkGuru.implement(GuestNetworkGuru.java:319)
at 
com.cloud.network.guru.ExternalGuestNetworkGuru.implement(ExternalGuestNetworkGuru.java:132)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:1011)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:950)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1314)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:997)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4605)
at sun.reflect.GeneratedMethodAccessor302.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)








On 3/15/17, 9:08 AM, "Ciobanu Cristian"  wrote:

Hello ,

   Please see : 
https://drive.google.com/file/d/0B2xyGcnD30FVcFZZa1FvTmZtRWc/view?usp=sharing I 
suggest to check on the last part of this log.


Thank you
 Cristian

-Original Message-
From: Sergey Levitskiy [mailto:sergey.levits...@autodesk.com] 
Sent: Wednesday, March 15, 2017 5:35 PM
To: users@cloudstack.apache.org
Subject: Re: ACS 4.9.2 with VMware 5.5

Can you extract full test of exception for management server logs and post 
here? Ideally please save the full management log on e.g. dropbox and add the 
link as well.

On 3/15/17, 8:21 AM, "Ciobanu Cristian"  wrote:

Hello,

 

 Today I have did another test, but now with VMware 5.5  and ACS 
4.9.2
configured with advanced networking, everything looks ok, except I'm not
able to deploy any VM.

 

SSVM - OK

Proxy Console - OK

VPC - OK

Tier - OK

Templates ready - OK

 

Deploy instance - NOT OK

 

  I also have 2 environments  with ACS 4.5.2 and VMware 5.5 configured 
with
basic and advanced networking everything works perfectly there.

 

 

  Can I get confirmation if anyone tested ACS 4.9.2 with VMware 5.5 ? 

 

 Logs related to this issue - http://pastebin.com/tM6ZBfDp

===

[root@acs management]# grep -r i-2-20-VM --color

apilog.log:2017-03-15 10:41:28,423 INFO  [a.c.c.a.ApiServer]
(catalina-exec-18:ctx-7ec54fca ctx-250a55aa) (logid:76a929db) (userId=2
accountId=2 sessionId=051314C1FA5E08E86DC0373970EE42D9) 86.125.237.148 
--
GET

command=listVirtualMachines=b7cbfcea-f13e-4954-b1e1-f7d067f64293
=json&_=148956710 200

{"listvirtualmachinesresponse":{"count":1,"virtualmachine":[{"id":"b7cbfcea-

f13e-4954-b1e1-f7d067f64293","name":"VM-b7cbfcea-f13e-4954-b1e1-f7d067f64293

","displayname":"VM-b7cbfcea-f13e-4954-b1e1-f7d067f64293","account":"admin",

"userid":"46a435ea-095d-11e7-811f-000c2929469d","username":"admin","domainid

":"c932053e-095b-11e7-811f-000c2929469d","domain":"ROOT","created":"2017-03-

15T10:41:21-0400","state":"Error","haenable":false,"zoneid":"f6f15408-a1fe-4

edf-a376-ff94c6e07392","zonename":"AMS-NVME","templateid":"c9354528-095b-11e
7-811f-000c2929469d","templatename":"CentOS 5.3(64-bit) no GUI

Re: SystemVM can't start

2017-03-15 Thread Rafael Weingärtner
Looking at the log from your XenServer, and as I said before the problem is
not in ACS.

This kind of log entries:

Db_exn.DBCache_NotFound("missing row", "VBD",
> "OpaqueRef:e1136dfc-cdbc-ba21-3eb8-94838cc75030")
>

or

> D:424e469aca54 failed with exception Db_exn.DBCache_NotFound("missing
> row", "task",
>

indicate a problem in the hypervisor metadata. In your case, XenServer uses
a file called state.db. This file contains metadata in XML format. Probably
your force reboot corrupted some entries there (I have already had similar
problems before). You can check if there is something wrong in state.db by
passing the contents of it in a XML validator. There will probably be some
broken XML tags there.

On Wed, Mar 15, 2017 at 12:15 PM, Fabiano A. Souza 
wrote:

> Yes. I set up the DataCenter with the Advanced Network configuration.
>
> I'm attaching XenServer file log detailed sample.
>
> Thank you so much for your help.
> ---
>
> *Fabiano A. Souza*
> *Assistência e Consultoria em TI*
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br
>
>
> Em 15/03/2017 12:52, Rafael Weingärtner escreveu:
>
> I am not sure if this is a complete destroy and if ACS re-uses something
> from the old VMs.
>
> From your logs,
>
> VIF.unplug
> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
>
>
> This probably happened because when the VM was being created and the VIF
> was not created in the hypervisor. There are probably other error log
> entries before this one. From your other log:
>
> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
>
>
> It is clear that there is something wrong in your XenServer. If you want us
> to help you, you need to provide a more log entries (not scattered bits).
> Also, in the XenServer logs, there will be plenty of exceptions there
> regarding this problem.
> You said that user VMs are working. I am guessing you have an advanced
> networking set up. Maybe the Guest network was not affected, but the
> Management or Storage network configuration in the XenServer may be
> affected by some misconfiguration/corruption that happened during the
> force-reboot.
>
> On Wed, Mar 15, 2017 at 11:42 AM, Fabiano A. Souza  >
> wrote:
>
> The ACS is trying to do this itself.
>
> ACS create, trying start, after error stop and destroy the systemvms
> instance. The instance name or ID is being incremented at each attempt
> to create these instances (s-300-VM, s-301-VM...).
>
> ---
> FABIANO A. SOUZA
> _Assistência e Consultoria em TI_
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br
>
> Em 15/03/2017 12:27, Rafael Weingärtner escreveu:
>
> You said you forced a reboot. It looks like something got corrupted in
>
> your
>
> host.
>
> I would not do some drastic measure like destroying pool.
>
> Have you tried to destroy the system VMs and then let ACS re-create them?
>
> On Wed, Mar 15, 2017 at 11:23 AM, Fabiano A. Souza <
>
> f.so...@fdsouza.com.br>
>
> wrote:
>
> Hi Rafael
>
> I have some other Guest (Windows/Linux) include VRs that works normally.
> Only systemvms has problem to deploy. I use one pool with two XenServer
> 7 host. In xenresource.log I see this error below.
>
> Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
> :::80|dispatch:VIF.unplug D:6cce7f031461|backtrace] VIF.unplug
> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
> row", "VIF", "OpaqueRef:20e49fbf-5c92-ef21-805b-13b1997e326e")
>
> Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
> :::80|dispatch:VIF.unplug D:b37f4fd2de0c|backtrace] VIF.unplug
> R:fcca316e07d3 failed with exception Db_exn.DBCache_NotFound("missing
> row", "VIF", "OpaqueRef:4d7c3a36-982a-825e-e71f-8978108ec56b")
>
> I'm thinking remove the hosts from CloudStack and destroy pool. Create
> again the pool and re-attach them again on CloudStack configuration. Do
> you believe that can I have problem to start the guests instance after
> that?
>
> ---
> FABIANO A. SOUZA
> _Assistência e Consultoria em TI_
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br
>
> Em 15/03/2017 11:28, Rafael Weingärtner escreveu:
>
> This is not an Apache CloudStack (ACS) problem per se.
> "HOST_CANNOT_ATTACH_NETWOR"
> Something is wrong with your hosts. Are all of the networks of yours
>
> hosts working? is everything in place as ACS expects?
>
>
> On Wed, Mar 15, 2017 at 10:26 AM, Fabiano A. Souza <
>
> f.so...@fdsouza.com.br> wrote:
>
>
> After my host with XenServer 7 forced reboot the systemvms can't start
> anymore.
>
> Can you help me?
>
> 2017-03-14 09:42:10,724 WARN [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Task failed! Task
> record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Tue Mar 14 09:42:46 BRT 2017
> finished: Tue Mar 14 09:42:46 BRT 2017
> status: failure
> residentOn: com.xensource.xenapi.Host@4e05ddb9
> 

Re: Not able to setup source-nat for a regular router yet

2017-03-15 Thread Jeff Hair
It's coming from the config scripts on the routers, yes. This is version
4.9.2.0 (it's a fork, but should be similar enough to vanilla). I'm not
necessarily noticing problems with it. Connectivity from public IPs on
Isolated networks seem to be working. I'm just wondering what this message
means, and if it can cause problems.

Jeff

On Wed, Mar 15, 2017 at 4:07 PM, Gabriel Beims Bräscher <
gabr...@autonomiccs.com.br> wrote:

> Hi Jeff,
>
> Could you please provide more details (e.g. CloudStack version, CloudStack
> management log)?
> Seems that the log came from [1]. I will check on it.
>
> [1] https://github.com/apache/cloudstack/blob/master/systemvm/
> patches/debian/config/opt/cloud/bin/cs/CsAddress.py
>
> Cheers,
> Gabriel.
>
>
> Em 15/03/2017 07:21, Jeff Hair escreveu:
>
>> Hi,
>>
>> I'm seeing this message in the logs when detaching IPs with
>> disableStaticNat. This is on a network without redundant routers. What
>> exactly dose "Not able to setup source-nat for a regular router yet" mean?
>> Does this cause functionality problems for non-redundant routers?
>>
>> Jeff
>>
>>
>


Re: SystemVM can't start

2017-03-15 Thread Rafael Weingärtner
I am not sure if this is a complete destroy and if ACS re-uses something
from the old VMs.

>From your logs,

> VIF.unplug
> R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
>

This probably happened because when the VM was being created and the VIF
was not created in the hypervisor. There are probably other error log
entries before this one. From your other log:

errorInfo: [HOST_CANNOT_ATTACH_NETWORK,


It is clear that there is something wrong in your XenServer. If you want us
to help you, you need to provide a more log entries (not scattered bits).
Also, in the XenServer logs, there will be plenty of exceptions there
regarding this problem.
You said that user VMs are working. I am guessing you have an advanced
networking set up. Maybe the Guest network was not affected, but the
Management or Storage network configuration in the XenServer may be
affected by some misconfiguration/corruption that happened during the
force-reboot.

On Wed, Mar 15, 2017 at 11:42 AM, Fabiano A. Souza 
wrote:

> The ACS is trying to do this itself.
>
> ACS create, trying start, after error stop and destroy the systemvms
> instance. The instance name or ID is being incremented at each attempt
> to create these instances (s-300-VM, s-301-VM...).
>
> ---
> FABIANO A. SOUZA
> _Assistência e Consultoria em TI_
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br
>
> Em 15/03/2017 12:27, Rafael Weingärtner escreveu:
>
> > You said you forced a reboot. It looks like something got corrupted in
> your
> > host.
> >
> > I would not do some drastic measure like destroying pool.
> >
> > Have you tried to destroy the system VMs and then let ACS re-create them?
> >
> > On Wed, Mar 15, 2017 at 11:23 AM, Fabiano A. Souza <
> f.so...@fdsouza.com.br>
> > wrote:
> >
> > Hi Rafael
> >
> > I have some other Guest (Windows/Linux) include VRs that works normally.
> > Only systemvms has problem to deploy. I use one pool with two XenServer
> > 7 host. In xenresource.log I see this error below.
> >
> > Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
> > :::80|dispatch:VIF.unplug D:6cce7f031461|backtrace] VIF.unplug
> > R:68394c4e8e7c failed with exception Db_exn.DBCache_NotFound("missing
> > row", "VIF", "OpaqueRef:20e49fbf-5c92-ef21-805b-13b1997e326e")
> >
> > Mar 15 08:31:32 fl-mia-compute1 xapi: [error|fl-mia-compute1|605 INET
> > :::80|dispatch:VIF.unplug D:b37f4fd2de0c|backtrace] VIF.unplug
> > R:fcca316e07d3 failed with exception Db_exn.DBCache_NotFound("missing
> > row", "VIF", "OpaqueRef:4d7c3a36-982a-825e-e71f-8978108ec56b")
> >
> > I'm thinking remove the hosts from CloudStack and destroy pool. Create
> > again the pool and re-attach them again on CloudStack configuration. Do
> > you believe that can I have problem to start the guests instance after
> > that?
> >
> > ---
> > FABIANO A. SOUZA
> > _Assistência e Consultoria em TI_
> > f.so...@fdsouza.com.br
> > http://www.fdsouza.com.br
> >
> > Em 15/03/2017 11:28, Rafael Weingärtner escreveu:
> >
> > This is not an Apache CloudStack (ACS) problem per se.
> > "HOST_CANNOT_ATTACH_NETWOR"
> > Something is wrong with your hosts. Are all of the networks of yours
> hosts working? is everything in place as ACS expects?
> >
> > On Wed, Mar 15, 2017 at 10:26 AM, Fabiano A. Souza <
> f.so...@fdsouza.com.br> wrote:
> >
> > After my host with XenServer 7 forced reboot the systemvms can't start
> > anymore.
> >
> > Can you help me?
> >
> > 2017-03-14 09:42:10,724 WARN [c.c.h.x.r.CitrixResourceBase]
> > (DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Task failed! Task
> > record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> > nameLabel: Async.VM.start_on
> > nameDescription:
> > allowedOperations: []
> > currentOperations: {}
> > created: Tue Mar 14 09:42:46 BRT 2017
> > finished: Tue Mar 14 09:42:46 BRT 2017
> > status: failure
> > residentOn: com.xensource.xenapi.Host@4e05ddb9
> > progress: 1.0
> > type: 
> > result:
> > errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> > OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
> > OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
> > otherConfig: {}
> > subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> > subtasks: []
> >
> > 2017-03-14 09:42:10,730 WARN [c.c.h.x.r.CitrixResourceBase]
> > (DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Unable to start
> > VM(s-294-VM) on host(b8324267-2cbe-4aa9-9b26-215375cb5553) due to Task
> > failed! Task record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> > nameLabel: Async.VM.start_on
> > nameDescription:
> > allowedOperations: []
> > currentOperations: {}
> > created: Tue Mar 14 09:42:46 BRT 2017
> > finished: Tue Mar 14 09:42:46 BRT 2017
> > status: failure
> > residentOn: com.xensource.xenapi.Host@4e05ddb9
> > progress: 1.0
> > type: 
> > result:
> > errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> > OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
> > OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
> > otherConfig: {}
> > subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> > 

Re: SystemVM can't start

2017-03-15 Thread Rafael Weingärtner
This is not an Apache CloudStack (ACS) problem per se.
"HOST_CANNOT_ATTACH_NETWOR"
Something is wrong with your hosts. Are all of the networks of yours hosts
working? is everything in place as ACS expects?

On Wed, Mar 15, 2017 at 10:26 AM, Fabiano A. Souza 
wrote:

> After my host with XenServer 7 forced reboot the systemvms can't start
> anymore.
>
> Can you help me?
>
> 2017-03-14 09:42:10,724 WARN [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Task failed! Task
> record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Tue Mar 14 09:42:46 BRT 2017
> finished: Tue Mar 14 09:42:46 BRT 2017
> status: failure
> residentOn: com.xensource.xenapi.Host@4e05ddb9
> progress: 1.0
> type: 
> result:
> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
> OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
> otherConfig: {}
> subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
>
> 2017-03-14 09:42:10,730 WARN [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Unable to start
> VM(s-294-VM) on host(b8324267-2cbe-4aa9-9b26-215375cb5553) due to Task
> failed! Task record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Tue Mar 14 09:42:46 BRT 2017
> finished: Tue Mar 14 09:42:46 BRT 2017
> status: failure
> residentOn: com.xensource.xenapi.Host@4e05ddb9
> progress: 1.0
> type: 
> result:
> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
> OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
> otherConfig: {}
> subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
>
> Task failed! Task record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Tue Mar 14 09:42:46 BRT 2017
> finished: Tue Mar 14 09:42:46 BRT 2017
> status: failure
> residentOn: com.xensource.xenapi.Host@4e05ddb9
> progress: 1.0
> type: 
> result:
> errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
> OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
> OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
> otherConfig: {}
> subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
>
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.
> checkForSuccess(CitrixResourceBase.java:471)
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.startVM(
> CitrixResourceBase.java:4900)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
> CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:128)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.
> CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:53)
> at
> com.cloud.hypervisor.xenserver.resource.wrapper.
> xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
> at
> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(
> CitrixResourceBase.java:1687)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(
> DirectAgentAttache.java:315)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(
> ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(
> DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.
> runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(
> ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(
> ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> --
> FABIANO A. SOUZA
> _Assistência e Consultoria em TI_
> f.so...@fdsouza.com.br
> http://www.fdsouza.com.br




-- 
Rafael Weingärtner


SystemVM can't start

2017-03-15 Thread Fabiano A. Souza
After my host with XenServer 7 forced reboot the systemvms can't start
anymore.  

Can you help me? 

2017-03-14 09:42:10,724 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Task failed! Task
record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Tue Mar 14 09:42:46 BRT 2017
finished: Tue Mar 14 09:42:46 BRT 2017
status: failure
residentOn: com.xensource.xenapi.Host@4e05ddb9
progress: 1.0
type: 
result:
errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: [] 

2017-03-14 09:42:10,730 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-184:ctx-f12cdd04) (logid:4552cd9d) Unable to start
VM(s-294-VM) on host(b8324267-2cbe-4aa9-9b26-215375cb5553) due to Task
failed! Task record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Tue Mar 14 09:42:46 BRT 2017
finished: Tue Mar 14 09:42:46 BRT 2017
status: failure
residentOn: com.xensource.xenapi.Host@4e05ddb9
progress: 1.0
type: 
result:
errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: [] 

Task failed! Task record: uuid: 84f3483d-1021-22fb-be39-2eb15366e03e
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Tue Mar 14 09:42:46 BRT 2017
finished: Tue Mar 14 09:42:46 BRT 2017
status: failure
residentOn: com.xensource.xenapi.Host@4e05ddb9
progress: 1.0
type: 
result:
errorInfo: [HOST_CANNOT_ATTACH_NETWORK,
OpaqueRef:3269022e-9b3d-88ca-8fb1-b15f3948b3a9,
OpaqueRef:cd7b3c3e-92fd-18a3-eaa7-099aa066bb46]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: [] 

at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:471)
at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:4900)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:128)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:53)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1687)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

-- 
FABIANO A. SOUZA
_Assistência e Consultoria em TI_
f.so...@fdsouza.com.br
http://www.fdsouza.com.br

Re: NFS Secondary Staging Store

2017-03-15 Thread Erik Weber
If I recall correctly it is used as intermediate storage for S3 and Swift.

-- 
Erik

On Wed, Mar 15, 2017 at 2:42 PM, Gian Paolo Buono
 wrote:
> Hi all,
>
> sory but i m not clear what is Secondary staging store, can anyone
> explain me ?
>
> Thanks
> GPB


NFS Secondary Staging Store

2017-03-15 Thread Gian Paolo Buono
Hi all,

sory but i m not clear what is Secondary staging store, can anyone 
explain me ?

Thanks
GPB

Not able to setup source-nat for a regular router yet

2017-03-15 Thread Jeff Hair
Hi,

I'm seeing this message in the logs when detaching IPs with
disableStaticNat. This is on a network without redundant routers. What
exactly dose "Not able to setup source-nat for a regular router yet" mean?
Does this cause functionality problems for non-redundant routers?

Jeff


Re: Cloudstack Management IP address pool exhausted

2017-03-15 Thread kangkan mahanta
Hi Nitin,

Used
update op_dc_ip_address_alloc set
nic_id=NULL,reservation_id=NULL,taken=NULL where id=1;
and systemVM started working.

Do you have any idea to extend guest IP pool

Regards,
Kangkan Mahanta Kashyap




On Mon, Feb 6, 2017 at 10:46 PM, Nitin Kumar Maharana <
nitinkumar.mahar...@accelerite.com> wrote:

> Hi Kangkan,
>
> You can extend the IP address pool by using the updatePod API.
> In UI, if you try to edit any pod, it will have an option to edit the
> start IP and end IP of the pod.
> You can either forward extend the end IP or backward extend the start IP.
>
>
> Thanks,
> Nitin
> > On 06-Feb-2017, at 11:30 AM, kangkan mahanta 
> wrote:
> >
> > Hi,
> >
> > Please let me know what to do as management IP address pool exhausted and
> > system VM are stopped. Cloudstack version 4.4.3
> >
> > Thanking you
> > k
>
>
>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent Systems business. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Accelerite, a Persistent Systems business does not accept any
> liability for virus infected mails.
>


RE: ACS 4.9.2 KVM

2017-03-15 Thread Ciobanu Cristian
Hi Glenn,

   Is a new install and I'm able to connect through ssh from management to kvm 
host without any issue.  

I know is very strange, this is why a asked for help.


Thank you.
Cristian



-Original Message-
From: Glenn Wagner [mailto:glenn.wag...@shapeblue.com] 
Sent: Wednesday, March 15, 2017 8:01 AM
To: users@cloudstack.apache.org
Subject: RE: ACS 4.9.2 KVM

Hi Cristian,

Can you ssh and login to the kvm host from the management server , I do 
understand you can telnet port 22 but can you login Did you upgrade your 4.5.2 
to 4.9.2 or is it a new install?


Regards
Glenn


 
 

glenn.wag...@shapeblue.com 
www.shapeblue.com
First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape Town  
7129South Africa
@shapeblue
  
 


-Original Message-
From: Ciobanu Cristian [mailto:cristian.c@istream.today] 
Sent: Wednesday, 15 March 2017 1:15 AM
To: users@cloudstack.apache.org
Subject: RE: ACS 4.9.2 KVM

Hi,

 Everything looks ok from firewall side also from global settings, I have 
did this before trying to add the host.

  Maybe be related this to Management server ? I have installed on CentOS 7 
...

  I have did telnet test from both side, 22, 8250, 8080, no problems.


Thank you for your time guys!
Cristian

-Original Message-
From: Glenn Wagner [mailto:glenn.wag...@shapeblue.com] 
Sent: Tuesday, March 14, 2017 11:51 PM
To: users@cloudstack.apache.org
Subject: RE: ACS 4.9.2 KVM

Hi,

Have a look at the host setting in the Global setting in cloudstack, make sure 
it's the IP of the management server and not 127.0.0.1 or localhost.
If it is change it to the real IP and restart the management server , then try 
to re-add the host  into cloudstack



Regards

Glenn 


glenn.wag...@shapeblue.com
www.shapeblue.com
First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape Town  
7129South Africa @shapeblue
  
 


-Original Message-
From: Ciobanu Cristian [mailto:cristian.c@istream.today]
Sent: Tuesday, 14 March 2017 10:57 PM
To: users@cloudstack.apache.org
Subject: ACS 4.9.2 KVM

Hello,

 

It's very strange, I have configured before a ACS 4.5.2 with KVM and 
everything was fine, but right now I have problem adding HOST to ACS 4.9.2, 
please see the output:

 

Agent KVM : 

 

2017-03-14 16:23:26,043 WARN  [utils.nio.NioConnection] (main:null) (logid:) 
Unable to connect to remote: is there a server running on port 8250

2017-03-14 16:23:31,044 INFO  [utils.nio.NioClient] (main:null) (logid:) 
Connecting to localhost:8250

 

   I also verified agent.propertis  and I see only default config, is using 
localhost for the management server, I'm not sure why has not been updated when 
I have tried to add the host to the management.

 

First part from agent :

 

# Generate with "uuidgen"

guid=

 

#resource= the java class, which agent load to execute

resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource

 

#workers= number of threads running in agent

workers=5

 

#host= The IP address of management server

host=localhost

 

#port = The port management server listening on, default is 8250

port=8250

 

#cluster= The cluster which the agent belongs to

cluster=default

 

#pod= The pod which the agent belongs to

pod=default

 

#zone= The zone which the agent belongs to

zone=default

 

#public.network.device= the public nic device

# if this is commented, it is autodetected on service startup

# public.network.device=cloudbr0

 

#private.network.device= the private nic device

# if this is commented, it is autodetected on service startup

# private.network.device=cloudbr1

 

#guest.network.device= the guest nic device

# if this is commented, the private nic device will be used

 

 

 

Logs from management server :

 

==> management-server.log <==

2017-03-14 16:35:58,455 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-b3627ef8 ctx-5f9cca17) (logid:7850022c) ===END=== 
86.125.xxx.xxx -- GET 
command=updateConfiguration=system.vm.use.local.storage=true
id=d74686ee-8107-451e-add2-dadc28aceecc=json&_=1489523757572

2017-03-14 16:35:58,770 DEBUG [c.c.a.ApiServlet]
(catalina-exec-20:ctx-4d8315e6) (logid:bfcbddff) ===START=== 86.125..xxx -- 
POST  command=addHost=json

2017-03-14 16:35:58,782 WARN  [c.c.a.d.ParamGenericValidationWorker]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Received unknown 
parameters for command addHost. Unknown parameters : clustertype

2017-03-14 16:35:58,787 INFO  [c.c.r.ResourceManagerImpl]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Trying to add a 
new host at http://xx.net in data center 2

2017-03-14 16:35:58,931 WARN  [c.c.h.k.d.LibvirtServerDiscoverer]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff)  can't setup 
agent, due to java.io.IOException: There was a problem while connecting to
144.x17.xx.xx:22 - There was a problem while connecting to 144.x17.xx.xx:22

2017-03-14 16:35:58,931 WARN  

RE: ACS 4.9.2 KVM

2017-03-15 Thread Glenn Wagner
Hi Cristian,

Can you ssh and login to the kvm host from the management server , I do 
understand you can telnet port 22 but can you login 
Did you upgrade your 4.5.2 to 4.9.2 or is it a new install?


Regards
Glenn


 
 

glenn.wag...@shapeblue.com 
www.shapeblue.com
First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape Town  
7129South Africa
@shapeblue
  
 


-Original Message-
From: Ciobanu Cristian [mailto:cristian.c@istream.today] 
Sent: Wednesday, 15 March 2017 1:15 AM
To: users@cloudstack.apache.org
Subject: RE: ACS 4.9.2 KVM

Hi,

 Everything looks ok from firewall side also from global settings, I have 
did this before trying to add the host.

  Maybe be related this to Management server ? I have installed on CentOS 7 
...

  I have did telnet test from both side, 22, 8250, 8080, no problems.


Thank you for your time guys!
Cristian

-Original Message-
From: Glenn Wagner [mailto:glenn.wag...@shapeblue.com] 
Sent: Tuesday, March 14, 2017 11:51 PM
To: users@cloudstack.apache.org
Subject: RE: ACS 4.9.2 KVM

Hi,

Have a look at the host setting in the Global setting in cloudstack, make sure 
it's the IP of the management server and not 127.0.0.1 or localhost.
If it is change it to the real IP and restart the management server , then try 
to re-add the host  into cloudstack



Regards

Glenn 


glenn.wag...@shapeblue.com
www.shapeblue.com
First Floor, Victoria Centre, 7 Victoria Street, Somerset West, Cape Town  
7129South Africa @shapeblue
  
 


-Original Message-
From: Ciobanu Cristian [mailto:cristian.c@istream.today]
Sent: Tuesday, 14 March 2017 10:57 PM
To: users@cloudstack.apache.org
Subject: ACS 4.9.2 KVM

Hello,

 

It's very strange, I have configured before a ACS 4.5.2 with KVM and 
everything was fine, but right now I have problem adding HOST to ACS 4.9.2, 
please see the output:

 

Agent KVM : 

 

2017-03-14 16:23:26,043 WARN  [utils.nio.NioConnection] (main:null) (logid:) 
Unable to connect to remote: is there a server running on port 8250

2017-03-14 16:23:31,044 INFO  [utils.nio.NioClient] (main:null) (logid:) 
Connecting to localhost:8250

 

   I also verified agent.propertis  and I see only default config, is using 
localhost for the management server, I'm not sure why has not been updated when 
I have tried to add the host to the management.

 

First part from agent :

 

# Generate with "uuidgen"

guid=

 

#resource= the java class, which agent load to execute

resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource

 

#workers= number of threads running in agent

workers=5

 

#host= The IP address of management server

host=localhost

 

#port = The port management server listening on, default is 8250

port=8250

 

#cluster= The cluster which the agent belongs to

cluster=default

 

#pod= The pod which the agent belongs to

pod=default

 

#zone= The zone which the agent belongs to

zone=default

 

#public.network.device= the public nic device

# if this is commented, it is autodetected on service startup

# public.network.device=cloudbr0

 

#private.network.device= the private nic device

# if this is commented, it is autodetected on service startup

# private.network.device=cloudbr1

 

#guest.network.device= the guest nic device

# if this is commented, the private nic device will be used

 

 

 

Logs from management server :

 

==> management-server.log <==

2017-03-14 16:35:58,455 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-b3627ef8 ctx-5f9cca17) (logid:7850022c) ===END=== 
86.125.xxx.xxx -- GET 
command=updateConfiguration=system.vm.use.local.storage=true
id=d74686ee-8107-451e-add2-dadc28aceecc=json&_=1489523757572

2017-03-14 16:35:58,770 DEBUG [c.c.a.ApiServlet]
(catalina-exec-20:ctx-4d8315e6) (logid:bfcbddff) ===START=== 86.125..xxx -- 
POST  command=addHost=json

2017-03-14 16:35:58,782 WARN  [c.c.a.d.ParamGenericValidationWorker]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Received unknown 
parameters for command addHost. Unknown parameters : clustertype

2017-03-14 16:35:58,787 INFO  [c.c.r.ResourceManagerImpl]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Trying to add a 
new host at http://xx.net in data center 2

2017-03-14 16:35:58,931 WARN  [c.c.h.k.d.LibvirtServerDiscoverer]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff)  can't setup 
agent, due to java.io.IOException: There was a problem while connecting to
144.x17.xx.xx:22 - There was a problem while connecting to 144.x17.xx.xx:22

2017-03-14 16:35:58,931 WARN  [c.c.r.ResourceManagerImpl]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Unable to find 
the server resources at http://.net

2017-03-14 16:35:58,931 INFO  [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-20:ctx-4d8315e6 ctx-9fb24e22) (logid:bfcbddff) Could not find
exception: com.cloud.exception.DiscoveryException in error code list for 
exceptions

2017-03-14 16:35:58,931 WARN