Re: Failed to find db.properties

2017-08-23 Thread Jevgeni Zolotarjov
Yes, I did, as it is suggested in the guide: cloudstack-setup-database then setup-management On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <rafaelweingart...@gmail.com> wrote: did you run cloudstack-setup-database and ...setup-management? On Wed, Aug 23, 2017 at 11:16 AM, Je

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
; > On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > > > Did that "setup --tomcat7" now. > > Output: > > Starting to configure CloudStack Management Server: > > Configure Firewall ...[OK] > &

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
es somewhere? > > On Thu, Aug 24, 2017 at 8:51 AM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > > > This is what I have in > > /etc/cloudstack/ > > /etc/cloudstack/management/ > > > > root@servername:/var/cache/tomcat7/Catalina/localhost/client#

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory validateFile WARNING: Problem with directory [/usr/share/tomcat7/common/classes], exists: [false], isDirectory: [false], canRead: [false] Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory validateFile

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
or CentOS the current latest is 7.3 > > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > It seems that there is something wrong with your installation. Maybe a > corrupted file? > > On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > &g

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
> > > -Original Message- > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] > Sent: 24 August 2017 18:06 > To: users@cloudstack.apache.org > Subject: Re: Failed to find db.properties > > It seems that there is something wrong with your installation. Maybe a > corrupte

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
Management Server. DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management start On Thu, Aug 24, 2017 at 8:02 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com> wrote: > Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory > validateFile > WARNING: Problem with

Re: Failed to find db.properties

2017-08-24 Thread Jevgeni Zolotarjov
/17 9:23 AM, Rafael Weingärtner wrote: > > did you run setup-management --tomcat7? > > > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com > >> wrote: > > > >> Yes, I did, as it is suggested in the guide: > >>

Re: Failed to find db.properties

2017-08-23 Thread Jevgeni Zolotarjov
some log files (catalina.log, management-server.log > and others that might be useful)? > > > 2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov <j.zolotar...@gmail.com>: > > > Hi > > > > I am installing Cloudstack 4.10 on Debian Jessie using guides from > >

Failed to find db.properties

2017-08-23 Thread Jevgeni Zolotarjov
Hi I am installing Cloudstack 4.10 on Debian Jessie using guides from http://cloudstack-installation.readthedocs.io/en/latest/management-server/index.html Apparently the installation process was smooth. But I cannot get client running on tomcat7 >From catalina.out log file I can read Failed to

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
.overprovisioning.factor – but keep in mind > overprovisioning is a science in itself – which has lots of gotcha’s > depending on your workload. > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 20/10/2017, 11:16, "Jevgeni Zolotarjov" <j.zolotar.

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
single anti-affinity > group, don't you? This is how it should really work if you do that thing. > Anti-affinity groups are meaningless if you don't have several hosts. > > 2017-10-20 16:19 GMT+07:00 Jevgeni Zolotarjov <j.zolotar...@gmail.com>: > > > I could successfully c

Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
I could successfully create and run an instance with prepared Compute offering. But when I try to add one more instance of the same Compute offering, I am getting an error. Unable to create a deployment for VM There are plenty of resources on host: cores, RAM, storage. Pleas help

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
if you don't have several hosts. > > 2017-10-20 16:19 GMT+07:00 Jevgeni Zolotarjov <j.zolotar...@gmail.com>: > > > I could successfully create and run an instance with prepared Compute > > offering. But when I try to add one more instance of the same Compute > > of

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
, because you're close to thresholds. > > 2017-10-20 16:40 GMT+07:00 Jevgeni Zolotarjov <j.zolotar...@gmail.com>: > > > Hi, > > > > Yes I have one host. But I have exactly zero affinity groups. I could > > successfully add few instances and they are runn

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
sev...@bw-sw.com > wrote: > Just look for threshold. Logs don't include such information. > > 2017-10-20 16:56 GMT+07:00 Jevgeni Zolotarjov <j.zolotar...@gmail.com>: > > > What is exact parameter name? > > > > On Fri, Oct 20, 2017 at 12:44 PM, Ivan

Re: Unable to create a deployment for VM

2017-10-20 Thread Jevgeni Zolotarjov
0 | d4b9d32e-d779-48b8-814d-d7847d55a684 | 0 | >0| 19 | zonenamehere | > +--+--+- > ++--+-----------+ > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 20/10/2017, 13:33, "Jevgeni Zolotarjov" <j.zol

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
that process went wrong. > > On Fri, Feb 9, 2018 at 10:44 AM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > > > I have a backup and noone is accessing the installation during upgrade > > process > > > > Now: > > I moved 1 bit fu

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
ror: failed to get domain '8' error: Domain not found: no domain with matching name '8' And yes, cloudstack and mysql - everything locally On Fri, Feb 9, 2018 at 5:15 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > On Fri, Feb 9, 2018 at 3:58 PM, Jevgeni Zolotarjov <j.zolot

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
on. > > > > You get to these through the infrastructure tab in the UI. > > > > > > > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > >

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
ll look at your log in the meantime > > > Kind regards, > > Paul Angus > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
> paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] > Sent: 09 February 2018 16:34 > To: users@cloudstack

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
g locally, right? > So my next step would be to stop cloudstack and see if you can start the > image with virsh? > Cloudstack thinks for some reason the host is not a suitable target. I have > no clue why that is from your log. You can start cloudstack in a debugger > but given

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
Hoogland <daan.hoogl...@gmail.com> wrote: > so try > # virsh list --all > > On Fri, Feb 9, 2018 at 4:27 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com > > > wrote: > > > I guess, these are system VMs. > > none of my own created instances can start. &g

cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
cloudstack-management fails to start after upgrade from 4.10 to 4.11 management-server.log: 2018-02-09 07:49:50,842 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Running upgrade Upgrade41000to41100 to upgrade from 4.10.0.0-4.11.0.0 to 4.11.0.0 2018-02-09 07:49:50,846 DEBUG

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
is installation > with UI or API, when you roll back? > > On Fri, Feb 9, 2018 at 10:15 AM, Ernie Janse van Rensburg < > ernie.jvrensb...@shapeblue.com> wrote: > > > engine/schema/resources/META-INF/db/schema-41000to41100.sql: > > > > ___

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
the 4.11 > upgrade process again. > > > Regards > > > Ernie > > > From: Jevgeni Zolotarjov <j.zolotar...@gmail.com> > Sent: Friday, February 9, 2018 10:10:59 AM > To: users@cloudstack.apache.org > Subject: cloudstack-management fails to

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
; at > > com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java: > 108) > > at > > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5. > > runInContext(AsyncJobManagerImpl.java:581) > > at > > org.apache.c

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
Yes, its KVM On Fri, Feb 9, 2018 at 4:06 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > I am at a loss but really would like to help you. > is it a KVM with the management server running locally? > > On Fri, Feb 9, 2018 at 3:02 PM, Jevgeni Zolotarjov <j.zolotar...@

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
previous version 4.10 - and it was correct. I want to decide myself if I want to allow cpu overprovisioning. I consider this a critical bug. On Fri, Feb 9, 2018 at 11:51 AM, Jevgeni Zolotarjov <j.zolotar...@gmail.com> wrote: > my host in Centos7. I upgraded just by changing the URL in re

Re: cloudstack-management fails to start after upgrade 4.10 -> 4.11

2018-02-09 Thread Jevgeni Zolotarjov
) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... 18 more On Fri, Feb 9, 2018 at 3:05 PM, Jevgeni Zolotarjov <j.zolotar...@gmail.com> wrote: > OK, I pushed through and got management server running. > The steps I made: > * recovered DB from backup > * downgraded eve

4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

2018-07-20 Thread Jevgeni Zolotarjov
I updated cloudstack 4.11.0 -> 4.11.1 Everything went OK during update, but after host reboot guest VMs lost connection after few minutes of normal work. I tried restarting network - systemctl restart network.service then connection was restored again for few minutes Finally I could restore

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

2018-07-20 Thread Jevgeni Zolotarjov
or on the host, or > maybe on the guest? and the restart network? > > > On Fri, Jul 20, 2018 at 7:43 AM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > > > I updated cloudstack 4.11.0 -> 4.11.1 > > > > Everything went OK during update, but after

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

2018-07-20 Thread Jevgeni Zolotarjov
20, 2018 at 1:33 AM Jevgeni Zolotarjov > > wrote: > > > - an ip-address conflict. > > JZ: unlikely, but not impossible. I tried to restart router VM in > > Network-Guest networks -> defaultGuestNetwork -> VirtualAppliances > > While rebooting ping to this ro

Re: 4.11.0 -> 4.11.1 problem: Guest VMs losing connection after few minutes

2018-07-20 Thread Jevgeni Zolotarjov
t side manually. It will be registered as USER only in > that case. > > -- > Makrand > > > On Fri, Jul 20, 2018 at 5:41 PM, Jevgeni Zolotarjov < > j.zolotar...@gmail.com> > wrote: > > > Eventually I fixed the problem, without clear understanding of

Re: Is there a way to get back destroyed Virtual Router?

2018-07-11 Thread Jevgeni Zolotarjov
> > > boris.stoya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > On 11 Jul 2018, at 10:10, Jevgeni Zolotarjov > wrote: > > > > I am running cloudstacl 4.11.1 > > Virtual Router VM got destroyed unintentionally. > > > > Is there a way to re-create it? > > > > Regards, > > Jevgeni > >

Is there a way to get back destroyed Virtual Router?

2018-07-11 Thread Jevgeni Zolotarjov
I am running cloudstacl 4.11.1 Virtual Router VM got destroyed unintentionally. Is there a way to re-create it? Regards, Jevgeni

Re: Is there a way to get back destroyed Virtual Router?

2018-07-11 Thread Jevgeni Zolotarjov
’ll need to dig in the management logs to see whats wrong. > > Bobby > > > boris.stoya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > On 11 Jul 2018, at 10:18, Jevgeni Zolotarjov > wrote: &

qemu update 1.5.3 -> newer?

2018-09-12 Thread Jevgeni Zolotarjov
Hi Our cloudstack 4.11.1 installation works with qemu-kvm 1.5.3, which is shipped with standard Centos7. Anyone has a guide about safe way to upgrade to a newer version of qemu? Best regards, Jevgeni

Re: Unable to communicate to instances on new host - iptables?

2018-09-19 Thread Jevgeni Zolotarjov
e IPV6INIT=no IPV6_AUTOCONF=no DELAY=5 STP=yes On Wed, Sep 19, 2018 at 5:27 PM Jevgeni Zolotarjov wrote: > Hi Simon, > > I am not using advanced network. > > Here is my network configuration > ifcfg-bond0: > TYPE=Bond > BONDING_MASTER=yes > BONDING_OPTS="mode=802.3ad miimon

Re: Unable to communicate to instances on new host - iptables?

2018-09-19 Thread Jevgeni Zolotarjov
are you using on your hosts? If advanced, what > type of isolation? > > > - Si > > ________ > From: Jevgeni Zolotarjov > Sent: Wednesday, September 19, 2018 3:17 AM > To: users@cloudstack.apache.org > Subject: Unable to communicate to instances o

Re: Unable to communicate to instances on new host - iptables?

2018-09-19 Thread Jevgeni Zolotarjov
ler wrote: > Can you provide your iptables rules on your hosts? > > > > > From: Jevgeni Zolotarjov > Sent: Wednesday, September 19, 2018 9:29 AM > To: users@cloudstack.apache.org > Subject: Re: Unable to communicate to instances on new host

Re: ***UNCHECKED*** Re: Unable to communicate to instances on new host - iptables?

2018-09-24 Thread Jevgeni Zolotarjov
_______ > From: Jevgeni Zolotarjov > Sent: Wednesday, September 19, 2018 9:34 AM > To: users@cloudstack.apache.org > Subject: Re: Unable to communicate to instances on new host - iptables? > > sure > > iptables: > *mangle > :PREROUTING ACCEPT [4215:32894293] > :INPUT

Re: qemu update 1.5.3 -> newer?

2018-09-13 Thread Jevgeni Zolotarjov
ved to > it due to better ceph performance and lower latencies. Before moving > all your servers test them for performance an stability. On Wed, Sep > 12, 2018 at 3:23 PM Jevgeni Zolotarjov wrote: > > > > Doesn't look to be active. The page has zero information about my > que

Unable to migrate instance to new host

2018-09-18 Thread Jevgeni Zolotarjov
We were running cloudstack 4.11.1 with 1 host. Now we added another identical host. The procedure completed successfully. But the attempt to migrate instance to this new host fails with error message: Migration was refused connection to destination: qemu+tcp://A.B.C.D/system. Please check

Re: Unable to migrate instance to new host

2018-09-18 Thread Jevgeni Zolotarjov
w month ago and we had to > modify the libvirt-bin.service as well. > > 'ExecStart=/usr/sbin/libvirtd $libvirtd_opts' >> > 'ExecStart=/usr/sbin/libvirtd -l $libvirtd_opts' > > Add the "-l" before $libvirtd_opts > > Best regards, > N.B > >

Re: Unable to migrate instance to new host

2018-09-18 Thread Jevgeni Zolotarjov
, then the network is available, IP address is correct and IP addresses in LAN are accessible from these instances. What is still missing? Help appreciated. On Tue, Sep 18, 2018 at 11:46 PM Jevgeni Zolotarjov wrote: > My host is running on Centos7. > > tried to set "LIBVIRTD_ARGS=-l"

Re: qemu update 1.5.3 -> newer?

2018-09-12 Thread Jevgeni Zolotarjov
t here > https://wiki.centos.org/SpecialInterestGroup/Virtualization. > On Wed, Sep 12, 2018 at 10:17 AM Jevgeni Zolotarjov > wrote: > > > > Hi > > > > Our cloudstack 4.11.1 installation works with qemu-kvm 1.5.3, which is > > shipped with standard Centos7. >

Unable to communicate to instances on new host - iptables?

2018-09-19 Thread Jevgeni Zolotarjov
Hello! We are running CS 4.11.1 on CentOS7 (latest) Previously the installation had just 1 KVM host. Now we added another identical host. After some configuration hassle with libvirtd, new host is up and running. I followed strictly the host installation guide for 4.11. But instances running on

cannot start system VMs: disaster after maintenance followup

2019-03-21 Thread Jevgeni Zolotarjov
I reinstalled cloudstack from scratch - everything But looks like I hit the same wall now In the last step of installation it cannot create system VMs. service libvirtd status -l gives me ● libvirtd.service - Virtualization daemon Loaded: loaded

Re: cannot start system VMs: disaster after maintenance followup

2019-03-25 Thread Jevgeni Zolotarjov
- but > this is all down to security groups so check these are in place and working. > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > > On 21/03/2019, 19:47, "Jevgeni Zolotarjov" > wrote: > > << Almost, but not complete

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
, since there are VMs in that network) > > I'm not 100% positive this will fix your issue, but doesn't hurt to try > > If above doesn't work - I would still take a look into agents and if they > are still connected - optionally, restart agents on both hosts once more > and confirm

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
9024 > > > > On 3/19/19, 2:19 PM, "Jevgeni Zolotarjov" wrote: > > Hello > > I did exactly like you suggested. > > After UPDATE on db, I can see the router in cloudstack console. > But attempt to restart network fails. > I get err

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
anagement > server log and agent log again. > > > > > On 3/19/19, 2:56 PM, "Jevgeni Zolotarjov" wrote: > > >>>Network offering needs to be change to non-redundant > How do I do that? > > On Tue, Mar 19, 2019 at 11:

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
Yes. Just a single network. On Tue, 19 Mar 2019, 21:39 Andrija Panic, wrote: > Just one more clarification - this is Isolate single network (not Shared > Network, not VPC) ? > > > > On Tue, Mar 19, 2019, 19:36 Jevgeni Zolotarjov > wrote: > > > Name defaultGue

Re: Disaster after maintenance

2019-03-20 Thread Jevgeni Zolotarjov
error is only > > thrown when there is no router associated with your network. Usually > > management server restart tries to implement network again. Please > restart > > management server, save and share management server log. > > > > > > > > > > On

Re: Disaster after maintenance

2019-03-20 Thread Jevgeni Zolotarjov
n access/mount both Primary and > Secondary Storage > > On Wed, 20 Mar 2019 at 13:15, Jevgeni Zolotarjov > wrote: > > > After dozen of attempts, the Virtual Router could finally be recreated. > But > > its in eternal Starting status, and console prompts it required upg

Re: Disaster after maintenance

2019-03-20 Thread Jevgeni Zolotarjov
; > > > > select * from vm_instance where id=87; > > > > select id,name from vm_instance where name like 'r%' and removed is > > null; > > > > > > > > Basically since the network offering is not redundant this error is > > only

How to reimport instances from failed cluster

2019-03-20 Thread Jevgeni Zolotarjov
I've come across a problem with cluster, which I cannot manage to resolved. There is long thread about the problem with failed defaultGuestNetwork Now: What I am going to do: * download all VM volumes * reinstall Cloudstack from scratch * upload volumes to new VMs. How can that be done

Re: Disaster after maintenance

2019-03-20 Thread Jevgeni Zolotarjov
2019-03-20 14:38:09,227 DEBUG [c.c.d.FirstFitPlanner] > (Work-Job-Executor-96:ctx-04c5c9f2 job-5120/job-6960 ctx-fde3d4d7) > (logid:49483c7a) No clusters found having a host with enough capacity, > returning. > > Andrija > > On Wed, 20 Mar 2019 at 16:39, Jevgeni Zolotarjov >

Re: Disaster after maintenance

2019-03-20 Thread Jevgeni Zolotarjov
cloudstack from scratch? On Wed, Mar 20, 2019 at 11:08 AM Jevgeni Zolotarjov wrote: > Under this defaultGuestNetwork, I go to Virtual Appliances. There is no > VMS - "no data to show" > > I dont have any network, other than this single default one. > > I've tried adding new

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
ast one > ever created - if so we can find it easily... > > > > On Tue, Mar 19, 2019, 18:40 Jevgeni Zolotarjov > wrote: > > > Here is management server log > > https://drive.google.com/open?id=1H2jI0roeiWxtzReB8qV6QxDkNpaki99A > > > > > > On Tue,

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
2019, 19:27 Jevgeni Zolotarjov > wrote: > > > >>> 1. Confirm please rolling restart is set to false please - double > check > > Double checked - It is set to false > > > > >>>>2. If so - do you know the name of VR which you deleted ? Is it

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
irt has started ok. Do you have some NUMA > constraints or anything which requires particular RAM configuration? > > paul.an...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > -Original Message- >

Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
We have Cloudstack 4.11.2 setup running fine for few months (>4) The setup is very simple: 2 hosts We decided to do a maintenance to increase RAM on both servers For this we put first server to maintenance. All VMS moved to second host after a while. Then first server was shutdown, RAM

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
t? > > Also: > What is the hypervisor version? > Host status in ACS? > Did you try to force a VM to start/deploy in this server where you changed > the RAM? > > > On Tue, Mar 19, 2019 at 9:39 AM Jevgeni Zolotarjov > > wrote: > > > We have Cloudstack 4.11.2 setup running f

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
Guys, please help with it. What can be done here? There is too much valuable data. On Tue, Mar 19, 2019 at 4:21 PM Jevgeni Zolotarjov wrote: > Tried that just now and got error: > Resource [DataCenter:1] is unreachable: Can't find all necessary running > routers! > > I

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
e s look: > https://github.com/apache/cloudstack-documentation/pull/27/files > > вт, 19 мар. 2019 г., 9:09 Jevgeni Zolotarjov : > > > That's it - libvirtd failed to start on second host. > > Tried restarting, but it does not start. > > > > > > >> Do you ha

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
; Andrija > > andrija.pa...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > -Original Message- > From: Jevgeni Zolotarjov > Sent: 19 March 2019 15:10 > To: users@cloudstack

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
fd4dc job-5090) (logid:c734edfc) Complete async job-5090, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed to delete network"} ==

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
t start it and see if it > >> > connects. > >> > > >> > If it’s running but still not connected please share the agent.log. > >> > > >> > If nothing helps at all you can remove the host and add it again, but > >> > let’s try to trou

Re: Disaster after maintenance

2019-03-19 Thread Jevgeni Zolotarjov
, but > let’s try to troubleshoot first. > > Bobby. > > > boris.stoya...@shapeblue.com > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > On 19 Mar 2019, at 17:29, Jevgeni Zolotarjov > wrote: > > >

Re: cannot start system VMs: disaster after maintenance followup

2019-03-21 Thread Jevgeni Zolotarjov
> > On Thu, 21 Mar 2019 at 13:06, Jevgeni Zolotarjov > wrote: > > > I reinstalled cloudstack from scratch - everything > > > > But looks like I hit the same wall now > > > > In the last step of installation it cannot create

Re: cannot start system VMs: disaster after maintenance followup

2019-03-21 Thread Jevgeni Zolotarjov
gt; > any production-like system) > > > > Please let me know if the guide above gives you problem - we had multiple > > users explicitly following it - and successfully installed (with some > minor > > modification, which we committed back to that guide). >

Re: cannot start system VMs: disaster after maintenance followup

2019-03-21 Thread Jevgeni Zolotarjov
is to flatten their images > with > > "qemu-img convert", next import them as templates and recreate VMs from > > those templates. > > > > чт, 21 мар. 2019 г. в 13:05, Jevgeni Zolotarjov >: > > > > > What happened in the end was: qemu-kvm got u

Re: cannot start system VMs: disaster after maintenance followup

2019-03-21 Thread Jevgeni Zolotarjov
<< wrote: > Stick to 4.11.2 - 4.12 should be released withing few days officially. > > As for qemu-kvm-ev - yes, it's supposed to work - make sure to test new > versions obviously. > > Did you got your new installation running fine ? > > On Thu, 21 Mar 2019 at 19:2

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
a 4.11.3 template to carry on the > template. > > Thanks, > Bobby. > > On 4.07.19, 9:10, "Jevgeni Zolotarjov" wrote: > > Hello > > I followed installation steps as described here > > http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upg

Re: failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
ble. And then > restart the management server. Then retry the systemvmtemplate (4.11.3) > registration and upgrade to the available packages (as mentioned, we're yet > to fix the notes and links). > > > Regards, > > Rohit Yadav > > Software Architect, ShapeBlue > > http

Re: "Command failed due to Internal Server Error" when stopping a VM

2019-07-16 Thread Jevgeni Zolotarjov
+1 Have experienced exactly the same problem. My host is centos7. Would be interested to get the solution. On Tue, 16 Jul 2019, 23:57 daniel bellido, wrote: > Hello, > > I've done a fresh install of cloudstack 4.11.3 on 2 ubuntu 18.04 servers > (1 server hosts the management server , the other

Re: unable to start management server after update 4.11.3 -> 4.13

2019-09-29 Thread Jevgeni Zolotarjov
est_os if I remember the name from top of my head...), you > might also want to remove those together with guest_os related entries... > > Ping here if any problems. > > Andrija > > > On Sun, 29 Sep 2019, 16:11 Jevgeni Zolotarjov, > wrote: > > > I was running clean

unable to start management server after update 4.11.3 -> 4.13

2019-09-29 Thread Jevgeni Zolotarjov
I was running clean installation of 4.11.3 Now after updating to 4.13 cloudstack-management does not start exception from management-server.log 2019-09-29 14:05:57,058 WARN [o.a.c.s.m.c.ResourceApplicationContext] (main:null) (logid:) Exception encountered during context initialization -

failure after update 4.11.2 -> 4.11.3

2019-07-04 Thread Jevgeni Zolotarjov
Hello I followed installation steps as described here http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.11.htm I made sure, that system VM templates were in READY state. But after update management server does not start ● cloudstack-management.service - CloudStack

Re: Cloudstack manager - Unable to login after restart

2020-04-08 Thread Jevgeni Zolotarjov
t; > On Wed, 8 Apr 2020 at 10:08, Jevgeni Zolotarjov > wrote: > > > After restart of host machine (Centos 7.7) I am not able to login > anymore. > > Neither cloudstack starts any VMs. > > > > In the log I see following error right after login > > >

Cloudstack manager - Unable to login after restart

2020-04-08 Thread Jevgeni Zolotarjov
After restart of host machine (Centos 7.7) I am not able to login anymore. Neither cloudstack starts any VMs. In the log I see following error right after login 2020-04-08 08:05:49,979 DEBUG [c.c.u.AccountManagerImpl] (qtp504527234-22:ctx-22182f59) (logid:ba27e53e) User: admin in domain 1 has