cancel
Showing results for 
Search instead for 
Did you mean: 

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

yhbg
Level 4

Running NetBackup 7.5.0.3 on RHEL 5.8, HP G6, Master Media server, get the following error:

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

On the client:

# cat vrtslog.conf
###############################################
# 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

 

On the Master server:

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

 

Both servers have /usr/openv/netbackup/nblog.conf.

5 REPLIES 5

Nicolai
Moderator
Moderator
Partner    VIP   

Copy over the vrtslog.conf from another client.

This is also suggested in this thread : 

https://www-secure.symantec.com/connect/forums/error-occurred-during-initialization-could-not-read-logging-configuration-file-0

Marianne
Level 6
Partner    VIP    Accredited Certified

Has anyone manually changed this file?

This is our master server's vrtslog.conf (RHEL NetBackup 7.5.0.4):

 

>cat /etc/vx/vrtslog.conf
###############################################
# 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
56413.Configuration=/opt/VRTSrm/rmlog.conf
56413.Names=RM,rm
50936.Configuration=/etc/vx/VxICS/icsul.conf
50936.Names=VxICS,ics
 
(File was not changed when 7.5.0.4 was installed - still has original NBU installation date as timestamp.)
 
Please also check contents of nblog.conf.
I have seen this file getting corrupted when master server's NBU filesystem filled up.
We stopped NBU and copied the file from a media server. All fine after that. 

yhbg
Level 4

@Marianne, No one has changed this file.  When you say check nblog.conf, what am I looking for?

Thanks....

yhbg
Level 4

@Nicolai, each of my customers is getting this error.

Marianne
Level 6
Partner    VIP    Accredited Certified

I have attached a default nblog.conf file as a .txt file in this post: https://www-secure.symantec.com/connect/forums/storage-life-cycle-manager#comment-7784991