Hi Liridon,
I think CS has the wrong timezone because the default project is set to GMT/UTC. I believe you can change that in the global settings. I have the same situation but my management logs have the correct timestamp. Thanks, Robert On 2020/05/01 17:52:46, "Ismaili, Liridon (SWISS TXT)" <liridon.isma...@swisstxt.ch> wrote: > @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 > <andrija.pa...@gmail.com<mailto:andrija%20panic%20%3candrija.pa...@gmail.com%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>>, > Rohit Yadav > <rohit.ya...@shapeblue.com<mailto: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: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: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: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 > > > 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/ > > > > PGP release keys (signed using 3DC01AE8): > > <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/ > > > 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/ > > > > 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 > > > > 4.14.0.0 systemVM templates are available from here: > > <http://download.cloudstack.org/systemvm/4.14/> > > http://download.cloudstack.org/systemvm/4.14/ > > > > Regards, > > Andrija Panić > > > > >
