You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by con <co...@gmail.com> on 2009/09/08 23:37:46 UTC
Misleading log messages while deploying solr
Hi
I am deploying solr in jboss and is indexing data from db.
Everything works fine and i am getting correct response.
But the log message that is getting print in the server console, in my case
jboss, is showing status as error.
Why is this showing as ERROR, even though things are working fine.
Since in the actual production environment this causes lot of mess up with
other logs, and also misleads with this message, how can i hide this ERROR
message(if it is not really error). or can i set the log level to INFO.
11:41:19,030 INFO [TomcatDeployer] deploy, ctxPath=/solr,
warUrl=.../tmp/deploy/tmp43266solr-exp.war/
11:41:19,948 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
org.apache.solr.servlet.SolrDispatchFilter init
INFO: SolrDispatchFilter.init()
11:41:19,975 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
org.apache.solr.core.SolrResourceLoader locateInstanceDir
INFO: No /solr/home in JNDI
11:41:19,976 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
org.apache.solr.core.SolrResourceLoader locateInstanceDir
INFO: using system property solr.solr.home: C:\app\Search
11:41:19,984 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
org.apache.solr.core.CoreContainer$Initializer initialize
INFO: looking for solr.xml: C:\app\Search\solr.xml
11:41:20,084 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
org.apache.solr.core.SolrResourceLoader <init>
INFO: Solr home set to 'C:\app\Search'
11:41:20,142 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
org.apache.solr.core.SolrResourceLoader createClassLoader
INFO: Adding
'file:/C:/app/Search/lib/apache-solr-dataimporthandler-1.3.0.jar' to Solr
classloader
11:41:20,144 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
org.apache.solr.core.SolrResourceLoader createClassLoader
INFO: Adding 'file:/C:/app/Search/lib/jsp-2.1/' to Solr classloader
...........
INFO: Reusing parent classloader
11:41:21,870 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
org.apache.solr.core.SolrConfig <init>
INFO: Loaded SolrConfig: solrconfig.xml
11:41:21,909 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
org.apache.solr.schema.IndexSchema readSchema
INFO: Reading Solr Schema
11:41:22,092 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
org.apache.solr.schema.IndexSchema readSchema
INFO: Schema name=contacts schema
11:41:22,121 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
org.apache.solr.util.plugin.AbstractPluginLoader load
INFO: created string: org.apache.solr.schema.StrField
.................
--
View this message in context: http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25354654.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Misleading log messages while deploying solr
Posted by Chris Hostetter <ho...@fucit.org>.
: As per my understandings and investigations, if we disable STDERR from the
: jboss configs, we will not be able to see any STDERR coming from any of the
: APIs - which can be real error messages.
: So if we know the exact reason why this message from solr is showing up, we
: can block this at solr level or may be jboss level.
I wouldn't suggest disabling all output to STDERR, you need to look into
what options JBoss has for managine java.util.logging (aka: JUL). BY
default Solr is using JUL (via SLF4J), and I suspect that by default JUL
is logging to STDERR, and JBoss has replaced System.err with it's own
PrintStream that writes to it's own logging framework.
You need to find a way to configure JBoss to take JUL messages and direct them to it's
framework directly -- OR -- swap the SLF4J backend so that instead of
using JUL it uses whatever JBoss uses.
: > Solr is not declaring that those messages are ERRORs, solr is just logging
: > informational messages (hence then "INFO" lines) using the java logging
: > framework.
: >
: > My guess: since the logs are getting prefixed with "ERROR [STDERR]"
: > something about the way your jboss container is configured is probably
: > causing those log messages to be written to STDERR, and then jboss is
: > capturing the STDERR and assuming that if it went there it mist be an
: > "ERROR" of some kind and logging it to the console (using it's own log
: > format, hence the touble timestamps per line message)
: >
: > In short: jboss is doing this in response to normal logging from solr.
: > you should investigate your options for configuriring jboss and how it
: > deals with log messages from applications.
-Hoss
Re: Misleading log messages while deploying solr
Posted by con <co...@gmail.com>.
i downloaded and installed a fresh jboss (jboss-4.2.1.GA) and updated run.bat
and jboss-service.xml
then deployed solr war in the deploy folder.
but still it is showing the same message on jboss
startup.:confused::confused:
con wrote:
>
> Thanks Hossman
>
> As per my understandings and investigations, if we disable STDERR from the
> jboss configs, we will not be able to see any STDERR coming from any of
> the APIs - which can be real error messages.
> So if we know the exact reason why this message from solr is showing up,
> we can block this at solr level or may be jboss level.
>
> Any suggestion which points out a reason for this or a solution that hides
> these messages only is really appreciable.
>
>
> thanks
>
>
>
> hossman wrote:
>>
>>
>> : But the log message that is getting print in the server console, in my
>> case
>> : jboss, is showing status as error.
>> : Why is this showing as ERROR, even though things are working fine.
>>
>> Solr is not declaring that those messages are ERRORs, solr is just
>> logging
>> informational messages (hence then "INFO" lines) using the java logging
>> framework.
>>
>> My guess: since the logs are getting prefixed with "ERROR [STDERR]"
>> something about the way your jboss container is configured is probably
>> causing those log messages to be written to STDERR, and then jboss is
>> capturing the STDERR and assuming that if it went there it mist be an
>> "ERROR" of some kind and logging it to the console (using it's own log
>> format, hence the touble timestamps per line message)
>>
>> In short: jboss is doing this in response to normal logging from solr.
>> you should investigate your options for configuriring jboss and how it
>> deals with log messages from applications.
>>
>>
>> : 11:41:19,030 INFO [TomcatDeployer] deploy, ctxPath=/solr,
>> : warUrl=.../tmp/deploy/tmp43266solr-exp.war/
>> : 11:41:19,948 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
>> : org.apache.solr.servlet.SolrDispatchFilter init
>> : INFO: SolrDispatchFilter.init()
>> : 11:41:19,975 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
>> : org.apache.solr.core.SolrResourceLoader locateInstanceDir
>> : INFO: No /solr/home in JNDI
>> : 11:41:19,976 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
>> : org.apache.solr.core.SolrResourceLoader locateInstanceDir
>> : INFO: using system property solr.solr.home: C:\app\Search
>> : 11:41:19,984 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
>> : org.apache.solr.core.CoreContainer$Initializer initialize
>> : INFO: looking for solr.xml: C:\app\Search\solr.xml
>> : 11:41:20,084 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
>> : org.apache.solr.core.SolrResourceLoader <init>
>> : INFO: Solr home set to 'C:\app\Search'
>> : 11:41:20,142 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
>> : org.apache.solr.core.SolrResourceLoader createClassLoader
>> : INFO: Adding
>> : 'file:/C:/app/Search/lib/apache-solr-dataimporthandler-1.3.0.jar' to
>> Solr
>> : classloader
>> : 11:41:20,144 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
>> : org.apache.solr.core.SolrResourceLoader createClassLoader
>> : INFO: Adding 'file:/C:/app/Search/lib/jsp-2.1/' to Solr classloader
>> :
>> : ...........
>> : INFO: Reusing parent classloader
>> : 11:41:21,870 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
>> : org.apache.solr.core.SolrConfig <init>
>> : INFO: Loaded SolrConfig: solrconfig.xml
>> : 11:41:21,909 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
>> : org.apache.solr.schema.IndexSchema readSchema
>> : INFO: Reading Solr Schema
>> : 11:41:22,092 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
>> : org.apache.solr.schema.IndexSchema readSchema
>> : INFO: Schema name=contacts schema
>> : 11:41:22,121 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
>> : org.apache.solr.util.plugin.AbstractPluginLoader load
>> : INFO: created string: org.apache.solr.schema.StrField
>> :
>> : .................
>> : --
>> : View this message in context:
>> http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25354654.html
>> : Sent from the Solr - User mailing list archive at Nabble.com.
>> :
>>
>>
>>
>> -Hoss
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25448607.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Misleading log messages while deploying solr
Posted by con <co...@gmail.com>.
Thanks Hossman
As per my understandings and investigations, if we disable STDERR from the
jboss configs, we will not be able to see any STDERR coming from any of the
APIs - which can be real error messages.
So if we know the exact reason why this message from solr is showing up, we
can block this at solr level or may be jboss level.
Any suggestion which points out a reason for this or a solution that hides
these messages only is really appreciable.
thanks
hossman wrote:
>
>
> : But the log message that is getting print in the server console, in my
> case
> : jboss, is showing status as error.
> : Why is this showing as ERROR, even though things are working fine.
>
> Solr is not declaring that those messages are ERRORs, solr is just logging
> informational messages (hence then "INFO" lines) using the java logging
> framework.
>
> My guess: since the logs are getting prefixed with "ERROR [STDERR]"
> something about the way your jboss container is configured is probably
> causing those log messages to be written to STDERR, and then jboss is
> capturing the STDERR and assuming that if it went there it mist be an
> "ERROR" of some kind and logging it to the console (using it's own log
> format, hence the touble timestamps per line message)
>
> In short: jboss is doing this in response to normal logging from solr.
> you should investigate your options for configuriring jboss and how it
> deals with log messages from applications.
>
>
> : 11:41:19,030 INFO [TomcatDeployer] deploy, ctxPath=/solr,
> : warUrl=.../tmp/deploy/tmp43266solr-exp.war/
> : 11:41:19,948 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
> : org.apache.solr.servlet.SolrDispatchFilter init
> : INFO: SolrDispatchFilter.init()
> : 11:41:19,975 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
> : org.apache.solr.core.SolrResourceLoader locateInstanceDir
> : INFO: No /solr/home in JNDI
> : 11:41:19,976 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
> : org.apache.solr.core.SolrResourceLoader locateInstanceDir
> : INFO: using system property solr.solr.home: C:\app\Search
> : 11:41:19,984 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
> : org.apache.solr.core.CoreContainer$Initializer initialize
> : INFO: looking for solr.xml: C:\app\Search\solr.xml
> : 11:41:20,084 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
> : org.apache.solr.core.SolrResourceLoader <init>
> : INFO: Solr home set to 'C:\app\Search'
> : 11:41:20,142 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
> : org.apache.solr.core.SolrResourceLoader createClassLoader
> : INFO: Adding
> : 'file:/C:/app/Search/lib/apache-solr-dataimporthandler-1.3.0.jar' to
> Solr
> : classloader
> : 11:41:20,144 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
> : org.apache.solr.core.SolrResourceLoader createClassLoader
> : INFO: Adding 'file:/C:/app/Search/lib/jsp-2.1/' to Solr classloader
> :
> : ...........
> : INFO: Reusing parent classloader
> : 11:41:21,870 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
> : org.apache.solr.core.SolrConfig <init>
> : INFO: Loaded SolrConfig: solrconfig.xml
> : 11:41:21,909 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
> : org.apache.solr.schema.IndexSchema readSchema
> : INFO: Reading Solr Schema
> : 11:41:22,092 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
> : org.apache.solr.schema.IndexSchema readSchema
> : INFO: Schema name=contacts schema
> : 11:41:22,121 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
> : org.apache.solr.util.plugin.AbstractPluginLoader load
> : INFO: created string: org.apache.solr.schema.StrField
> :
> : .................
> : --
> : View this message in context:
> http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25354654.html
> : Sent from the Solr - User mailing list archive at Nabble.com.
> :
>
>
>
> -Hoss
>
>
>
--
View this message in context: http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25379937.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Misleading log messages while deploying solr
Posted by Chris Hostetter <ho...@fucit.org>.
: But the log message that is getting print in the server console, in my case
: jboss, is showing status as error.
: Why is this showing as ERROR, even though things are working fine.
Solr is not declaring that those messages are ERRORs, solr is just logging
informational messages (hence then "INFO" lines) using the java logging
framework.
My guess: since the logs are getting prefixed with "ERROR [STDERR]"
something about the way your jboss container is configured is probably
causing those log messages to be written to STDERR, and then jboss is
capturing the STDERR and assuming that if it went there it mist be an
"ERROR" of some kind and logging it to the console (using it's own log
format, hence the touble timestamps per line message)
In short: jboss is doing this in response to normal logging from solr.
you should investigate your options for configuriring jboss and how it
deals with log messages from applications.
: 11:41:19,030 INFO [TomcatDeployer] deploy, ctxPath=/solr,
: warUrl=.../tmp/deploy/tmp43266solr-exp.war/
: 11:41:19,948 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
: org.apache.solr.servlet.SolrDispatchFilter init
: INFO: SolrDispatchFilter.init()
: 11:41:19,975 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
: org.apache.solr.core.SolrResourceLoader locateInstanceDir
: INFO: No /solr/home in JNDI
: 11:41:19,976 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
: org.apache.solr.core.SolrResourceLoader locateInstanceDir
: INFO: using system property solr.solr.home: C:\app\Search
: 11:41:19,984 ERROR [STDERR] 8 Sep, 2009 11:41:19 AM
: org.apache.solr.core.CoreContainer$Initializer initialize
: INFO: looking for solr.xml: C:\app\Search\solr.xml
: 11:41:20,084 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
: org.apache.solr.core.SolrResourceLoader <init>
: INFO: Solr home set to 'C:\app\Search'
: 11:41:20,142 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
: org.apache.solr.core.SolrResourceLoader createClassLoader
: INFO: Adding
: 'file:/C:/app/Search/lib/apache-solr-dataimporthandler-1.3.0.jar' to Solr
: classloader
: 11:41:20,144 ERROR [STDERR] 8 Sep, 2009 11:41:20 AM
: org.apache.solr.core.SolrResourceLoader createClassLoader
: INFO: Adding 'file:/C:/app/Search/lib/jsp-2.1/' to Solr classloader
:
: ...........
: INFO: Reusing parent classloader
: 11:41:21,870 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
: org.apache.solr.core.SolrConfig <init>
: INFO: Loaded SolrConfig: solrconfig.xml
: 11:41:21,909 ERROR [STDERR] 8 Sep, 2009 11:41:21 AM
: org.apache.solr.schema.IndexSchema readSchema
: INFO: Reading Solr Schema
: 11:41:22,092 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
: org.apache.solr.schema.IndexSchema readSchema
: INFO: Schema name=contacts schema
: 11:41:22,121 ERROR [STDERR] 8 Sep, 2009 11:41:22 AM
: org.apache.solr.util.plugin.AbstractPluginLoader load
: INFO: created string: org.apache.solr.schema.StrField
:
: .................
: --
: View this message in context: http://www.nabble.com/Misleading-log-messages-while-deploying-solr-tp25354654p25354654.html
: Sent from the Solr - User mailing list archive at Nabble.com.
:
-Hoss