Re: Where to look when your SSVM creation NPE's?

2018-10-18 Thread Boris Stoyanov
2018-10-18 06:20:26,076 INFO [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-70aba7ab) (logid:f3c51c51) Unable to start secondary storage vm for standby capacity, vm id : 346, will recycle it and start a new one 2018-10-18 06:20:26,095 INFO [o.a.c.s.PremiumSecondaryStorageManagerImpl]

Re: Where to look when your SSVM creation NPE's?

2018-10-18 Thread Jordan Michaels
Hi Si, Thanks so much for the follow-up! > Could you tell us a bit more about your setup? I've got a little lab setup, with a dedicated router, switch, and several 1U's that I can test with. Will eventually set up a little micro-environment with VLAN's and such but for now just trying to get t

Re: Where to look when your SSVM creation NPE's?

2018-10-18 Thread Andrija Panic
Can you please make sure that the Agent is up and running - check agent logs etc ? This has nothing to do with "SSVM cant talk to Secondary Storage" (actually this can be checked/tested with existing script from inside SSVM, once SSVM has been started) It might be capacity issue (though it's usual

Re: New SSVM wont start after upgrade from 4.9.3 to 4.11.2rc3

2018-10-18 Thread Rohit Yadav
Hi Jean-Francois, Did you upgrade your KVM agent and restart it as well? The systemvmtemplate seems find but it may be possible that an older systemvm.iso has patched the systemvm which is why you're seeing the error. - Rohit ___

New SSVM wont start after upgrade from 4.9.3 to 4.11.2rc3

2018-10-18 Thread Jean-Francois Nadeau
hi all, After upgrading from 4.9.3 to 4.11.2rc3 on centos7/KVM, the old SSMV were running and working fine until I destroyed them to get them on the current version (I uploaded the 4.11.2rc3 template before the upgrade) Now whatever I do there's nothing running on the new Console proxy VM Oct 1

Re: Where to look when your SSVM creation NPE's?

2018-10-18 Thread Simon Weller
Jordan, Could you tell us a bit more about your setup? Hypervisor Type? Network design (basic or advanced)? Primary storage type? CloudStack version? OS being used? - Si From: Jordan Michaels Sent: Thursday, October 18, 2018 2:26 PM To: users Subject: Where to

Where to look when your SSVM creation NPE's?

2018-10-18 Thread Jordan Michaels
Hi Folks, I've added a host to the CloudStack Management server but now I'm getting NPE's when the Management server tries to create the System VM's: 2018-10-18 06:20:26,052 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-40:ctx-ac017e0e job-1248/job-1621) (logid:b6f3dd96) Done exec

Re: Problems configuring KVM host

2018-10-18 Thread Alexandre Bruyere
Will definitely look into it - next step of the project IS to build a CentOS 7 Cloudstack setup, so I can take notes and submit them once it works. -Original Message- Re: Problems configuring KVM host From: Alexandre Bruyere To: To Adrija: You were spot-on. Your instructions allowed me

Re: Problems configuring KVM host

2018-10-18 Thread Andrija Panic
Sure, great you solved it! I will try my best to update that article - though you can do it also - fork, edit, create pull request - this is community stuff :) Cheers On Thu, Oct 18, 2018, 16:59 Alexandre Bruyere wrote: > To Adrija: > > You were spot-on. Your instructions allowed me to success

Re: Problems configuring KVM host

2018-10-18 Thread Alexandre Bruyere
To Adrija: You were spot-on. Your instructions allowed me to successfully add a host. For posterity's sake, here is the specific configuration I've done: Removed IP from eth0, added it to the cloudbr0 bridge Created cloudbr0 interface, configured it according to the "Network Example for Basic Ne

Re: Problems configuring KVM host

2018-10-18 Thread Alexandre Bruyere
To Simon: I would, but that command returns an error: -bash: syntax error near unexpected token `newline' As for the rest (I've trimmed the agent.properties to remove the big patches of comments): - agent.properties # Sample configuration file for CloudStack agent # The GUID to identify the

RE: [VOTE] Apache CloudStack 4.11.2.0 RC3

2018-10-18 Thread Paul Angus
Uggh cut and paste fail! Yes 26th October - end of next week. (I'm on annual leave next week). Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -Original Message- From: Rene Moser Sent: 18 October

Re: [VOTE] Apache CloudStack 4.11.2.0 RC3

2018-10-18 Thread Rene Moser
On 10/18/2018 12:54 PM, Paul Angus wrote: > The vote will be open until the middle of next week, 26th September 2018. s/September/October/ right?

RE: [VOTE] Apache CloudStack 4.11.2.0 RC3

2018-10-18 Thread Paul Angus
Hi All, The issues in RC2 have been fixed so we're ready to go with RC3 I've created a 4.11.2.0 release (RC3), with the following artefacts up for testing and a vote: Git Branch and Commit SH: https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/

Re: Cloudstack database and orphaned entities

2018-10-18 Thread Boris Stoyanov
well, with Xen I think you have a console where you can see and manage all running vms on the host and remove if it’s orphaned. Further I think maybe a new cloudstack zone/installation would sync this and recognize it as a guest vm and probably you’ll be able to see it in cloudstack UI even..

RE: Cloudstack database and orphaned entities

2018-10-18 Thread Yordan Kostov
Thank you for pointing this out Bobi, I will document the steps and open the ticket there. Btw forgot to mention - this is ACS 4.11.2 + XenServer. Best regards, Jordan -Original Message- From: Boris Stoyanov [mailto:boris.stoya...@shapeblue.com] Sent: Thursday, October 18, 2018 12:49 PM

Re: Cloudstack database and orphaned entities

2018-10-18 Thread Boris Stoyanov
Hi Yordan, I think the best approach would be to submit an issue in the GitHub page of ACS and document the exact steps on reproducing this issue. From there on someone could pick it up and fix it for the next LTS release. Honestly I don’t think that would be a common production problem, since

Cloudstack database and orphaned entities

2018-10-18 Thread Yordan Kostov
Dear all, While testing different setups and also deleting them I noticed that it is occasional/common occurrence that orphaned system VMs or hosts remain in the database. For example - during removal of a zone (system VMs, secondary storages, host, cluster, pod