cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup update_clients fails for few servers

Can someone please help me on below error.. I am trying to push install the Netbackup version 7.7.2 from media server and for few client its successfull and for few its failed with below error. 

#./update_clients -ForceInstall -Install_Client_Bins -ClientList /tmp/client

There are 1 clients to upgrade.

The upgrade will likely take 1 to 3 minutes.
Do you want to upgrade clients now? [y,n] (y)
Please be patient.

Updating client client_1 -- Linux hardware running RedHat2.6.18
client_1: update failed, see /tmp/update_clients.08-16-1623.20050

The update trace can be found in /tmp/update_clients.08-16-1623.20050.

 


# cat /tmp/update_clients.08-16-1623.20050
fairmont701-bk Linux/RedHat2.6.18 ...
CLIENT_CMD_SOCK from bpcd = 4
CLIENT_STAT_SOCK from bpcd = 5
BPCD connected
Couldn't read from file /usr/openv/netbackup/version on client client_1
Client read errno = 0
bin_net.tar.20050 size = 10240
client_bin.tar.gz size = 182844841
.sizes_client_bin size = 7
NB-Java.tar.gz size = 347107379
.sizes_NB-Java size = 7
JRE.tar.gz size = 40828448
.sizes_JRE size = 6
nbj.conf.20050 size = 671
PBX.tar.gz size = 9282324
installpbx size = 62891
pddeagent.tar.gz size = 22448030
pdinstall size = 33685
fairmont701-bk.20050 size = 29
cp_to_client size = 87521
extract_java size = 23750
install_client size = 31254
nbcheck size = 11816726
version size = 29
nbbsdtar size = 2106467
.sizes size = 15
client_config size = 98315
client_config size = 98315

INF OTHER - EXIT STATUS = 127
EXIT STATUS = 127

 

 

 

Tags (1)
8 Replies

Re: Netbackup update_clients fails for few servers

You forgot to tell us the OS on the master?

Can you please show us the contents of this folder on the master?
/usr/openv/netbackup/client/Linux

and output of :
bpgetconfig -M client_1

 

Re: Netbackup update_clients fails for few servers

Hi Marianne,

                It is Media server from where I am trying to push.  Below is the info

Media Server OS =Red Hat Enterprise Linux Server release 6.7.

]# bpgetconfig -s client_1
Client of Master-Server
Linux, RedHat2.6.18
7.6.0.0.0.2
NetBackup
7.6
760000
/usr/openv/netbackup/bin
Linux 2.6.32-642.6.2.el6.x86_64

 

# cd /usr/openv/netbackup/client/Linux
# ls -altr
total 32
drwxr-xr-x. 2 root bin 4096 Apr 25 2014 SuSE2.6.16
drwxr-xr-x. 2 root bin 4096 Apr 25 2014 IBMpSeriesSuSE2.6
drwxr-xr-x. 2 root bin 4096 Apr 25 2014 IBMpSeriesRedHat2.6
drwxr-xr-x. 2 root bin 4096 May 18 2016 Debian2.6.18
drwxr-xr-x. 2 root bin 4096 May 18 2016 RedHat2.6.18
drwxr-xr-x. 2 root bin 4096 May 18 2016 SuSE3.0.76
drwxr-xr-x. 15 root bin 4096 May 18 2016 ..
drwxr-xr-x. 8 root bin 4096 May 18 2016 .

Re: Netbackup update_clients fails for few servers

The timestamp on the media server folder RedHat2.6.18 looks a bit old.

What is in the contents of the version file in that folder?

Re: Netbackup update_clients fails for few servers

Hi Marianne,

                 But I am able to upgrade the client on few other servers running RHEL 6/7 from same media server.

Re: Netbackup update_clients fails for few servers

# pwd
/usr/openv/netbackup/client/Linux/RedHat2.6.18
# cat version
NetBackup-RedHat2.6.18 7.7.2

Tags (2)

Re: Netbackup update_clients fails for few servers

I have searched for Error 127 with update_clients and could only find this forum post:

https://vox.veritas.com/t5/NetBackup-Appliance/Push-NBU-client-install/td-p/817684

The most feasible reply was from @vtas_chas :

Do you have enough space on the drive?  I've seen 127s with a full /tmp or / file system.

Re: Netbackup update_clients fails for few servers

Marianne, Thanks for the reply.   There is 6 GB free space in /tmp, / and /usr. 

When I looked into the client /var/log/messages i see below error, 

Aug 17 10:36:25  kernel: bpcd: page allocation failure. order:0, mode:0x20

Aug 17 10:36:25  kernel: Pid: 23614, comm: bpcd Not tainted 2.6.32-642.6.2.el6.x86_64 #1

Aug 17 10:36:25  kernel: Call Trace:...

Re: Netbackup update_clients fails for few servers

Could be this red hat bug:

https://access.redhat.com/solutions/90883

Please note this section:

The below mentioned workaround also works in 2.6.32-358.el6 and newer if the issue still persists even after the update