cancel
Showing results for 
Search instead for 
Did you mean: 

Error occurred during initialization. Could not read logging configuration file.

lanira_1509
Level 4

Hi every body,

As the title indicates, I have this message on my Media Server which is also the Master Server.(NetBackup 7.0.1)

In the bpdm log

Here the details :

14:04:33.379 [7760.6476] <16> initialize: Error occurred during initialization.  Could not read logging configuration file.
14:04:33.394 [7760.6476] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172004 -jm
14:04:33.394 [7760.6476] <2> main: Sending [EXIT STATUS 0] to NBJM
14:04:33.394 [7760.6476] <2> bptm: EXITING with status 0 <----------
14:14:33.382 [6000.8320] <16> initialize: Error occurred during initialization.  Could not read logging configuration file.
14:14:33.382 [6000.8320] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172009 -jm
14:14:33.397 [6000.8320] <2> main: Sending [EXIT STATUS 0] to NBJM
14:14:33.397 [6000.8320] <2> bptm: EXITING with status 0 <----------
14:24:33.385 [5968.4128] <16> initialize: Error occurred during initialization.  Could not read logging configuration file.
14:24:33.401 [5968.4128] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172014 -jm
14:24:33.401 [5968.4128] <2> main: Sending [EXIT STATUS 0] to NBJM
14:24:33.401 [5968.4128] <2> bptm: EXITING with status 0 <----------
14:34:33.357 [9932.8988] <16> initialize: Error occurred during initialization.  Could not read logging configuration file.
14:34:33.373 [9932.8988] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172019 -jm
14:34:33.373 [9932.8988] <2> main: Sending [EXIT STATUS 0] to NBJM

This error happened since 2 days.

Someone has an idea ?

Thank you very much.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

nblog.conf may be corrupt. 
The location is <install-path>\Veritas\NetBackup.

See if file is readable (but don't edit it manually).

Any chance that you can copy the file from another server?
You may want to install NBU 7.0 Admin Console on your Windows desktop/laptop and then patch to 7.0.1.
This will give you a good, default nblog.conf that you can copy to NBU master/media server while NBU is down.

 

View solution in original post

6 REPLIES 6

mph999
Level 6
Employee Accredited

Check this file :

/etc/vx/vrtslog.conf

Should look like this :

###############################################
# Caution! Do not update/modify file by hand.
# Use vxlogcfg tool to update/modify this file
###############################################
51216.Configuration=/usr/openv/netbackup/nblog.conf
51216.Names=NB,nb
50936.Configuration=/etc/vx/VxICS/icsul.conf
50936.Names=VxICS,ics

 

 

 

 

 

lanira_1509
Level 4

@mph999

Thank for your reply.
 

/etc/vx/vrtslog.conf

==> this is a Linux's environment, isn't it ?

Can you tell me the equivalent in Windows ?

Thank you very much !

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

nblog.conf may be corrupt. 
The location is <install-path>\Veritas\NetBackup.

See if file is readable (but don't edit it manually).

Any chance that you can copy the file from another server?
You may want to install NBU 7.0 Admin Console on your Windows desktop/laptop and then patch to 7.0.1.
This will give you a good, default nblog.conf that you can copy to NBU master/media server while NBU is down.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

vrtslog.conf is registry entry on Windows.

See: http://www.symantec.com/docs/TECH210786

lanira_1509
Level 4

Hi,

As Marianne said, get the nblog.conf from another media which is working perfect,

put on the defected master server, reboot services. everything is OK.

Thank you very much to everybody !

this is not working for windows & ever aritcle