Log files might not be created when using the MaxLogFileSize directive
 Technote (troubleshooting)
 
Problem(Abstract)
For Caching Proxy, log file creation might fail with a "Can not open the <Log File Name>" error when using the MaxLogFileSize directive
 
Resolving the problem
The MaxLogFileSize directive lets you specify the maximum size of a log file. When the maximum size of the log file is reached, new log files are created with the same name and appended by an incremental integer.

On Unix and Linux platforms, the log files are not created if the permission of the directory where the log files reside does not have write permission, at least for the group under which the ibmproxy daemon runs. In other words, the log file locations for the Logging Directives in the ibmproxy.conf file must have write permission, at least for the group defined by the GroupId directive in the ibmproxy.conf file.

This is typically a problem only when the default location of the log files has been changed, or when the default UserId or GroupId directives have been changed in the ibmproxy.conf file.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
84448
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Linux
Software version: 5.0
Software edition:
Reference #: 1105983
IBM Group: Software Group
Modified date: Mar 4, 2004