PostgreSQL Monitor Addition Fails with “Invalid value for parameter 'TimeZone'”

PostgreSQL Monitor Addition Fails with “Invalid value for parameter 'TimeZone'”

Error Message
FATAL: invalid value for parameter "TimeZone":

Troubleshooting 

 1. Execute the below query on PgSQL server which you are trying to add as a monitor

  1. SHOW TimeZone;

Cause

This error occurs because the PostgreSQL server does not recognize the timezone 

Resolution

To resolve this issue, configure the correct timezone for the AppManager service as follows:

  1. Open the file:

    <AppManager_Home>/working/conf/wrapper.conf

  2. Add the following line (or modify if it already exists) to set the correct timezone:

    wrapper.java.additional.37=-Duser.timezone={Add the result of the SHOW TimeZone query here}

  3. 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 → timezone parameter) use consistent, valid timezone names.



      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • 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 ...

                    • 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 ...

                    • 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 ...

                    • How to get ISP and Region data in Real User Monitor?

                      The default setting of the Real User Monitor does not display ISP and region data for the end user. To obtain the data, you have the option to use a third-party Geolocation API. Currently, RUM exclusively supports APIs that provide responses in JSON ...

                    • 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 ...

                      Related Products