You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Frank Kozuschnik (JIRA)" <ji...@apache.org> on 2018/08/02 18:28:01 UTC
[jira] [Commented] (LOG4NET-496)
RollingFileAppender.ActivateOptions throws UnauthorizedAccessException
[ https://issues.apache.org/jira/browse/LOG4NET-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567333#comment-16567333 ]
Frank Kozuschnik commented on LOG4NET-496:
------------------------------------------
This is still an issue, and I see it when two processes are running as different users, and both try to have *RollingFileAppender* write to the same log file. The first process creates the mutex successfully, but does not grant sufficient privileges for other users. Other users' processes will then get the exception and cannot write anything to the log.
There is an answer on Stackoverflow that suggests calling the Mutex constructor overflow with a MutexSecurity object that grants full "full control" to "Everyone".
[https://stackoverflow.com/a/229567]
I have tried this, and the suggestion seems to work for me.
This is the my code change in *ActivateOptions()*:
{code:java}
// initialize the mutex that is used to lock rolling
bool createdNew;
var securitySettings = new MutexSecurity();
securitySettings.AddAccessRule(new MutexAccessRule(new SecurityIdentifier(WellKnownSidType.WorldSid, null),
MutexRights.FullControl, AccessControlType.Allow));
m_mutexForRolling = new Mutex(false, m_baseFileName.Replace("\\", "_").Replace(":", "_").Replace("/", "_"),
out createdNew, securitySettings);
{code}
> RollingFileAppender.ActivateOptions throws UnauthorizedAccessException
> ----------------------------------------------------------------------
>
> Key: LOG4NET-496
> URL: https://issues.apache.org/jira/browse/LOG4NET-496
> Project: Log4net
> Issue Type: Bug
> Affects Versions: 1.2.14
> Reporter: Fabian Pachner
> Priority: Major
>
> We upgraded our Azure cloud service project from log4net 1.2.13 to 1.2.14 and received the following exception when the web roles are starting up:
> {code}
> System.UnauthorizedAccessException: Access to the path 'C__Resources_directory_9b9a1e064b78414281c81f861d0634b0.Role.Web.Frontend.DiagnosticStore_LogFiles_UI_UI_0' is denied.
> at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
> at System.Threading.Mutex.MutexTryCodeHelper.MutexTryCode(Object userData)
> at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
> at System.Threading.Mutex.CreateMutexWithGuaranteedCleanup(Boolean initiallyOwned, String name, Boolean& createdNew, SECURITY_ATTRIBUTES secAttrs)
> at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name, Boolean& createdNew, MutexSecurity mutexSecurity)
> at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name, Boolean& createdNew)
> at log4net.Appender.RollingFileAppender.ActivateOptions()
> at Base.Logging.AzureFileLogAppender.ActivateOptions() in j:\Source\Commons\Logging\AzureFileLogAppender.cs:line 95
> at log4net.Repository.Hierarchy.XmlHierarchyConfigurator.ParseAppender(XmlElement appenderElement)
> {code}
> This affects the w3wp process of the web role. A consequence of this is that file logging isn't working for that process. We didn't have that exception with log4net 1.2.13 and recognized there was a change in 1.2.14 in RollingFileAppender.ActivateOptions: A mutex is created there and that seems to lead to the mentioned exception.
> Can you tell us whether it is likely that this issue was already fixed with 1.2.15? And if so, when will this version be available via Nuget package? Thank you!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)