Forum Discussion
Nimbostratusproblem to configure healt monitor oracle !!!!!!!!!!!!!! help
Hi, I'm having trouble setting up an oracle type monitor, I can't find a solution, we're doing a simple healt heck, the applied monitor is something like this:
tr7556@(F5-LTM-01)(cfg-sync In Sync)(Active)(/Common)(tmos)# list ltm monitor oracle monitor_db_1
ltm monitor oracle monitor_db_1 {
count 1
database "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=%node_ip%)(PORT=%node_port%)) (CONNECT_DATA=(SID=swproddb)) (SERVER=dedicated))"
debug yes
defaults-from oracle
destination *:*
interval 2
password $M$JN$xrQa75yEutCc5w5cpQjV0w==
recv OPEN
recv-column 1
recv-row 1
send "SELECT status FROM v$instance;"
time-until-up 0
timeout 21
username user_f5
}
the query has already been thrown from a linux server and runs without problems, it is executed from a sqlplus and if it works, the credentials are fine and I am only consulting the state of the instance (see image), when reviewing the debug file I have something like this:
019-08-23 18:09:14,709 [main] - client socket accepted: Socket[addr=/0:0:0:0:0:0:0:1,port=50428,localport=1521], bound: true, closed: false
2019-08-23 18:09:14,709 [MonitorWorker-21488] - command: pid
2019-08-23 18:09:14,709 [MonitorWorker-21488] - ----------------------------------------
2019-08-23 18:09:14,710 [main] - client socket accepted: Socket[addr=/0:0:0:0:0:0:0:1,port=50430,localport=1521], bound: true, closed: false
2019-08-23 18:09:14,710 [MonitorWorker-21489] - Count: 1
2019-08-23 18:09:14,710 [MonitorWorker-21489] - Pinger Key: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.30.3.167)(PORT=22)) (CONNECT_DATA=(SID=swproddb)) (SERVER=dedicated))_SELECT status FROM v$instance;_OPEN
2019-08-23 18:09:14,714 [MonitorWorker-21489] - MonitorWorker-21489 will query.
2019-08-23 18:09:14,714 [MonitorWorker-21489] - new pinger created. connect str = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.30.3.167)(PORT=22)) (CONNECT_DATA=(SID=swproddb)) (SERVER=dedicated))
2019-08-23 18:09:14,714 [DBPinger-21489] - Attempting DB connection, attempt # 1
2019-08-23 18:09:14,744 [DBPinger-9129] - waiting for ping
2019-08-23 18:09:14,744 [DBPinger-9127] - waiting for ping
2019-08-23 18:09:14,744 [DBPinger-21097] - waiting for ping
2019-08-23 18:09:14,744 [DBPinger-21099] - waiting for ping
2019-08-23 18:09:14,994 [DBPinger-9129] - waiting for ping
2019-08-23 18:09:14,994 [DBPinger-9127] - waiting for ping
2019-08-23 18:09:14,994 [DBPinger-21097] - waiting for ping
2019-08-23 18:09:14,994 [DBPinger-21099] - waiting for ping
can someone help me ?, I have already read some references but I can not make it work
Hi,
Can you try after changing the interval and timeout values?
Interval = TCP.CONNECT_TIMEOUT = 60 (default)
Timeout = 181
joelinho2019-08-23 22:00:58,818 [DBPinger-9127] - waiting for ping
2019-08-23 22:00:58,818 [DBPinger-9129] - waiting for ping
2019-08-23 22:00:58,818 [DBPinger-23727] - waiting for ping
2019-08-23 22:00:58,818 [DBPinger-21097] - waiting for ping
2019-08-23 22:00:58,818 [DBPinger-23725] - waiting for ping
2019-08-23 22:00:59,022 [DBPinger-48803] - waiting for ping
2019-08-23 22:00:59,028 [DBPinger-48801] - waiting for ping
2019-08-23 22:00:59,067 [DBPinger-21099] - waiting for ping
2019-08-23 22:00:59,068 [DBPinger-9127] - waiting for ping
2019-08-23 22:00:59,068 [DBPinger-9129] - waiting for ping
2019-08-23 22:00:59,068 [DBPinger-23727] - waiting for ping
2019-08-23 22:00:59,068 [DBPinger-21097] - waiting for ping
2019-08-23 22:00:59,068 [DBPinger-23725] - waiting for ping
2019-08-23 22:00:59,272 [DBPinger-48803] - waiting for ping
2019-08-23 22:00:59,278 [DBPinger-48801] - waiting for ping
2019-08-23 22:00:59,317 [DBPinger-21099] - waiting for ping
2019-08-23 22:00:59,318 [DBPinger-9127] - waiting for ping
2019-08-23 22:00:59,318 [DBPinger-9129] - waiting for ping
2019-08-23 22:00:59,318 [DBPinger-23727] - waiting for ping
2019-08-23 22:00:59,318 [DBPinger-21097] - waiting for ping
2019-08-23 22:00:59,318 [DBPinger-23725] - waiting for ping
2019-08-23 22:00:59,522 [DBPinger-48803] - waiting for ping
2019-08-23 22:00:59,528 [DBPinger-48801] - waiting for ping
2019-08-23 22:00:59,567 [DBPinger-21099] - waiting for ping
2019-08-23 22:00:59,568 [DBPinger-9127] - waiting for ping
2019-08-23 22:00:59,568 [DBPinger-9129] - waiting for ping
2019-08-23 22:00:59,568 [DBPinger-23727] - waiting for ping
2019-08-23 22:00:59,568 [DBPinger-21097] - waiting for ping
2019-08-23 22:00:59,568 [DBPinger-23725] - waiting for ping
2019-08-23 22:00:59,772 [DBPinger-48803] - waiting for ping
2019-08-23 22:00:59,779 [DBPinger-48801] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-21099] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-9127] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-9129] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-23727] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-21097] - waiting for ping
2019-08-23 22:00:59,818 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:00,023 [DBPinger-48803] - waiting for ping
2019-08-23 22:01:00,029 [DBPinger-48801] - waiting for ping
2019-08-23 22:01:00,068 [DBPinger-21099] - waiting for ping
2019-08-23 22:01:00,068 [DBPinger-9127] - waiting for ping
2019-08-23 22:01:00,069 [DBPinger-9129] - waiting for ping
2019-08-23 22:01:00,069 [DBPinger-23727] - waiting for ping
2019-08-23 22:01:00,069 [DBPinger-21097] - waiting for ping
2019-08-23 22:01:00,069 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:00,273 [DBPinger-48803] - waiting for ping
2019-08-23 22:01:00,279 [DBPinger-48801] - waiting for ping
2019-08-23 22:01:00,318 [DBPinger-21099] - waiting for ping
2019-08-23 22:01:00,319 [DBPinger-9129] - waiting for ping
2019-08-23 22:01:00,319 [DBPinger-9127] - waiting for ping
2019-08-23 22:01:00,319 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:00,319 [DBPinger-21097] - waiting for ping
2019-08-23 22:01:00,319 [DBPinger-23727] - waiting for ping
2019-08-23 22:01:00,526 [DBPinger-48803] - waiting for ping
2019-08-23 22:01:00,530 [DBPinger-48801] - waiting for ping
2019-08-23 22:01:00,568 [DBPinger-21099] - waiting for ping
2019-08-23 22:01:00,569 [DBPinger-9129] - waiting for ping
2019-08-23 22:01:00,569 [DBPinger-9127] - waiting for ping
2019-08-23 22:01:00,569 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:00,569 [DBPinger-21097] - waiting for ping
2019-08-23 22:01:00,569 [DBPinger-23727] - waiting for ping
2019-08-23 22:01:00,776 [DBPinger-48803] - waiting for ping
2019-08-23 22:01:00,780 [DBPinger-48801] - waiting for ping
2019-08-23 22:01:00,818 [DBPinger-21099] - waiting for ping
2019-08-23 22:01:00,819 [DBPinger-9129] - waiting for ping
2019-08-23 22:01:00,819 [DBPinger-9127] - waiting for ping
2019-08-23 22:01:00,819 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:00,819 [DBPinger-21097] - waiting for ping
2019-08-23 22:01:00,819 [DBPinger-23727] - waiting for ping
2019-08-23 22:01:01,026 [DBPinger-48803] - waiting for ping
2019-08-23 22:01:01,030 [DBPinger-48801] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-21099] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-9129] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-9127] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-23725] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-21097] - waiting for ping
2019-08-23 22:01:01,069 [DBPinger-23727] - waiting for ping
status down
The node port seems to 22. Can you change it?
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=%node_ip%)(PORT=1521)) (CONNECT_DATA=(SID=swproddb)) (SERVER=dedicated))
