[jira] [Comment Edited] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j
[
https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651243#comment-17651243
]
Markus Jelsma edited comment on NUTCH-2978 at 12/22/22 11:33 AM:
-
Ah nope, this is not it. Parse-tika throws lots of errors and stack traces,
although it does work. We now get:
{color:#00}java.util.ServiceConfigurationError:
org.apache.logging.log4j.spi.Provider:
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype
{color}
{color:#00}There are no multiple versions of the same logging JARs anywhere
on the classpath.{color}
was (Author: markus17):
Ah nope, this is not it. Parse-tika throws lots of errors and stack traces,
although it does work. We now get:
{color:#00}java.util.ServiceConfigurationError:
org.apache.logging.log4j.spi.Provider:
org.apache.logging.log4j.core.impl.Log4jProvider not a subtype{color}
> Move to slf4j2 and remove log4j1 and reload4j
> -
>
> Key: NUTCH-2978
> URL: https://issues.apache.org/jira/browse/NUTCH-2978
> Project: Nutch
> Issue Type: Task
>Reporter: Markus Jelsma
>Priority: Major
> Attachments: NUTCH-2978-1.patch, NUTCH-2978-2.patch,
> NUTCH-2978-3.patch, NUTCH-2978-any23.patch, NUTCH-2978.patch
>
>
> I got in trouble upgrading some dependencies and got a lot of LinkageErrors
> today, or with a Tika upgrade, disappearing logs. This patch fixes that by
> moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old
> log4j -> reload4j.
>
> This patch fixes it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j
[ https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644838#comment-17644838 ] Markus Jelsma edited comment on NUTCH-2978 at 12/8/22 2:34 PM: --- Ah, well. I also tried a Tika parsing fetcher of a vanilla 1.20 Nutch with just this patch, and the generator patch. It works! Not sure why our parser stuff fails, but at least Nutch' stuff is working! But we both use a LoggerFactory.getLogger invocation, the original TikaParser invocation works, mine doesn't. was (Author: markus17): Ah, well. I also tried a Tika parsing fetcher of a vanilla 1.20 Nutch with just this patch, and the generator patch. It works! Not sure why our parser stuff fails, but at least Nutch' stuff is working! > Move to slf4j2 and remove log4j1 and reload4j > - > > Key: NUTCH-2978 > URL: https://issues.apache.org/jira/browse/NUTCH-2978 > Project: Nutch > Issue Type: Task >Reporter: Markus Jelsma >Priority: Major > Attachments: NUTCH-2978.patch > > > I got in trouble upgrading some dependencies and got a lot of LinkageErrors > today, or with a Tika upgrade, disappearing logs. This patch fixes that by > moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old > log4j -> reload4j. > > This patch fixes it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NUTCH-2978) Move to slf4j2 and remove log4j1 and reload4j
[ https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644825#comment-17644825 ] Markus Jelsma edited comment on NUTCH-2978 at 12/8/22 2:12 PM: --- This morning i saw one of our internal projects spewing the same error as any23, it was quickly remedied by upgrading a dependency further down the line. Not sure if this will go as easy with the any23 plugin, i'll take a look Regarding running on Hadoop, I just ran a patched 1.20 CrawldbReader job on a 3.3.4 cluster, i ran flawless! Encouranged by the result i quickly ran a generate, followed by a fetch. The fetch failed due to LinkageError in our parser plugin, similar as parse-tika. Too bad. A local indexchecker runs fine, an indexchecker using a job file fails with the same error. Removing all reload4j references is not solving it, as expected. Not sure what to do now. was (Author: markus17): This morning i saw one of our internal projects spewing the same error as any23, it was quickly remedied by upgrading a dependency further down the line. Not sure if this will go as easy with the any23 plugin, i'll take a look Regarding running on Hadoop, I just ran a patched 1.20 CrawldbReader job on a 3.3.4 cluster, i ran flawless! Encouranged by the result i quickly ran a generate, followed by a fetch. The fetch failed due to LinkageError in our parser plugin, similar as parse-tika. Too bad. A local indexchecker runs fine, an indexchecker using a job file fails with the same error. > Move to slf4j2 and remove log4j1 and reload4j > - > > Key: NUTCH-2978 > URL: https://issues.apache.org/jira/browse/NUTCH-2978 > Project: Nutch > Issue Type: Task >Reporter: Markus Jelsma >Priority: Major > Attachments: NUTCH-2978.patch > > > I got in trouble upgrading some dependencies and got a lot of LinkageErrors > today, or with a Tika upgrade, disappearing logs. This patch fixes that by > moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old > log4j -> reload4j. > > This patch fixes it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
