XOS: Audit records are generated even when audit is set to OFF
Check the processing time for the ruling against the PROCESSING_TIMEOUT value in the OSCONF.
If the value of this keyword is set to a nonzero number and XOS takes longer than this value for responding to a request, then XOS will audit the request regardless of audit settings in the OSCONF and OSACL.
Syntax:
PROCESSING_TIMEOUT <seconds>
Example:
PROCESSING_TIMEOUT 5
The processing time for a ruling can be checked by running an XOS_REPORT covering the time period of the unexpected audit with the Sort Order (option O.) set to ELAPSED. This will display the elapsed amount of time for each ruling to be made. Example report output below:
1 requests processed in 4.639175 <--processing time in seconds
4.626166 1 2021-03-27 23:50:51 S $VDO35
\NODE.$VHCV1 99 102 LOR.XXTV
4.626166 \NODE.$VDO35:1101249257 $VOL.SUBVOL.EXAMPLE $VDO35
POGROUP GUARDIAN-MANAGE-OWN-PROCESSES ACCESS YES $VSO25
If persistent, longer ruling times indicate additional XOS processes may be needed . If XOS is not currently installed as a multi-threaded SEEP this should be considered. If already installed as multi-threaded you can consider increasing the number of XOS processes.
For more information on installing XOS as a multi-threaded SEEP and changing the number of processes please see: https://xypro.my.salesforce.com/articles/Knowledgebase_Article/XOS-What-is-the-recommended-number-of-processes-when-XOS-is-installed-as-a-multi-threaded-SEEP
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.
Related Articles
XOS: NORECORD IGNORED causing frequent audit rollover
If you want to get rid of ?IGNORED?s, set the AUDIT-NORECORD keyword to OFF in the OSCONF. Additionally, depending on whether or not you want NORECORD audits for non-IGNORE entries, just setting AUDIT_NORECORD OFF wouldn't work. You would also need a ...
XOS: Disk that holds XOS audit is running out of space
A. Create more disk space or change audit location in OSCONF to location with more space OR B. Decrease the extent size of the audit files (Modify OSCONF to set extents smaller) Steps to modify OSCONF and update configuration: 1. Set new parameters ...
XOS: Audit of $:?? plus additional characters are showing up in the audit files.
Fix: Include the MASK RE:"^\$\:" in the POGROUP The following example suppresses audits for $:?? processes: POGROUP NO-POGROUP-AUDITS DESCRIPTION "Stop logging NORECORDS" ! *** Selection Criteria *** MASK RE:"^\$:" ! *** Access Granted *** ACL ...
XOS: Audit File Error 45 - Missing Sequence Numbers
If a disk file name is specified for the AUDIT and no disk file exists, the file is created with the default format of type E, rec 4000, block 4096, primary extent size 300 pages, secondary extent size 300 pages and maxextents set to 16. When an ...
XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?
Below are two possible reasons "\unknown" is seen in a XOS Audit Report for node name: A. When the EXPLICIT_NODES is OFF and you try to execute a FUP program on \one node to purge a file on another you see \UNKNOWN on the SUBJECT-SYSTEM field as ...