Forum Discussion

mst1's avatar
mst1
Level 3
3 years ago

Installation of EEB NB_8.3.0.2_ET4067650_2 failed, now backups fail with error status 23

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

 

5 Replies

  • 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?

    • mst1's avatar
      mst1
      Level 3

      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

       

       

      • StefanosM's avatar
        StefanosM
        Level 6
        I asume that no backup is working.
        Call support on the phone and ask helpdesk to raise the severity to 1. ( server down).
        They will put you on hold and forward you to the next available engineer.