Re: Unable to locate datastore with id

Thanks, The next problem seems to be now, that there was an original snapshot that is no longer there. When I try to snapshot the volume I’m working on, it fails, because it’s looking for an initial snapshot that the database says is still there, but which was actually removed when I removed

Re: Unable to locate datastore with id

Do not remove (delete), to remove you can mark the flags. First set the removed date flag and then the state as Destroyed. On Thu, Aug 24, 2017 at 1:10 PM, Asai wrote: > I the DB table snapshot_store_ref I see two snapshots listed with store_id > 3. Can I safely

Re: Unable to locate datastore with id

I the DB table snapshot_store_ref I see two snapshots listed with store_id 3. Can I safely remove those rows? Asai Network and Systems Administrator GLOBAL CHANGE MEDIA office: 520.398.2542 http://globalchange.media Tucson, AZ > On Aug 24, 2017, at 1:06 PM, Asai

Re: Unable to locate datastore with id

I can see now that id 3 refers to a primary storage that I had to remove a while ago. It’s still in the DB, though, and seems to be causing the error. What steps should I take to remove this reference completely from the DB? Asai > On Aug 24, 2017, at 11:20 AM, Gabriel Beims Bräscher

Re: Unable to locate datastore with id

Just adding to Rafael's comment. Constant database backup is also a great idea. 2017-08-24 15:19 GMT-03:00 Rafael Weingärtner : > I would suggest you taking quite a lot of care before executing anything in > the database. > Please, do not hesitate to ask for further

Re: Unable to locate datastore with id

I would suggest you taking quite a lot of care before executing anything in the database. Please, do not hesitate to ask for further assistance here. On Thu, Aug 24, 2017 at 2:15 PM, Asai wrote: > Thank you very much for the assistance. I will try that. > Asai > >

Re: Unable to locate datastore with id

Thank you very much for the assistance. I will try that. Asai > On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner > wrote: > > Yes, quite easily. > I do not know if your problem is the same (you need a human not paying much > attention to cause this type of

Re: Different Time/Timezone on ACS node and hypervisors

I am not sure if different time zones would be the cause of your snapshot issues. Can you please provide us with more details and, if possible, some logs related to your problem? Thanks. 2017-08-14 3:05 GMT-03:00 Makrand : > Hey All, > > Is there any possible problem or

RE: Failed to find db.properties

Yes I do. Thank you  Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Rodrigo Baldasso [mailto:rodr...@loophost.com.br] Sent: 24 August 2017 18:25 To:

RE: Failed to find db.properties

As Rodrigo says, I should say that the CloudStack community doesn't support the mgmt. server running on Debian in that the packaging has not been designed to take the Debian OS into account, and we don't run any testing on Debian mgmt. servers. While someone in the community might know how to

Re: Failed to find db.properties

I think that by 'we', he meant 'cloudstack'. http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.9/overview/index.html#minimum-system-requirements []'s. - - - - - - - - - - - - - - - - - - - Rodrigo Baldasso - LHOST (51) 9 8419-9861 - - - - - - - - - - - - - - - - - - -

Re: Failed to find db.properties

end of story? no one can help me? On Thu, Aug 24, 2017 at 8:15 PM, Paul Angus wrote: > Ah. > > We don't support a Debian based management server - the Debian repo works > for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet). > For CentOS the current

RE: Failed to find db.properties

Ah. We don't support a Debian based management server - the Debian repo works for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet). For CentOS the current latest is 7.3 Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London

Re: Failed to find db.properties

Debian 8.9 the service is called tomcat7 in debian - not tomcat On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus wrote: > Hi Jevgeni, > > What OS are you running your management server on? (sorry if it's buried > in your post somewhere). > The log suggest that tomcat7

Re: Failed to find db.properties

how something can be wrong? I am installing to virgin clean Debian 8.9 machine using these repository http://packages.shapeblue.com/cloudstack/upstream/debian/4.10/ and the guide found on cloudstack website. The only thing, I did - was installation of Java8 On Thu, Aug 24, 2017 at 8:05 PM,

RE: Failed to find db.properties

Hi Jevgeni, What OS are you running your management server on? (sorry if it's buried in your post somewhere). The log suggest that tomcat7 isn't installed, or isn't where CloudStack is expecting it to be. Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos

Re: Failed to find db.properties

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 wrote: > sorry. this log file is correct > > DEBUG:root:execute:/usr/bin/lsb_release -i > DEBUG:root:execute:hostname -f >

Re: Failed to find db.properties

sorry. this log file is correct DEBUG:root:execute:/usr/bin/lsb_release -i DEBUG:root:execute:hostname -f DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080 DEBUG:root:Failed to execute: DEBUG:root:execute:ufw allow 8080/tcp DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250

Re: Failed to find db.properties

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

Did you send the log file? I think it is not possible to send attachments through this mailing list. On Thu, Aug 24, 2017 at 12:39 PM, Jevgeni Zolotarjov wrote: > I guess, this management setup log file explains the root of evil. > There are many errors, though setup

Re: Failed to find db.properties

I guess, this management setup log file explains the root of evil. There are many errors, though setup reports everything is OK. On Thu, Aug 24, 2017 at 4:12 PM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > db.properties is there. > Can you post your log files somewhere? > > On

Re: Failed to find db.properties

db.properties is there. Can you post your log files somewhere? On Thu, Aug 24, 2017 at 8:51 AM, Jevgeni Zolotarjov wrote: > This is what I have in > /etc/cloudstack/ > /etc/cloudstack/management/ > > root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd >

SystemVMs in Alert State | 4.7.1 release

Dear Team, Has anyone gone through this, i.e. system VMs agent state never come up until n unless you ping the management server IP from system VM. If you don’t ping the same and when you run the “ssvm_check.sh” script it shows not connectivity to port 8250. The time you ping the management

Re: Failed to find db.properties

This is what I have in /etc/cloudstack/ /etc/cloudstack/management/ root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd /etc/cloudstack/ root@servername:/etc/cloudstack# ls -al total 20 drwxr-xr-x 5 root root 4096 Aug 23 16:31 . drwxr-xr-x 100 root root 4096 Aug 23 19:26 ..

Re: Failed to find db.properties

Is there a db.properties in /etc/cloudstack.. folder? On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov wrote: > Did that "setup --tomcat7" now. > Output: > Starting to configure CloudStack Management Server: > Configure Firewall ...[OK] > Configure

Re: Failed to find db.properties

Did that "setup --tomcat7" now. Output: Starting to configure CloudStack Management Server: Configure Firewall ...[OK] Configure CloudStack Management Server ...[OK] CloudStack Management Server setup is Done! But no difference, when I try to run client application. Absolutely the same