PostgreSQL Monitor Addition Fails with “Invalid value for parameter 'TimeZone'” Error
FATAL: invalid value for parameter "TimeZone": "Asia/Calcutta"
Cause
This error occurs because the PostgreSQL server does not recognize the timezone Asia/Calcutta.
The valid timezone identifier as per PostgreSQL standards is Asia/Kolkata.
If the Java runtime environment or the application wrapper process is configured to use Asia/Calcutta, PostgreSQL rejects the connection during validation of timezone parameters.
Resolution
To resolve this issue, configure the correct timezone for the AppManager service as follows:
Open the file:
<AppManager_Home>/working/conf/wrapper.confAdd the following line (or modify if it already exists) to set the correct timezone:
wrapper.java.additional.37=-Duser.timezone=Asia/Kolkata-
Save the file and restart the AppManager service for the changes to take effect.
Verification
After restarting the service:
-
Try adding the PostgreSQL monitor again.
-
The connection should succeed without the
invalid value for parameter "TimeZone"error.
Additional Information
-
Ensure both the server OS timezone and PostgreSQL configuration (
postgresql.conf→timezoneparameter) use consistent, valid timezone names.
New to ADSelfService Plus?
Related Articles
Troubleshooting URL Monitor
When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...Monitor Addition Fails with ‘Invalid Username & Password’ Error Despite Providing Correct Credentials
If your build version is 177300 or above, but below 178400, there is a known issue that causes Monitor Addition Failure due to invalid username or password. To resolve this, on the remote WebLogic server Version 12, navigate to <Weblogic ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...REST API Monitor - FAQS
1. What to do when Basic Authentication fails in REST API monitor? When Basic Authentication fails in the REST API monitor, follow the below steps to troubleshoot the error. Ensure the credentials provided in Applications Manager (Username and ...