You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated my voms packages to the latest from https://repo.cloud.cnaf.infn.it/repository/voms-rpm-stable/centos7/
and ran into a problem with the mysql connector: java.sql.SQLException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
(from the /var/log/voms-admin/voms-admin-<MYVO>.log file).
From e.g. https://stackoverflow.com/q/37719818, in particular https://stackoverflow.com/a/54256150 I just added ?serverTimezone=Europe/Amsterdam to the hibernate.connection.url=jdbc:mysql://localhost:3306/voms_<MYVO>
line in /etc/voms-admin/<MYVO>/database.properties
which solves the issue.
This is an up-to-date CentOS7.9 with mariadb-server-5.5.68-1.el7 and voms-admin-server-3.8.1-1.el7
I'm not sure if this is a misconfiguration from our side but don't fully understand why we didn't see this before.
The text was updated successfully, but these errors were encountered:
I just updated my voms packages to the latest from
https://repo.cloud.cnaf.infn.it/repository/voms-rpm-stable/centos7/
and ran into a problem with the mysql connector:
java.sql.SQLException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.
(from the
/var/log/voms-admin/voms-admin-<MYVO>.log
file).From e.g. https://stackoverflow.com/q/37719818, in particular https://stackoverflow.com/a/54256150 I just added
?serverTimezone=Europe/Amsterdam
to thehibernate.connection.url=jdbc:mysql://localhost:3306/voms_<MYVO>
line in
/etc/voms-admin/<MYVO>/database.properties
which solves the issue.
This is an up-to-date CentOS7.9 with mariadb-server-5.5.68-1.el7 and voms-admin-server-3.8.1-1.el7
I'm not sure if this is a misconfiguration from our side but don't fully understand why we didn't see this before.
The text was updated successfully, but these errors were encountered: