# Vertica DB Monitoring Failure post upgrade 10.x to 23.x **URL:** \ **Category:** Technical Forums\ **Tags:** monitors\ **Created:** [September 10, 2024, 2:58pm UTC](https://community.f5.com/t/vertica-db-monitoring-failure-post-upgrade-10-x-to-23-x/75114 "2024-09-10T14:58:14Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ShaunSimmons](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@ShaunSimmons](https://community.f5.com/u/ShaunSimmons)\ **Post date:** [September 10, 2024, 2:58pm UTC](https://community.f5.com/t/vertica-db-monitoring-failure-post-upgrade-10-x-to-23-x/75114/1 "2024-09-10T14:58:14Z")
I need assistance with a Vertica monitor, due to versions have caused the F5 to no longer be able to use a postgresql monitor. **-Why does the monitor for 23.3 no longer work?** Pool Monitor Type:  Postgresql local login:  password verified and working for version 10.1 --------------------------------------------------------------------------------------------- **Current Vertica Version: 23.3 / Previous Version 10.1** \*TMOS 15.1 and 17.1 have the same Pool member status result/symptoms ![image_334211.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/b/b3ebd6109ca1dacb502594583f25aac17993b21c.png) Monitors tested:  Postgresql, Oracle, Mysql  ( to think outside the box ) Currently configured for the Pool: Postgresql -Send strings tested for all monitor types- Send String: SELECT 1 Send String: SELECT 1 FROM DUAL; Receive: 1   **\*10.1 = Success / 23.3 Fail** ----------------------------- Send String: SELECT 1 Send String: SELECT 1 FROM DUAL; Receive: Nothing   **\*10.1 = Success / 23.3 Fai** l Both Select 1 and Select from Dual receive the below successfully ![image_334211.png](https://d20hrnpixdzcsd.cloudfront.net/original/3X/b/6/b636ca8b889d37313c8d20273b96271bb49d1a47.png) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Troubleshooting via F5 CLI** [foo.bar.f5.com](http://foo.bar.f5.com):Active# DB\_monitor cmd status debug ![image_334211.png](https://d20hrnpixdzcsd.cloudfront.net/original/3X/e/0/e0a7f2071cf97c8bc2d948e66b7ab1842161a04c.png) **Telnet** Port 5433 = Successful **Version of jdbc does not matter between TMOS versions, the monitor still fails** **RPM version ( TMOS 15.1 )** postgresql-jdbc-42.2.13-.0.0.32.noarch postgresql-9.3.2-0.0.32.i686 postgresql-libs-9.3.2-0.0.32.i686 postgresql-share-9.3.2-0.0.32.i686 **RPM version ( 17.1 )** postgresql-server-15.0-1.fc38.0.0.2.x86\_64 postgresql-jdbc-42.2.13-0.0.2.noarch postgresql-private-libs-15.0-1.fc38.0.0.2.i686 postgresql-15.0-1.fc38.0.0.2.x86\_64 postgresql-private-libs-15.0-1.fc38.0.0.2.x86\_64 ---
**Author:** ![ShaunSimmons](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@ShaunSimmons](https://community.f5.com/u/ShaunSimmons)\ **Post date:** [September 12, 2024, 1:35pm UTC](https://community.f5.com/t/vertica-db-monitoring-failure-post-upgrade-10-x-to-23-x/75114/2 "2024-09-12T13:35:02Z")
Bump - Buller…Buelller..Bueller  đŸ¤£ ---
**Author:** ![ShaunSimmons](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@ShaunSimmons](https://community.f5.com/u/ShaunSimmons)\ **Post date:** [September 17, 2024, 9:23pm UTC](https://community.f5.com/t/vertica-db-monitoring-failure-post-upgrade-10-x-to-23-x/75114/3 "2024-09-17T21:23:00Z")
Anyone have any thoughts? đŸ™‚ ---
**Author:** ![boneyard](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/boneyard/32/20419_2.png) [@boneyard](https://community.f5.com/u/boneyard)\ **Post date:** [September 29, 2024, 5:10pm UTC](https://community.f5.com/t/vertica-db-monitoring-failure-post-upgrade-10-x-to-23-x/75114/4 "2024-09-29T17:10:57Z")
Do you also have a ticket open with F5 support? That seems like the good way to go.