(DP) Support Tip: BSM/CSM SessionError "[138:742] Backup session "R-..."

1 Likes
over 2 years ago

Error Message
Backup doesn't start intermittently .
DP Event log only shows an error of undefined session ID with "R-" .

- Ob2EventLog.txt
Major 03/28/2019 03:04 BSM/CSM SessionError "[138:742] Backup session "R-2019/03/28-66" of the backup specification "",backup group "Default" has errors: 2."

- debug.log
2019-03-28 03:04:25.134 BSM.9698.538052416 ["/sm/smcmn/smmain.c $Rev: 60516 $ $Date:: 2017-10-27 06:01:07 ":1545] A.10.00 b308
DbgStack: DbgFcnOut() function does not match function on stack!
ExitFcn="SmMainLoop", StackFcn="br_openCDB"
cmd:bsm
Function trace (currentLevel=1):
Level 1: br_openCDB()
Level 0: SmMainLoop()
"SmMainLoop" found on stack, adjusted level to 0 (one or more DbgFcnOut() calls missing)
SeqSeek: Position verified!

- hpdp-idb-cp.log
2019-03-28 03:04:24.113 5902 WARNING C-0x7cfec0: hpdpidb/hpdpidb_app@127.0.0.1:43006 Pooler Error: pgbouncer cannot connect to server
2019-03-28 03:04:24.114 5902 WARNING C-0x7cfec0: hpdpidb/hpdpidb_app@127.0.0.1:43010 Pooler Error: pgbouncer cannot connect to server

Cause
The error situation occurred because /etc/hosts resolves localhost to ::1 although IPv6 can not be used at the system .
As a result , pgbouncer tried using ::1 to connect to PostgreSQL, but it failed .
BSM failed immediately without waiting for pgbouncer reconnection because it's not expected error situation .

Workaround / Fix
1. Disable IPv6 loopback for connection between pgbouncer and postgreSQL
file : /var/opt/omni/server/db80/pg/pg_hba.conf

Comment out the entry of IPv6 as follows .

# IPv6 local connections:
#host all all ::1/128 md5

Restart IDB (or omnisv stop/start)

2. Remove any IPv6 entries in /etc/hosts file if IPv6 can not be used at the system

Labels:

Support Tip
Comment List
Anonymous
Related Discussions
Recommended