Loading...
Loading...
JDBC uses an incorrect timezone rather than the one configured on the system through 'sys ntp timezone'. In a PostgreSQL-based health monitor, an error similar to the following may occur, for example when 'sys ntp timezone' is set as America/Los_Angeles' (default): org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "US/Pacific-New" In an Oracle health monitor, an error similar to the following may occur, for example when 'sys ntp timezone' is set as 'UTC' when the client presents a timezone of 'Zulu': java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01882: timezone region not found
Monitor incorrectly marks the pool member down when the remote database server does not recognize the time zone presented by the DB monitor.
1. A DB monitor is in use (eg. PostgreSQL, Oracle). 2. The current timezone of the system is set with a timezone that has multiple equivalent and possibly deprecated aliases, for example: - America/Los_Angeles [US/Pacific-New, posix/US/Pacific-New ] - UTC [ Zulu, posix/Zulu ] 3. System has /etc/localtime as a normal file instead of a symbolic link. 4. The remote database does not support the presented time zone parameter.
Delete the file /etc/localtime: rm /etc/localtime Create a symbolic link for the file pointing to the desired timezone as listed in /usr/share/zoneinfo: For example, if you have 'sys ntp timezone UTC', the command would be: ln -sf /usr/share/zoneinfo/UTC /etc/localtime If you have 'sys ntp timezone America/Los_Angeles', the command would be: ln -sf /usr/share/zoneinfo/America/Los_Angeles /etc/localtime
None
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.