Policy Server stop working when smaccess.log is not accessible
search cancel

Policy Server stop working when smaccess.log is not accessible

book

Article ID: 203087

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER

Issue/Introduction

An application is reading the smaccess.log file, but it allocate it disabling the policy server to access it.

During this time the policy server stops to work and the smps.log reports the message:   

ERROR:[sm-Server-00940] Reject s3/r3 : Failed to write access log]

Is there a way to disable this behavior?

 

Environment

Release : 12.8.03

Component : SITEMINDER -WEB AGENT FOR APACHE

Resolution

There is no way to disable this behavior.

It seems as if the application reading smaccess.log is locking it for write. This should not be allowed as it is an audit log for siteminder so nothing else should write to it. Consider copying the actual smaccess.log somewhere and then have the application read the copy.

You could also log an idea for ignoring failed writes to smaccess.log:

https://knowledge.broadcom.com/external/article?articleId=39337