WebLogic Server doesn't set log file permissions to 022 even after changing umask value in startWeblogic.sh script

(Doc ID 1356806.1)

Last updated on DECEMBER 08, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Mar-2015***


The permissions umask value defined at OS level for the log files is not being picked up on WLS 10.3.5. Even after changing the umask value to 022 in startWeblogic.sh script, it doesn't work. Changing the umask in startWebLogic.sh does NOT work. Managed servers continue to have their logs created with permissions of 640.

Managed servers are on remote servers using Node Manager.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms