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 zone. If your System has UTC configured it can handle it without specifically configured under my.cnf. However if you time zone is something like CEST (as it was in my case) or EDT (as it was in Roberts case) mysql won't be able to establish a connection and will give the error message that "CEST" is not known and requires you to set the time zone information inside the my.cnf file.
The upgrade went fine but for some reason my dates are configured as UTC inside the database. I'm still looking into this. All time zone related configuration I found in the global configurations were related to usage and were already correct. Regards Liridon -----Original Message----- From: "Riepl, Gregor (SWISS TXT)" <gregor.ri...@swisstxt.ch<mailto:%22Riepl,%20gregor%20%28swiss%20txt%29%22%20%3cgregor.ri...@swisstxt.ch%3e>> Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org> To: users <users@cloudstack.apache.org<mailto:users%20%3cus...@cloudstack.apache.org%3e>> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1 Date: Mon, 04 May 2020 09:38:48 +0000 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 < <mailto:andrija.pa...@gmail.com> andrija.pa...@gmail.com > Sent: 04 May 2020 11:35 To: users < <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org > Subject: 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) < <mailto:gregor.ri...@swisstxt.ch> gregor.ri...@swisstxt.ch > wrote: 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 make it permanent. See <https://dev.mysql.com/doc/refman/5.7/en/using-system-variables.html> https://dev.mysql.com/doc/refman/5.7/en/using-system-variables.html and <https://dev.mysql.com/doc/refman/5.7/en/set-variable.html> https://dev.mysql.com/doc/refman/5.7/en/set-variable.html for more info. Regards, Gregor ________________________________ From: Ismaili, Liridon (SWISS TXT) < <mailto:liridon.isma...@swisstxt.ch> liridon.isma...@swisstxt.ch > Sent: 01 May 2020 19:52 To: <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org < <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org > Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1 @Robert I did add the default-time-zone parameter to the my.cnf file but the dates inside CloudStack are still in UTC format. select now() however gives me the correct output: mysql> select now(); +---------------------+ now() | +---------------------+ 2020-05-01 19:48:38 | +---------------------+ 1 row in set (0.00 sec) Does anyone else have such wrong dates? All tables in the cloud DB seems to be affected. Regards Liridon -----Original Message----- From: Andrija Panic < <mailto:andrija.pa...@gmail.com> andrija.pa...@gmail.com <mailto: <mailto:andrija%20panic%20%3candrija.pa...@gmail.com> andrija%20panic%20%3candrija.pa...@gmail.com %3e>> Reply-To: <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org <mailto: <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org > To: users < <mailto:users@cloudstack.apache.org> users@cloudstack.apache.org <mailto: <mailto:users%20%3cus...@cloudstack.apache.org> users%20%3cus...@cloudstack.apache.org %3e>>, Rohit Yadav < <mailto:rohit.ya...@shapeblue.com> rohit.ya...@shapeblue.com <mailto: <mailto:rohit%20yadav%20%3crohit.ya...@shapeblue.com> rohit%20yadav%20%3crohit.ya...@shapeblue.com %3e>> Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC1 Date: Fri, 01 May 2020 19:08:16 +0200 @Rohit Yadav < <mailto: <mailto:rohit.ya...@shapeblue.com> rohit.ya...@shapeblue.com > <mailto:rohit.ya...@shapeblue.com> rohit.ya...@shapeblue.com can you possibly advice on the time zone issue? I've seen this on another ML thread as well. We are mostly in UTC (test envs) so this might be the reason we didn't see this...could be just a documentation update that is needed. @Robert is there any specifics to your NFS server (i.e. a forbidden NFSv3 or similar)? Also, can you please open a GitHub issue and provide the same there? So we can track it and collaborate - I've not seen this one before. What packages did you use for the installation? On the issue you'll raise, please also include the relevant output from the /var/log/cloud.log from inside the SSVM Also not sure what is the relation between MySQL and JRE at all - they should have nothing in common? Thanks! Andrija On Fri, 1 May 2020 at 17:49, Robert Ward < <mailto: <mailto:rww...@gmail.com> rww...@gmail.com > <mailto:rww...@gmail.com> rww...@gmail.com wrote: Hi all, I too have run into an issues while performing a clean install: Centos 7, MySQL 5.6, JRE 11 JRE 11 and MySQL 5.6 don't see to play well on two points: Installing JRE before MySQL causes MYSQL to "lockup" on startup. I have found that if I install JRE after MySQL that issue is resolved. MySQL chokes with timezone error @ cloudstack-setup-management. In my case MySQL doesn't like "EDT" as a timezone. Resolved by adding this to etc/my.cnf: default-time-zone= "-05:00" On my last point CS has difficulty with mounting secondary storage. I have clipped the logs to the point where I think the problem lies: 2020-05-01 10:55:07,871 DEBUG [c.c.h.o.r.Ovm3HypervisorGuru] (StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) getCommandHostDelegation: class com.cloud.agent.api.GetStorageStatsCommand 2020-05-01 10:55:07,871 DEBUG [c.c.h.XenServerGuru] (StatsCollector-5:ctx-35c593ba) (logid:aad9ed2a) We are returning the default host to execute commands because the command is not of Copy type. 2020-05-01 10:55:07,910 DEBUG [c.c.a.t.Request] (AgentManager-Handler-8:null) (logid:) Seq 2-4356951164504244991: Processing: { Ans: , MgmtId: 144345337593, via: 2, Ver: v1, Flags: 10, [{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException: GetRootDir for nfs://192.168.25.1/export/secondary failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount 192.168.25.1:/export/secondary at /mnt/SecStorage/b7e9e158-ed80-3a62-a5d7-1992c991d829 due to mount.nfs: requested NFS version or transport protocol is not supported\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:2458)\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:2208)\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:292)\n\tat com.cloud.storage.resource.PremiumSecondaryStorageResource.defaultAction(PremiumSecondaryStorageResource.java:64)\n\tat com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:60)\n\tat com.cloud.agent.Agent.processRequest(Agent.java:644)\n\tat com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1057)\n\tat com.cloud.utils.nio.Task.call(Task.java:83)\n\tat com.cloud.utils.nio.Task.call(Task.java:29)\n\tat java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:834)\n","wait":0}}] } My troubleshooting steps: restart SSVM restart MS restart agent verify I can manually mount secondary storage on agent and navigate through all directories. change secondary storage version from null to V4 in CS global settings Any input is greatly appreciated on how to resolve. Thanks, Robert On 2020/04/29 14:38:44, Andrija Panic < <mailto: <mailto:andrija.pa...@gmail.com> andrija.pa...@gmail.com > <mailto:andrija.pa...@gmail.com> andrija.pa...@gmail.com wrote: Hi All, I've created a 4.14.0.0 release (RC1), 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/4.14.0.0-RC20200429T1355> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200429T1355 <https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200429T1355> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200429T1355 Commit: 2c39b7180a9fb40cbdcad5e6a58be64a86913771 Source release (checksums and signatures are available at the same location): < <https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/ > <https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/ PGP release keys (signed using 3DC01AE8): < <https://dist.apache.org/repos/dist/release/cloudstack/KEYS> https://dist.apache.org/repos/dist/release/cloudstack/KEYS > <https://dist.apache.org/repos/dist/release/cloudstack/KEYS> https://dist.apache.org/repos/dist/release/cloudstack/KEYS The vote will be open until Wednesday 06.May.2020. For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote? [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Additional information: For users' convenience, I've built packages from 2c39b7180a9fb40cbdcad5e6a58be64a86913771 and published RC1 repository here (CentOS 7 and Debian/generic): < <http://packages.shapeblue.com/testing/41400rc1/> http://packages.shapeblue.com/testing/41400rc1/ > <http://packages.shapeblue.com/testing/41400rc1/> http://packages.shapeblue.com/testing/41400rc1/ and here (Ubuntu 18.04 specific, thanks to Gabriel): < <https://download.cloudstack.org/testing/4.14.0.0-RC20200429T1355/ubuntu/bionic/> https://download.cloudstack.org/testing/4.14.0.0-RC20200429T1355/ubuntu/bionic/ <https://download.cloudstack.org/testing/4.14.0.0-RC20200429T1355/ubuntu/bionic/> https://download.cloudstack.org/testing/4.14.0.0-RC20200429T1355/ubuntu/bionic/ The release notes are still work-in-progress, but for the upgrade instructions (including new systemVM templates) you may refer the following URL: < <https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr87/upgrading/index.html> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr87/upgrading/index.html <https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr87/upgrading/index.html> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr87/upgrading/index.html 4.14.0.0 systemVM templates are available from here: < <http://download.cloudstack.org/systemvm/4.14/> http://download.cloudstack.org/systemvm/4.14/ > <http://download.cloudstack.org/systemvm/4.14/> http://download.cloudstack.org/systemvm/4.14/ Regards, Andrija Panić -- Andrija Panić
