After upgrade to NetBackup 10.2, pgbouncer will not start

Article: 100056028
Last Published: 2023-07-04
Ratings: 0 0
Product(s): NetBackup


The PostgreSQL Bouncer connection pooler (pgbouncer) was implemented as a process since NetBackup 10.2. to pool and optimize connections from other parts of NetBackup to the PostgreSQL database engine.
Pgbouncer process crashes if /etc/resolv.conf is missing on the primary host. This causes the NetBackup process to have communication problems.

Additionally, an upgrade to 10.2 may fail if /etc/resolv.conf does not exist prior to the upgrade.

Error Message

Snippets from install log on NetBackup Primary Server:

WARNING: NetBackup web services could not start on this host. This will cause
         failure of certain NetBackup operations. For details, refer to:

Snippets from pgbouncer_<TIMEPTAMP>_XXXXX.log NetBackup Primary Server:

2023-05-11 22:15:04.370 JST [9434] LOG kernel file descriptor limit: 8000 (hard: 8000); max_client_conn: 2000, max expected fd use: 2252
2023-05-11 22:15:04.370 JST [9434] ERROR evdns_base_new failed

Snippets from messages on NetBackup Primary Server:

May 11 22:15:04 nbumaster kernel: pgbouncer[9434]: segfault at 130 ip 00007ff8af4f5f7b sp 00007ffe0f45be60 error 4 in[7ff8af4c2000+52000]
May 11 22:15:04 bumaster kernel: Code: eb ad 0f 1f 44 00 00 48 89 df e8 60 f4 ff ff eb a3 66 0f 1f 44 00 00 48 83 c4 08 5b 5d c3 90 55 89 f5 53 48 89 fb 48 83 ec 08 <48> 8b b7 30
 01 00 00 48 85 f6 74 0c 48 8b 05 b2 ef 21 00 31 ff ff
May 11 22:15:04 nbumaster sssd_nss[1235]: Enumeration requested but not enabled
May 11 22:15:04 nbumaster systemd[1]: Created slice system-systemd\x2dcoredump.slice.
May 11 22:15:04 nbumaster systemd[1]: Started Process Core Dump (PID 9436/UID 0).
May 11 22:15:06 nbumaster systemd-coredump[9451]: Resource limits disable core dumping for process 9434 (pgbouncer).
May 11 22:15:06 nbumaster systemd-coredump[9451]: Process 9434 (pgbouncer) of user 1002 dumped core.



Since pgbouncer refers to /etc/resolv.conf file even when DNS is not used, it will not work properly if /etc/resolv.conf file is missing.



The workaround is to create an empty /etc/resolv.conf file if it does not exist on the primary host.

If upgrading to 10.2, the file must be created prior to the attempted upgrade to 10.2.

If an upgrade encounters errors due to a missing /etc/resolv.conf, re-running the installer after creating /etc/resolv.conf may result in a successful upgrade.

Note: This issue has been fixed in NetBackup, which is generally available.  When upgrading NetBackup, it is highly recommended to upgrade to the latest available release.

Applies To: Linux operating system


Etrack : 4116963

Was this content helpful?