Re: Secondary Storage

Luis, thanks for your feedback. Though waiting seem to resolve your issue, I'm sure that is not the intended deployment outcome. I've made some observations around the problem. - The system vms console/storage repeatedly rebuild and never come online. - The system vm template is downloaded to

ISO file snot uploading

Hi Group. I have this problems, now that the secondary storage is mounted witch I don't know how this happened after some errors but know that I am trying to upload some files I see this in the logs, any idea will be appreciated. I will continue researching 2020-05-04 15:54:57,090

Re: Secondary Storage

I had a similar problem, secondary storage not mounted by CS, I left the CS running for a couple of hours and not I see the secondary storage working, I am not sure if it has to download something before mounting it. On 5/4/2020 3:27 PM, Mr Jazze wrote: I've now tried 3 attempts to deploy CS

Secondary Storage

I've now tried 3 attempts to deploy CS with the following resources: Management Server also hosting NFS shares (primary & secondary) 2 x KVM Hosts running Ubuntu 16.04 CloudStack 4.13.1 Native Linux Bridge VXLAN Isolation I cannot get the console to show/recognize the secondary NFS storage which

Re: Removing Secondary Storage

There are two more tables: snapshot_store_ref & volume_store_ref Check if you've entries in these tables. With regards Thomas On Mon, 4 May 2020, 10:28 pm Fariborz Navidan, wrote: > Hello, > > I have two secondary storages. I want to remove one. I have moved all > template files to another and

Removing Secondary Storage

Hello, I have two secondary storages. I want to remove one. I have moved all template files to another and have changed references to another image store in template_store_ref. However, I still I get the message: "Cannot delete image store with active volumes backup!" Which table should I look

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Liridon, "Not owner of usage job, skipping" means there is a PID in the record for this job that isn't the current process. If recognise this and have remedied by setting the process id to null in the record. I'm sure there is some underlying issue that you hit though. Just a workaround. On Mon,

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Rohit I tried so and did configure the usage to run 12:45 so I can monitor the behavior. I got the following output: 2020-05-04 12:45:00,002 INFO [cloud.usage.UsageManagerImpl] (Usage-Job-1:null) (logid:) starting usage job... 2020-05-04 12:45:00,015 DEBUG [cloud.usage.UsageManagerImpl]

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Thanks for testing and sharing your results Liridon! Can you also test the case if the usage records have the correct time according to configured timezone (in global settings) if you're using a non-UTC timezone? I'll add the db.usage.url.paramsl as well in the PR. Regards, Rohit Yadav

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Rohit That did the trick! I did remove all the timezone information on my.cnf and only added the timezone information on the db.properties file. So I can confirm it fixes the issue. If you are using the usage service too you will also need to specify the timezone information for the usage

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Rohit I'll test that and let you know. Regards Liridon -Original Message- From: Rohit Yadav mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com%3e>> Reply-To: d...@cloudstack.apache.org To: Andrija Panic

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Andrija To answer your question: Yes that's something we hit during testing 4.14 only. I also did test 4.13.1 (and other releases) and there it was not required. With CS 4.14 we have to upgrade Java JRE to version 11. This is used under mysql JDBC driver which requires now to set a time

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Andrija, all, While adding support for Java 11, the mysql-connector 8.x java dependency was introduced from previous 5.7x version. According to https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-usagenotes-known-issues-limitations.html it seems we can specify the server time in

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Andrija, Ah no, I just had a quick look out the MySQL documentation, because I vaguely remembered that SET GLOBAL may not be permanent. Just wanted to comment on that, so people don't run into nasty surprises later. Regards, Gregor From: Andrija Panic Sent:

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Gregor, is this something you've also hit during testing 4.14 only, or are you aware of the need for setting those values even before (4.11-4.13) ? Thanks Andrija On Mon, 4 May 2020 at 10:49, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Liridon, > > Note that > > > SET

Re: [VOTE] Apache CloudStack 4.14.0.0 RC1

Hi Liridon, Note that > SET GLOBAL time_zone = '+2:00'; has the mostly same effect as writing > default-time-zone= "-05:00" to /etc/my.cnf The difference is that using SET GLOBAL does not persist the setting across MySQL starts. You should write this setting into the configuration file to

Re: 4.13.1 VR ERR tcp match: only valid for protocol 6

Yes, VNP is enabled in this network (mainly for function test) I have this problem since upgrading from 4.13.0 to 4.13.1. Do you know what service exceptions will be caused by this err? -邮件原件- 发件人: Andrija Panic 发送时间: 2020年5月4日 0:44 收件人: users 主题: Re: 4.13.1 VR ERR tcp match: only