Problems report for backup shows "ERR - NetBackup libonline_util library not installed: ld.so.1: bpfis: fatal: /usr/openv/lib/libonline_util.so: open failed: No such file or directory."
| Article:TECH35812 | | | Created: 2004-01-30 | | | Updated: 2005-01-29 | | | Article URL http://www.symantec.com/docs/TECH35812 |
Problem
Problems report for backup shows "ERR - NetBackup libonline_util library not installed: ld.so.1: bpfis: fatal: /usr/openv/lib/libonline_util.so: open failed: No such file or directory."
Error
ERR - NetBackup libonline_util library not installed: ld.so.1: bpfis: fatal:
/usr/openv/lib/libonline_util.so: open failed: No such file or directory
Solution
The following message may appear in the problems report for
a UNIX client backup when the policy type is set to
MS-Windows-NT.
11/29/2004 09:45:26 master client expected start message from client;
read: ERR - NetBackup libonline_util library not
installed: ld.so.1: bpfis: fatal:
/usr/openv/lib/libonline_util.so: open failed: No such
file or directory
11/29/2004 09:45:26 master client expected start message from client;
read: INF - No valid files in the file list
11/29/2004 09:45:26 master client could not write file list name to
COMM_SOCK
11/29/2004 09:45:27 master client CLIENT client POLICY policy
SCHED DIFF EXIT STATUS 24 (socket write failed)
These errors are caused by an incorrect setting in the Policy Attributes for the policy listed in the backup. If the policy type is set to MS-Windows-NT then any UNIX client in the policy will fail with the above errors.
To correct this, set the policy type to Standard. If there are any Windows clients listed in the policy then create a seperate policy for any UNIX clients and set the policy type to Standard.
11/29/2004 09:45:26 master client expected start message from client;
read: ERR - NetBackup libonline_util library not
installed: ld.so.1: bpfis: fatal:
/usr/openv/lib/libonline_util.so: open failed: No such
file or directory
11/29/2004 09:45:26 master client expected start message from client;
read: INF - No valid files in the file list
11/29/2004 09:45:26 master client could not write file list name to
COMM_SOCK
11/29/2004 09:45:27 master client CLIENT client POLICY policy
SCHED DIFF EXIT STATUS 24 (socket write failed)
These errors are caused by an incorrect setting in the Policy Attributes for the policy listed in the backup. If the policy type is set to MS-Windows-NT then any UNIX client in the policy will fail with the above errors.
To correct this, set the policy type to Standard. If there are any Windows clients listed in the policy then create a seperate policy for any UNIX clients and set the policy type to Standard.
|
|
Legacy ID
273357
Article URL http://www.symantec.com/docs/TECH35812
Terms of use for this information are found in Legal Notices
Thank you.