08-23-2022 10:03 AM
Hello,
i tried to install security patch NB_8.3.0.2_ET4067650_2, but it failed with those errors:
-----
...
Skipping EEB install. EEB: name: [4067617]; skipReason: [ALREADY_INSTALLED]
Skipping EEB install. EEB: name: [4067913]; skipReason: [ALREADY_INSTALLED]
Skipping EEB install. EEB: name: [4067969]; skipReason: [ALREADY_INSTALLED]
Attempting to install EEB: [eebinstaller_4079114_1_AMD64.exe]
Attempting to install EEB: [eebinstaller_4079122_1_AMD64.exe]
Attempting to install EEB: [eebinstaller_4077106_1_AMD64.exe]
Attempting to install EEB: [eebinstaller_4075538_1_AMD64.exe]
Attempt to install EEB failed with status [1].
Output from failed attempt: [localhost is a master server
-----
further down:
Validating target platform... Successful!
Starting pre-processing.
Extracting pre-process script -- C:\Program Files\VERITAS\NetBackup\Temp\preprocess_install_4075538.exe
Starting install failure processing.
Extracting install failure script -- C:\Program Files\VERITAS\NetBackup\wmc\webserver\webapps_api\install_failure_4075538_eebi_nbwmc.ps1
install failure complete.
Error executing: ""C:\Program Files\VERITAS\NetBackup\Temp\preprocess_install_4075538.exe"" -no_questions, returned 255
]
----------
Now the backups no longer work, they all fail with status 23: socket real failed.
I already opened a case at veritas support but got no answer yet. I was wondering if its worth trying to uinstall the eeb or if chances are high that i will make things even worse?
Kind regards
08-23-2022 07:35 PM
@mst1 I have the same problem after running this EEB, but my backups for while is running because I don't using MSDP disk on master server, did you receive any answer to Veritas support?
08-23-2022 09:03 PM
Hello, no, so far i haven't received an answer yet.
Meanwhile i realized some other things:
The backup of the netbackup catalog works, it seems i just can't communicate with other machines it should backup. Also when i'm in the administration console and select Netbackup Management / Host properties / Clients it failes to connect to any of the clients there (except for the server itself). But of course the server is connected to the network and can for example reach the clients it should backup over ping.
When i use bpdown and bpup to restart the services, starting the Web Management Console service takes between 45 - 60 Minutes.
Kind regards
08-23-2022 09:42 PM
08-23-2022 10:25 PM
Thank you very much, i wasn't sure if such a situation allows for highest priority. I will try to contact support again. Meanwhile i realized that jobs fail with those errors:
24.08.2022 06:00:35 - Error bpbrm (pid=13596) [PROXY] Connecting host: xxbackupxx
24.08.2022 06:00:35 - Error bpbrm (pid=13596) [PROXY] ConnectionId: {88CE8BA9-1401-4E09-BB7D-8FCD7DBB5264}:OUTBOUND
24.08.2022 06:00:35 - Error bpbrm (pid=13596) [PROXY] pid: 224
24.08.2022 06:00:35 - Error bpbrm (pid=13596) [PROXY] Received status: 26 with message Unable to perform peer host name validation. Curl error has occurred for peer name: xxarchiv1.xx.de, self name: xxBACKUPxx
24.08.2022 06:00:35 - Error bpbrm (pid=13596) [PROXY] Encountered error (VALIDATE_PEER_HOST_PROTOCOL_RUNNING) while processing(ValidatePeerHostProtocol).
24.08.2022 06:00:35 - Error bpbrm (pid=13596) bpcd on xxarchiv1.xx.de exited with status 23: socket read failed
24.08.2022 06:00:35 - Info bpbkar32 (pid=0) done. status: 23: socket read failed
24.08.2022 06:00:35 - end writing
09-23-2022 12:40 PM
did you get any solution about this problem?