Absent Member.. Absent Member..
Absent Member..

[ST OMU] Which command has higher precedence to control the System.xx files sizes?

Which command has higher precedence to control the System.xx files sizes, the log.cfg file or the name space xpl.log.OvLogFileHandler?



Can the number of /var/opt/OV/log/System.txt backup files be increased or the size of each file increased from 1Mb to 2Mb before the file rolls?


HPOM error and warning log information are logged to the System.txt and System.bin files.

On Unix : /var/opt/OV/log directory.
On Windows : \%OvDataDir%\log directory.

There may also be other files with names :

System.txt.001, System.txt.002 right through to System.txt.009.
System.bin.001, System.bin.002 right through to System.bin.009.

By default, the size of each file is 1Mb in size and there are up to 10 files.
The files are automatically rotated, preserving the 10 most recent files.



There are two different solutions for this issue.

The two solutions offered are as follows:

1) To vary the number of files or size of each System.txt, edit the following files :

On Unix : /var/opt/OV/conf/xpl/log/log.cfg
On Windows : %OVDataDir%\conf\xpl\log\log.cfg



BinSizeLimit=1000000  - Each System.bin file is 1Mb.
BinFileLimit=10 - The maximum number of System.bin files.
TextSizeLimit=1000000 - Each System.bin file is 1Mb
TextFileLimit=10 - The maximum number of System.txt files.

2) The XPL default logging policy for all OV components is controlled via the log.cfg file found at <DataDir>/conf/log (normally /var/opt/OV/conf/xpl/log/log.cfg). 

The parameters to control the file sizes are:

BinSizeLimit=n (bytes) - Set the maximum size of the bin log file to n bytes before it "rolls" to the next file.
Default is 1000000 (bytes).

TextSizeLimit=n - Idem, but applied to the text file

The ones to control the number of logging files are:

BinFileLimit = n - Set the maximum number of bin log file instances to generate before removing oldest files.
Default is 10.

TextFileLimit = n - idem for text log file instances

Other available parameters are:

Turns logging via syslog off and on.
It has no effect on Windows systems.
Default is off.

Turns logging via NT Event log off and on. It has no effect on UNIX systems.
Default is off.

Turns proprietary binary logging off and on. This must not be turned off as it is the primary logging capability for OpenView products.

Turns locale-specific text logging off and on. Turning this on causes the logging libraries to write a locale-specific log in human-readable format. Default is on.

Controls OVO message bridging – OVO error messages will be generated if enabled. Default is empty (application-specific).

The default options to all the above apply if the configuration is invalid or not found or the configured value is empty.


Which command has higher precedence?:

*         The config variables in "xpl.log.OvLogFileHandler" namespace can be used to set defaults during installations and as part of Content of agent profile file passed with the installer.
*         Both methods have control over System.txt/bin files and sizes.
*         The config variables in "xpl.log.OvLogFileHandler" namespace are made to have a higher precedence than the values in log.cfg file while logging into System.txt /bin files.

This is documented in the following KCS document: http://support.openview.hp.com/selfsolve/document/KM00893193


HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you liked it I would appreciate KUDOs.
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.