[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385697#comment-16385697
]
Shawn Heisey commented on SOLR-7887:
------------------------------------
Patch didn't want to apply for me on my desktop. Moved it to a Linux machine,
and then it worked. Building the server target and then running "bin/solr
start", I see the same exception, but before that, the first two errors are
different. I trimmed most of the stacktraces out. It acts like the property
substitution isn't working properly ... I think the first message came directly
from Java file code.
I couldn't figure out which xml config file was being used. Ultimately by
experimenting I learned that it is using the one at
server/scripts/cloud-scripts/log4j2.xml ... which doesn't seem right.
{noformat}
2018-03-05 00:01:38,054 main ERROR Unable to create file
${sys:solr.solr.home}/../logs/solr.log java.io.IOException: No such file or
directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:1012)
at
org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory.createManager(RollingFileManager.java:628)
{noformat}
{noformat}
2018-03-05 00:01:38,063 main ERROR Could not create plugin of type class
org.apache.logging.log4j.core.appender.RollingFileAppender for element
RollingFile: java.lang.IllegalStateException: ManagerFactory
[org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@545997b1]
unable to create manager for [${sys:solr.solr.home}/../logs/solr.log] with
data
[org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@4cf4d528[pattern=${sys:solr.solr.home}/../logs/solr.%i.log.gz,
append=true, bufferedIO=true, bufferSize=8192,
policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy,
SizeBasedTriggeringPolicy(size=4194304)]),
strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null,
layout=%d{yyyy-MM-dd HH:mm:ss.SSS} %-5p (%t) [%X{collection} %X{shard}
%X{replica} %X{core}] %c{1.} %m%n, filePermissions=null, fileOwner=null]]
java.lang.IllegalStateException: ManagerFactory
[org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@545997b1]
unable to create manager for [${sys:solr.solr.home}/../logs/solr.log] with
data
[org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@4cf4d528[pattern=${sys:solr.solr.home}/../logs/solr.%i.log.gz,
append=true, bufferedIO=true, bufferSize=8192,
policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy,
SizeBasedTriggeringPolicy(size=4194304)]),
strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null,
layout=%d{yyyy-MM-dd HH:mm:ss.SSS} %-5p (%t) [%X{collection} %X{shard}
%X{replica} %X{core}] %c{1.} %m%n, filePermissions=null, fileOwner=null]]
at
org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:115)
{noformat}
> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
> Key: SOLR-7887
> URL: https://issues.apache.org/jira/browse/SOLR-7887
> Project: Solr
> Issue Type: Task
> Affects Versions: 5.2.1
> Reporter: Shawn Heisey
> Assignee: Varun Thacker
> Priority: Major
> Attachments: SOLR-7887-WIP.patch, SOLR-7887-eoe-review.patch,
> SOLR-7887-eoe-review.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final
> logging destination, so the admin UI has a log watcher that actually uses
> log4j and java.util.logging classes. That will need to be extended to add
> log4j2. I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j. Figuring out exactly which
> jars need to be in the lib/ext directory will take some research.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
