vertica
1 TopicVertica DB Monitoring Failure post upgrade 10.x to 23.x
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 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 Fail Both Select 1 and Select from Dual receive the below successfully _________________________________________________________________________________________________ Troubleshooting via F5 CLI foo.bar.f5.com:Active# DB_monitor cmd status debug 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_6464Views0likes3Comments