Problem with Unified Logging

[Vijay_K_Gera]

Hello,

Since last few days we are facing issues with our Netbackup Drives getting fulled. While we were able to delete the logs from the Netbackup\Logs directory but the logs are getting created quite fastly.

So I thought of changing the Unified Logging for our nb variables but unable to. Is that a problem with our nblog.conf ?

See this.

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o 118 -l
Configuration settings for originator 118, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\nbrb\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames = nbrb
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResource = nbrb
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = nbrb
NtEventLogCategory = 0
LogFileSDDL = (null)

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -a -p 51216 -o 118 -s DebugLevel=
0 -s DiagnosticLevel=0

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o 118 -l
Configuration settings for originator 118, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\nbrb\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames = nbrb
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResource = nbrb
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = nbrb
NtEventLogCategory = 0
LogFileSDDL = (null)

This is happening for nbrb,nbpem,nbjm & nbemm. We have tried restarting NB Services multiple times but with no luck. Any advise. ?

[Marianne]

Probably dumb question... but did you open cmd with 'Run As Administrator'?

I would personally change all unified logging to minimum levels:

vxlogcfg -a -p 51216 -o Default -s DebugLevel=0 -s DiagnosticLevel=0 

Verify with:
vxlogcfg -p 51216 -o Default -l 

[sdo]

You may have the default set, or you may have other VxUL OIDs with high levels of logging.

What do these commands show:

1) First check, list and understand what your default debug and diag levels are:

> vxlogcfg -l -p 51216 -o Default | findstr /i "debug diag"
 

2) Then list all OIDNames, debug and diag levels - AND - look for an OIDName with logging levels different to the defaut:

> for /f "tokens=1" %a in ('vxlogcfg -l -p 51216') do (vxlogcfg -l -p 51216 -o %a | findstr /i "oidnames debug diag")

[Nicolai]

Agree with Marianne about the default loggin level. You can have Netbackup clean-up its own logs by using

vxlogmgr --del -p 51216 -e '05/05/2015 12:00:00 PM'

This command will delete all logs created before May the 5.th

More info about loggin can be found in :

NetBackup Unified and VX Logs and Troubleshooting

http://www.symantec.com/docs/TECH75805

[Vijay_K_Gera]

@ Nicolai. That would be a manual task everything which I would like to eliminate by decreasing the logging. Working on Marianne & sdo advise @ the moment.

[sdo]

Nicolai's command is a useful one to add to uour own notes, to keep in your tool box so to speak - as it can be a quick fix when space runs dangerously low.

[Vijay_K_Gera]

@ Marianne. Its not working unfortunately. See this.

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o Default -l
Configuration settings for originator 112, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames =
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -a -p 51216 -o Default -s DebugLe
vel=0 -s DiagnosticLevel=0

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -p 51216 -o Default -l
Configuration settings for originator 112, of product 51,216...
LogDirectory = D:\Veritas\NetBackup\logs\
DebugLevel = 1
DiagnosticLevel = 6
DynaReloadInSec = 0
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 51200
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
OIDNames =
AppMsgLogging = ON
L10nLib = D:\Veritas\NetBackup\bin\vxextwincat_1.dll
L10nResourceDir = D:\Veritas\NetBackup\resources
NtEventLogSourceName = Application
NtEventLogCategory = 0
LogFileSDDL = (null)

[Vijay_K_Gera]

@all. I ran as admin. Here are the results

C:\Documents and Settings\xvgera4>vxlogcfg -l -p 51216 -o Default | findstr /i "
debug diag"
DebugLevel = 1
DiagnosticLevel = 6

the Next o/p is quite big. Do you really need that ?

[Nicolai]

DebugLevel = 1, DiagnosticLevel = 6 is the  default. Do do not want to lower Diagnostic too low as you may not catch essential messages in the logs.

###############################################################################
#  Default Settings for all NetBackup Originator Identifiers (OIDs)
###############################################################################

Default.LogDirectory=/usr/openv/logs
Default.LogFilePermissions=664
Default.L10nLib=/usr/openv/lib/libvxexticu
Default.L10nResourceDir=/usr/openv/resources
Default.AppMsgLogging=ON
Default.DiagnosticLevel=6
Default.DebugLevel=1

[Marianne]

Similar post a couple of months ago:

Unified logging settings cannot be changed 

The solution was to copy nblog.conf from another server.

Another one: 

Can't Reduce Logging Level 

[Vijay_K_Gera]

@ Nicolai. Can do if that works. But it is not at all getting changed . Does that means a corrupt nblog.conf ?

[sdo]

Yes, it will change your VxUL logging configuration, but then you are currently unable to amend your VxUL logging configuration - so, you don't really have a choice, unless you want to leave it in a broken state.

Yes, it sounds as if your nblog.conf file was corrupted, and this is usually as a result of a manual edit.

My advice, save a copy of your broken file before you overwrite it.  Then diff (in Windows use the 'fc' command) to compare what's different between your old broken file, and the newly copied (hopefully working file).

[Nicolai]

Please explain - what is not getting changed ?

Even with default logging level some debug logs are still being written, but it should not impact normal operations.

[Vijay_K_Gera]

Thanks Marianne for chasing. Apologies as I couldn't update on this forum.

I am trying to get the nblog.conf updated as this looks like being corrupted at the moment. Would be updating this forum as soon as I am able to get a window for NB restart.

Thanks for all the support.

[Vijay_K_Gera]

No Luck. I have updated the nblog.conf today supplied by Symantec which was copied after stopping the Netbackup Services and removing all the copies of nblog.conf from the <Install_Path>\Veritas\NetBackup\ folder.

Still unable to modified the Settings here.

Any further clue ?

[RoyScott]

Can you post your nblog.conf?

I see you trying to set the default levels but each OID can be set seperatly as well.

For example if you look in your nblog.conf a OID 111 that will use the defaults will look like:

# 111. Enterprise Media Manager
111.L10nResource=nbemm
111.NtEventLogSourceName=nbemm
111.OIDNames=nbemm
111.LogDirectory=nbemm

After setting OID 111 with vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6

# 111. Enterprise Media Manager
111.L10nResource=nbemm
111.NtEventLogSourceName=nbemm
111.OIDNames=nbemm
111.LogDirectory=nbemm
111.DebugLevel=6
111.DiagnosticLevel=6
111.AppMsgLogging=ON

To remove that setting for OID 111 and tell it to respect the defaults run:

vxlogcfg -r -p 51216 -o 111 -s DebugLevel=0 -s DiagnosticLevel=0

If you have other OID's to change you will want to remove or set them one at a time

[Vijay_K_Gera]

Hello Roy,

This is already done. 

I mean trying to change the setting individually. The results must be there in the forum itself.

nblog.conf is supplied by Symantec. Do you need a copy of that ?

Thanks

[RoyScott]

A posted copy would be nice only as a method of confirming all of the unified logging settings.

[watsons]

There is something missing here...

When you said you did this: 

C:\Documents and Settings\xvgera4>vxlogcfg.cmd -a -p 51216 -o Default -s DebugLevel=0 -s DiagnosticLevel=0

I didn't see any output at all. Whereas a succesful run will give you an output like this:

C:\> vxlogcfg -p nb -o Default -a -s DebugLevel=1
The configuration settings were added successfully.

With no output I believe no change is going into nblog.conf. What I suspect is that you have another vxlogcfg.cmd in your path setting which supersedes the local one, which maybe incorrect. Try to search through your filesystem to look for duplicate files and ensure only the correct vxlogcfg.cmd is there.

[Marianne]

Good point! Check for binary file size and compare with another machine.