Log folder growing

Hi all,

I had a long troubleshooting session with Symantec in regards to our VMware farm and it looks like logging still enable as I see abnormal size of VxMS log here C:\Program Files\Common Files\VERITAS\VxMS\Logs

How do I disable it?

1 Solution

Accepted Solutions
Accepted Solution!

Refer to this

Refer to this technote

 

DOCUMENTATION: How to turn up logging for VxMS (Veritas Federated Mapping Service)

Problem



DOCUMENTATION: How to turn up logging for VxMS (Veritas Federated Mapping Service)


Solution



To enable logging of the VxMS Mapping service on Windows:


1. Click Start > Run and enter regedit.
2. Create a backup of your current registry (File > Export)
3. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ VERITAS \ VxMS
4. Change the Logging DWORD value to 7580 in Hexadecimal.  The value will actually show up on the Registry as 0x00007580 (30080)

The next time VxMS is run, it will create a log (ex: VxMS-1832-MMDDYY.log).  The log is in C:\Program Files\Common Files\VERITAS\VxMS\Logs\.  The Logs directory will be created automatically if it does not exist.
 

 

VxMS uses the following macros to govern what gets logged and what doesn’t. The registry values to be set are bitwise OR of one or more of these values:

#define VFMDBG_DEBUG 0x80
#define VFMDBG_INFO 0x100
#define VFMDBG_WARN 0x200
#define VFMDBG_TRC_TOP 0x400
#define VFMDBG_TRC_LOW 0x800
#define VFMDBG_PARAM_IN 0x1000
#define VFMDBG_PARAM_OUT 0x2000
#define VFMDBG_PARAM_FULL 0x4000
 

Based on the table above, we can use different hex values to change what is output to the logs.

For example, 0x7580 is a bitwise OR of (VFMDBG_PARAM_FULL, VFMDBG_PARAM_OUT, VFMDBG_PARAM_IN, VFMDBG_TRC_TOP, VFMDBG_INFO and VFMDBG_DEBUG).


For reduced logging use value 0x3400

For general purposes use value 0x7400

For verbose logging use value 0x7580


Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

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

 

View solution in original post

2 Replies
Accepted Solution!

Refer to this

Refer to this technote

 

DOCUMENTATION: How to turn up logging for VxMS (Veritas Federated Mapping Service)

Problem



DOCUMENTATION: How to turn up logging for VxMS (Veritas Federated Mapping Service)


Solution



To enable logging of the VxMS Mapping service on Windows:


1. Click Start > Run and enter regedit.
2. Create a backup of your current registry (File > Export)
3. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ VERITAS \ VxMS
4. Change the Logging DWORD value to 7580 in Hexadecimal.  The value will actually show up on the Registry as 0x00007580 (30080)

The next time VxMS is run, it will create a log (ex: VxMS-1832-MMDDYY.log).  The log is in C:\Program Files\Common Files\VERITAS\VxMS\Logs\.  The Logs directory will be created automatically if it does not exist.
 

 

VxMS uses the following macros to govern what gets logged and what doesn’t. The registry values to be set are bitwise OR of one or more of these values:

#define VFMDBG_DEBUG 0x80
#define VFMDBG_INFO 0x100
#define VFMDBG_WARN 0x200
#define VFMDBG_TRC_TOP 0x400
#define VFMDBG_TRC_LOW 0x800
#define VFMDBG_PARAM_IN 0x1000
#define VFMDBG_PARAM_OUT 0x2000
#define VFMDBG_PARAM_FULL 0x4000
 

Based on the table above, we can use different hex values to change what is output to the logs.

For example, 0x7580 is a bitwise OR of (VFMDBG_PARAM_FULL, VFMDBG_PARAM_OUT, VFMDBG_PARAM_IN, VFMDBG_TRC_TOP, VFMDBG_INFO and VFMDBG_DEBUG).


For reduced logging use value 0x3400

For general purposes use value 0x7400

For verbose logging use value 0x7580


Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

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

 

View solution in original post

thanks for response, mouse

thanks for response, mouse let me check this technote