After this issue I did some other RHEL5
installations and didn’t see the issue on those hosts.
Differences between those installations and
this one were:
1)
I had gone into the GUI
host properties for Master and set this client to use ports for firewall as we’d
previously done with 5.1. On the new clients it defaults to vnetd in firewall
configuration so this wasn’t necessary. On removing this setup after the
other installs it didn’t resolve the issue by itself but I mention it as
it *might* be part of the
solution.
2)
During my initial attempt
to do backup on the RHEL5 host it had failed on missing library, /usr/lib/libstdc++-libc6.2-2.so.3.
This was because the compat-libstdc++-296 package wasn’t installed.
Installation of that package made the backup work but I got the error noted in
original message. On all the new hosts I installed compat-libstdc++-296
before installing NBU 6.0 MP4 client.
I believe item 2 was what actually fixed
it. On the original host I removed the installation then reinstalled (this
means the compatibility library was already there on reinstall of NBU). After
reinstall the backup worked without giving the bpbrm error. Also I noticed on
all the successful installs including this reinstall it creates the
/usr/openv/logs directory and creates log with a header. It hadn’t done
that during my initial install on the problem host.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jeff Lightner
Sent: Tuesday, March 04, 2008 6:22
PM
To:
VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Could not read
logging configuration file
Trying
to figure out the fix for this message:
Error
bpbrm (pid=28218) from client atlrdda3: ERR - Error occurred during
initialization. Could not read logging configuration file.
I
see this at the beginning of backup even though the backup ultimately completes
with 0 exit status.
On
searching forums and Symantec site I see a lot of talk about possibly corrupt
nblog.conf. This is a brand new installation however and it seems clear it
pushed out the nblog.conf.template then made a nblog.conf on the system during
the installation so it is unclear to me how it could be corrupt.
I
found the vxlogcfg utility but can’t really make much sense out of
it. No man page just a “vxlogcfg –h”
to get some information.
This
is a RHEL5 client but the Symantec site mentions same issue with
RHEL4. Their solution is to copy the
nblog.conf from another server of the same type and version but we don’t
have one. In fact on checking a RHEL5 server a co-worker installed I see
his backup jobs get the same error (with pid being different of course).
Some
things I’ve tried:
1)
Something
mentioned path being <installpath>/NetBackup – we have
“netbackup”
so I created a symbolic link since Linux/UNIX are case sensitive. No go.
2)
The
nblog.conf specifies logs in /usr/openv/logs – that
directory didn’t exist so I created it. No go.
3)
I had
iptables firewall running (Master was configured to know this
but…). Turned off iptables. No go.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
