[jboss-jira] [JBoss JIRA] (WFCORE-3355) logging subsystem should skip if directories can't be listed
Janine Eichler (JIRA)
issues at jboss.org
Thu Oct 12 08:23:00 EDT 2017
[ https://issues.jboss.org/browse/WFCORE-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janine Eichler updated WFCORE-3355:
-----------------------------------
Affects Version/s: (was: 2.1.0.Final)
> logging subsystem should skip if directories can't be listed
> ------------------------------------------------------------
>
> Key: WFCORE-3355
> URL: https://issues.jboss.org/browse/WFCORE-3355
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Affects Versions: 3.0.5.Final
> Reporter: Janine Eichler
> Assignee: James Perkins
>
> Following condition:
> - a mounted volume within the jboss.log.dir
> - the mounted volume is an ext filesystem
> as a consequence a lost+found directory is automatically created, owned by root.root, permissions are 700.
> Now when you spin up a jboss instance, the logging directory is recursively scanned, due to the lost+found folder the logging subsystem throws the error https://github.com/wildfly/wildfly-core/blob/802d4dfcf58e24030d6c43ed2b0102a0c3620ae1/logging/src/main/java/org/jboss/as/logging/logging/LoggingLogger.java#L909
> using the cli or mgmt console to read the log is then not possible.
> i tested it using the EAP7 (so wildfly-logging-2.1.2-final-redhat.jar), but also built the 3.0.6-SNAPSHOT and used this jar in the logging subsystem to check whether it may have been already fixed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list