07-18-2011 01:52 AM
does anyone know how to turn this off? the wingui folder in the logs directory keeps filling up. The triuble shooting tab on the media server has all the debug levels set to zero. I have been handed this server by someone else so am not sure what he did to have wingui log overflowing all the time.
does anyone know?
Solved! Go to Solution.
11-08-2011 09:26 AM
Although the settings in nblog.conf were correct, there were two old nbconsole processes still running on the media server which had picked up the old settings and were merrily logging away to wingui.
So killed nbconsole processes and log files stopped. Didn't start logging when I started console again. Something to watch out for on windows!!
07-18-2011 02:07 AM
Which one's that?
07-18-2011 02:08 AM
I'm with Andy on that, but if it is indeed a NetBackup log, simply delete it. NetBackup only logs to folders that exist.
07-18-2011 02:10 AM
\VERITAS\Netbackup\logs\wingui
keeps filling up on media server - driving me nuts
07-18-2011 02:11 AM
can't delete it - it's connstatntly writing data to it. No one know this log folder?
07-18-2011 02:16 AM
Is that the actual log or a folder with logs in it?
If the former what sort of contents ? If the latter what sort of file names?
Only reference I can find on KB (but that's moot!) for "wingui" references unified logging .....
***EDIT***
There's plenty on the KB regarding controlling of NetBackup logs:
DOCUMENTATION: Best Practice recommendations for enabling and gathering NetBackup (tm) logging
http://www.symantec.com/business/support/index?page=content&id=TECH47372
DOCUMENTATION: How to configure Veritas NetBackup (tm) to write Unified and\or Legacy log files to a different directory
http://www.symantec.com/business/support/index?page=content&id=TECH45907
& plenty of links within those to other useful T/N's.
07-18-2011 02:24 AM
folder with logs in - logs are in .log format writes about 50mb every 20 minutes
07-18-2011 02:39 AM
- but what type of name?
Similar to this? (Per one of the T/N's I quoted earlier)
"Unified logs are written to the /usr/openv/logs directory on UNIX systems or the <install_path>\NetBackup\logs directory on Windows systems. An example of a log file that would be generated would be: 51216-111-990921226-060318-0000000000.log"
07-18-2011 02:41 AM
Hi,
Andy is correct it is a unified log. Go to /usr/openv/netbackup/nblog.conf and look for OID 263 and set both debug and diagnostic to 0.
07-18-2011 02:59 AM
Nice post from Martin that I had bookmarked (a year later, not sure if it ever got published?):
https://www-secure.symantec.com/connect/forums/how-activate-logs-client#comment-4094011
07-18-2011 03:54 AM
using commnd vxlogcfg -r -p 51216 -o 263
checked nblog.conf file and settings have gone for wingui - but it's still logging - grrrrrrrrr
07-18-2011 04:51 AM
Hmm, I would stop services, edit the nblog.conf manually, then restart. I've seen vxlogcfg fail to work on quite a few occasions.
07-18-2011 01:59 PM
Andy,
That looks like TECH75805.
NetBackup Unified and VX Logs and Troubleshooting
http://symantec.com/docs/TECH75805
07-18-2011 11:20 PM
Had a quick browse on the KB, but we know how productive that can be!
11-08-2011 02:46 AM
I've done everything on here - changed conf file, set debug and diag to zero, stopped and started services. yet the media server is constantly filling up with large log files in \netbackup\logs. All start with 51216-263* been to Symantec and they have just suggested the above which I have done but I just can't stop it logging. Can anyone help?
11-08-2011 04:10 AM
"been to Symantec"
Let the engineer know that the advice/suggestion did not work and ask for your case to be escalated.
11-08-2011 09:26 AM
Although the settings in nblog.conf were correct, there were two old nbconsole processes still running on the media server which had picked up the old settings and were merrily logging away to wingui.
So killed nbconsole processes and log files stopped. Didn't start logging when I started console again. Something to watch out for on windows!!