cancel
Showing results for 
Search instead for 
Did you mean: 

logs level stuck at high causing disk space to fill

I enabled logging assistant. Once I got the logs I wanted to delete these logging entries in logging assistant. It came up with an error and I couldn't delete it. I had to try many times, shutdown services and then only I was able to delete it. I checked my log level is set to minimum. Yet one of the clients logs keeps filling up. Any ideas on how to find where and why logs are filling up? Regards.
8 Replies

Re: logs level stuck at high causing disk space to fill

I assume you already checked the logging level from the host properties from NetBackup console, if yes then check using the below command :

 

 

vxlogcfg -p 51216 -o Default -l  > to print the config

 

It should show you debug level at 1 and diagnostic level at 0 if not then you need to change using below command:

 

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

 

 

Let me know how it goes.

Re: logs level stuck at high causing disk space to fill

# To reset all logging levels for vxlog on the master
  vxlogcfg -a -p 51216 -o ALL -s DebugLevel=0 -s DiagnosticLevel=0

 

NetBackup 8.3.0.1 on Solaris 11, writing to Data Domain 9800 6.2.1.0
duplicating via SLP to LTO5 in SL8500 via ACSLS

Yet one of the clients logs

Yet one of the clients logs keeps filling up.

 

NetBackup Management > Host Properties > Clients > (select client) > Properties > Logging

  also under Windows Client > Client Settings > Additional Logging Levels

Re: logs level stuck at high causing disk space to fill

Hi Mujtaba,

The print showed DiagnosticLevel at 6.

I changed it to 0. Will check and confirm if it works out.

Regards.

Re: logs level stuck at high causing disk space to fill

DiagnosticLevel SHOULD be 6 - that is default.

DebugLevel should be 1  - that is default.

 

Re: logs level stuck at high causing disk space to fill

Hi Mujtaba,

Your solution did not work as the logs are still filling up. I have multiple huge files in bpbkar folder. For now I have deleted this folder to check how it goes.

Regards.

Re: logs level stuck at high causing disk space to fill

bpbkar is not a unified log, so is unaffected by the vxlogcfg commands.

The verbose level is controlled by a VERBOSE setting in either bp.conf (unix) or registry (windows)

Re: logs level stuck at high causing disk space to fill

Hi AAK,

I am guessing this is a Windows client - if so:

  • Open up the BAR GUI
  • From the File menu select "NetBackup Client Properties"
  • Click the "Troubleshooting" tab and have a look at the "Verbose" setting there

This controls the Registry setting Martin is referring to.  The location in the Registry that this setting modifies is:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config]
  • "VERBOSE"=dword:00000000 (Mine is set to 0 because verbose is off)

Hope this helps,

Steve