-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.3.0
-
rear-2.6-22.el9
-
Normal
-
OtherQA
-
sst_cs_system_management
-
ssg_core_services
-
24
-
26
-
3
-
False
-
-
No
-
Red Hat Enterprise Linux
-
Unspecified Release Note Type - Unknown
What were you trying to do that didn't work?
A customer using NetBackup 10.2.0.1 fails to recover the system.
It's unclear at this point if the issue is specific to NetBackup 10.2.0.1 or applies to NetBackup in general.
Digging into this, we could find out that the ReaR ISO was missing "proxy_peers" and "nbrntd_peers" directories, as seen in the strace:
15741 14:59:45.048352 openat(AT_FDCWD</root>, "/usr/openv/var/proxy_peers/04d/SERVERIP-SERVERPORT-CLIENTIP-CLIENTPORT.json", O_RDONLY) = -1 ENOENT (No such file or directory) <0.000025> 15741 14:59:45.048417 openat(AT_FDCWD</root>, "/usr/openv/var/nbrntd_peers/SERVERIP-SERVERPORT-CLIENTIP-CLIENTPORT.dat", O_RDONLY) = -1 ENOENT (No such file or directory) <0.000025> (more occurrences)
The resulting error message in bprestore logs was:
14:59:45.489 [15741] <16> dump_proxy_info: statusmsg: Unable to perform peer host name validation. Curl error has occurred for peer name: SERVERNAME, self name: CLIENTNAME, NetBackup status = 0, severity = 2, Additional Message: [PROXY] E...
The resulting error message in ReaR logs was:
EXIT STATUS 25: cannot connect on socket
Including /usr/openv/var into the ReaR ISO fixed the issue:
COPY_AS_IS_NBU+=( /usr/openv/var )
Please provide the package NVR for which bug is seen:
rear-2.6-19.el9.x86_64
How reproducible:
Always on customer system, cannot test myself since no access to NetBackup
- links to
-
RHSA-2024:126086
rear bug fix and enhancement update