[ 
https://issues.apache.org/jira/browse/LOG4NET-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204222#comment-17204222
 ] 

Davyd McColl commented on LOG4NET-653:
--------------------------------------

Looks like it's related to 
[https://issues.apache.org/jira/projects/LOG4NET/issues/LOG4NET-652] – 
[~andy250] can you confirm?

> BufferingAppenderSkeleton.Append throws exception on arm64 linux
> ----------------------------------------------------------------
>
>                 Key: LOG4NET-653
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-653
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0.10
>         Environment: Ubuntu 18.04.4 LTS Linux 4.9.140-tegra aarch64 on nvidia 
> jetson xavier nx (arm64)
>            Reporter: Andrzej Kowal
>            Priority: Major
>
> I have a .netcore 3.1 console app which works correctly with log4net 2.0.8. 
> After upgrading this package 
> [https://www.nuget.org/packages/Microsoft.Extensions.Logging.Log4Net.AspNetCore/]
>  to latest version I also had to upgrade to log4net 2.0.10. After that 
> upgrade I started getting errors:
>  
> 2020-09-28 15:17:24,191 [ERROR] MyProject.ElasticsearchAppenderBase - 
> System.PlatformNotSupportedException: Windows Principal functionality is not 
> supported on this platform.
>  at System.Security.Principal.WindowsIdentity.GetCurrent()
>  at log4net.Core.LoggingEvent.get_UserName()
>  at log4net.Core.LoggingEvent.FixVolatileData(FixFlags flags)
>  at log4net.Core.LoggingEvent.set_Fix(FixFlags value)
>  at log4net.Appender.BufferingAppenderSkeleton.Append(LoggingEvent 
> loggingEvent)
>  at MyProject.ElasticsearchAppenderBase.Append(LoggingEvent loggingEvent) in 
> /home/MyProject/Common/SharedPublic/Logging/Elasticsearch/ElasticsearchAppenderBase.cs:line
>  87
> The same error happens on 2.0.11.
> The ElasticsearchAppenderBase is my custom class built on top of 
> BufferingAppenderSkeleton.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to