I faced the same issue as jakob with solr-7.6.0, eclipse-2018-12 (4.10.0),
Java 1.8.0_191:
*Solution:*
In eclipse Run Configuration run-solr
remove "file:" from Argument
-Dlog4j.configurationFile="file:${workspace_loc:solr-7.6.0}/solr/server/resources/log4j2.xml"
--
Sent from: http://lucene.47
The file:/// change was made in:
https://issues.apache.org/jira/browse/SOLR-12538, how to reconcile
these two?
On Sun, Sep 16, 2018 at 10:54 PM marcostocch...@gmail.com
wrote:
>
>
>
> On 2018/07/03 08:53:20, ja...@jafurrer.ch wrote:
> > Hi,
> >
> > I was intending to open an Issue in Jira when I r
On 9/16/2018 3:05 PM, marcostocch...@gmail.com wrote:
I experienced the same issue on Windows 10 professional. I don't think the OS
version is important. The solr version might. I have solr-7.4.0.
The problem has been fixed in the source code and the next version of
Solr (7.5.0) won't experie
On 2018/07/03 08:53:20, ja...@jafurrer.ch wrote:
> Hi,
>
> I was intending to open an Issue in Jira when I read that I'm supposed
> to first contact this mailinglist.
>
> Problem description
> ==
>
> System: Microsoft Windows 10 Enterprise Version 10.0.16299 Build 16299
>
>
I did it success by remove 'file:'
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Shawn:
Yeah, the best I've been able to come up with so far is to have
exactly two, both in server/resources
log4j2.xml - the standard configuration for running Solr
log4j2-console.xml Used by the startup scripts (_not_ running Solr).
See the last two comments on SOLR-12008 for more detail.
Eric
On 7/3/2018 2:53 AM, ja...@jafurrer.ch wrote:
> I was intending to open an Issue in Jira when I read that I'm supposed
> to first contact this mailinglist.
>
> Problem description
> ==
>
> System: Microsoft Windows 10 Enterprise Version 10.0.16299 Build 16299
>
> Steps to reproduce
Jakob:
I don't have Windows so rely on people who do to vet changes. But I'm
working on https://issues.apache.org/jira/browse/SOLR-12008 which
seeks to get rid of the confusing number of log4j config files and
solr.cmd has a lot of paths to change. So if you do get agreement that
you should raise
Thanks a lot for your inputs Alessandro and Mikhail.
@Alessandro, I tried with transaction log. But it was bit more of work to
get around( as it gets rolled over).
Hack I did is use of a proxy in between and Now I have more control.
Regards,
Govind
On Thu, Jun 14, 2018 at 7:32 PM Mikhail Khludne
You can enable DEBUG level for LogUpdateProcessorFactory category
https://github.com/apache/lucene-solr/blob/228a84fd6db3ef5fc1624d69e1c82a1f02c51352/solr/core/src/java/org/apache/solr/update/processor/LogUpdateProcessorFactory.java#L100
On Wed, Jun 13, 2018 at 5:00 PM, govind nitk wrote:
> H
Isn't the Transaction Log what you are looking for ?
Read this good blog post as a reference :
https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Cheers
-
---
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Direct
ofessional publishers, created in May 2015 through the combination of
> Nature Publishing Group,
> Palgrave Macmillan, Macmillan Education and Springer Science+Business Media.
> ---
> Springer Science+Business Media Deutschland GmbH
> Registered Office: Berlin / Amtsgericht Ber
In 6.5.1, the intra-cluster requests are POST, which makes them easy to
distinguish in the request logs. Also, the intra-cluster requests go to a
specific core instead of to the collection. So we use the request logs and grep
out the GET lines.
We are considering fronting every Solr process wit
To be more precisely and provide some more details, i tried to simplify the
problem by using the Solr-examples that were delivered with the solr
So i started bin/solr -e cloud, using 2 nodes, 2 shards and replication of 2.
To understand the following, it might be important to know, which por
Hi Stefan,
I am not aware of option to log only client side queries, but I think that you
can find workaround with what you currently have. If you take a look at log
lines for query that comes from the client and one that is result of querying
shards, you will see differences - the most simple o
Thanks Shawn for the detailed context.
I saw some Logger (java.util.logging) in one class in lucene folder, hence
I thought that logging is now properly supported. Since, i am using solr
(and indirectly lucene), I will use whatever solr is using.
Not depending on any concrete logger is good for lu
Thanks Shalin
I actually had that config true, so it seems that I may not be exercising
the right scenario to execute that logline.
On Fri, Jul 28, 2017 at 1:47 AM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Lucene does not use a logger framework. But if you are using Solr then you
On 7/27/2017 10:57 AM, Nawab Zada Asad Iqbal wrote:
> I see a lot of discussion on this topic from almost 10 years ago: e.g.,
> https://issues.apache.org/jira/browse/LUCENE-1482
>
> For 4.5, I relied on 'System.out.println' for writing information for
> debugging in production.
>
> In 6.6, I notice
Lucene does not use a logger framework. But if you are using Solr then you
can route the infoStream logging to Solr's log files by setting an option
in the solrconfig.xml. See
http://lucene.apache.org/solr/guide/6_6/indexconfig-in-solrconfig.html#IndexConfiginSolrConfig-OtherIndexingSettings
On Fr
Any doughnut for me ?
Regards
Nawab
On Thu, Jul 27, 2017 at 9:57 AM Nawab Zada Asad Iqbal
wrote:
> Hi,
>
> I see a lot of discussion on this topic from almost 10 years ago: e.g.,
> https://issues.apache.org/jira/browse/LUCENE-1482
>
> For 4.5, I relied on 'System.out.println' for writing infor
I'm not a fan of auto-archiving myself and we definitely shouldn't be
doing it before checking if an instance is running. Can you please
open an issue?
On Thu, May 4, 2017 at 12:52 PM, Bernd Fehling
wrote:
> Hi Shalin,
>
> sounds like all or nothing method :-)
>
> How about a short check if an in
Hi Shalin,
sounds like all or nothing method :-)
How about a short check if an instance is still running
and using that log file before moving it to archived?
Regards
Bernd
Am 04.05.2017 um 09:07 schrieb Shalin Shekhar Mangar:
> Yes this is expected. On startup old console logs and gc logs are
Hi Erik,
about 1>
I have no core.properties at all, just a clean new installation.
- 5 x Zookeeper on 5 different server
- 5 x Solr 6.5.1 on 5 different server
- uploaded a configset with "bin/solr zk upconfig ..."
- started first Solr node with port 8983 of first server
- started second Solr node
Yes this is expected. On startup old console logs and gc logs are
moved into the archived folder by default. This can be disabled by
setting SOLR_LOG_PRESTART_ROTATION=false as a environment variable
(search for its usage in bin/solr) but it will also disable all log
rotation.
On Wed, May 3, 2017
Hi Edwin,
I'm using Solr 6.5.1
Am 04.05.2017 um 04:35 schrieb Zheng Lin Edwin Yeo:
> Which version of Solr are you using?
>
> I am using Solr 6.4.2, it seems that both nodes are trying to write to the
> same archived file.
>
>
> Exception in thread "main" java.nio.file.FileSystemException:
>
Bernd:
Do check two things:
1> your core.properties files. Do you have properties set in the
core.properties files that could possibly confuse things?
2> when you start your Solr instances, do you define any sysvars that
could confuse the archive directories?
These are wild shots in the dark mi
Which version of Solr are you using?
I am using Solr 6.4.2, it seems that both nodes are trying to write to the
same archived file.
Exception in thread "main" java.nio.file.FileSystemException:
C:\edwin\solr\server\logs\solr_gc.log.0.current ->
C:\edwin\solr\server\logs\archived\solr_gc.log.0.cu
That does look weird. Does the 7574 console log really get archived or
is the 8983 console log archived twice? If 7574 doesn't get moved to
the archive, this sounds like a JIRA, I'd go ahead and raise it.
Actually either way I think it needs a JIRA. Either the wrong log is
getting moved or the mes
removing the colon crushed it. thanks
the reason i'm looking at this is the logging screen is not showing log
content...last check shows the spinning wheel to the left.
Time (Local)Level CoreLogger Message
No Events available
Last Check:4/7/2017, 10:26:43 AM
Google chrome, IE 10
You also put a colon ':' in
FINEST, :
BTW, this will give you a _lot_ of output
Best,
Erick
On Fri, Apr 7, 2017 at 6:17 AM, KRIS MUSSHORN wrote:
> SOLR 5.4.1
>
> log files have this entry
>
>
> log4j:ERROR Could not find value for key log4j.appender.: file
> log4j:ERROR Could not instantia
ateek Jain
-Original Message-
From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
Sent: 17 February 2017 02:33 PM
To: solr-user
Subject: Re: logging query received
There is actually several ways to answer this depending on the level of
precision your situation requires. And, of course,
There is actually several ways to answer this depending on the level of
precision your situation requires. And, of course, there are trade-offs.
One issue to keep in mind is what you mean by "parameters". Do you want to
include all the explicit defaults and overrides that the Request Handler
will
If you enabled the logging for org.apache.solr.core you should be fine.
You can also go more fine grained if you don't need part of the logs.
Just remember that the UI will show only from the warning level.
If you want to see the query log you need to access the log files.
N.B. in a produciton env
I stand corrected. The Jetty request logs do indeed contain ALL of the
traffic, both from other nodes and from query requests.
For the record, it is valuable to capture the time at the client AND from the
server to track latency or compression issues.
On 2/11/16, 8:13 AM, "Shawn Heisey" wr
On 2/10/2016 10:33 AM, McCallick, Paul wrote:
> We’re trying to fine tune our query and ingestion performance and would like
> to get more metrics out of SOLR around this. We are capturing the standard
> logs as well as the jetty request logs. The standard logs get us QTime,
> which is not a g
Mikhail,
Thanks - it works now.The script transformer was really not needed, a
template transformer is clearer, and the log transformer is now working.
On Mon, Dec 8, 2014 at 1:56 AM, Mikhail Khludnev wrote:
> Hello Dan,
>
> Usually it works well. Can you describe how you run it particularl
Hello Dan,
Usually it works well. Can you describe how you run it particularly, eg
what you download exactly and what's the command line ?
On Fri, Dec 5, 2014 at 11:37 PM, Dan Davis wrote:
> I have a script transformer and a log transformer, and I'm not seeing the
> log messages, at least not w
Or you could use system properties to control that.
For example if you are using logbak, then
JAVA_OPTS="$JAVA_OPTS
-Dlogback.configurationFile=$CATALINA_BASE/conf/logback.xml" will do it
On 20 August 2014 03:15, Aman Tandon wrote:
> As you are using tomcat you can configure the log file na
As you are using tomcat you can configure the log file name, folder,etc. by
configuring the server.xml present in the Conf directory of tomcat.
On Aug 19, 2014 4:17 AM, "Shawn Heisey" wrote:
> On 8/18/2014 2:43 PM, M, Arjun (NSN - IN/Bangalore) wrote:
> > Currently in my component Solr is
On 8/18/2014 2:43 PM, M, Arjun (NSN - IN/Bangalore) wrote:
> Currently in my component Solr is logging to catalina.out. What is
> the configuration needed to redirect those logs to some custom logfile eg:
> Solr.log.
Solr uses the slf4j library for logging. Simply change your program to
Sorry, outdated link. And I suppose you use tomcat if you are talking
about catalina.out The correct link is :
http://wiki.apache.org/solr/SolrLogging#Solr_4.3_and_above
Le 18/08/2014 23:06, Aurélien MAZOYER a écrit :
Hi,
Are you using tomcat or jetty? If you use the default jetty, have
Hi,
Are you using tomcat or jetty? If you use the default jetty, have a look
to : http://wiki.apache.org/solr/LoggingInDefaultJettySetup
Regards,
Aurélien
Le 18/08/2014 22:43, M, Arjun (NSN - IN/Bangalore) a écrit :
Hi,
Currently in my component Solr is logging to catalina.out. W
I assume you are passing extra info to Solr.
Then you can write servletfilter to put it in NDC or MDC which can then be
picked up by log4j config pattern.
This approach is not Solr specific. Just usual servlet/log stuff.
Regards,
Alex
On 27/03/2014 9:00 pm, "Juha Haaga" wrote:
> Hello,
>
You could always just pass the username as part of the GET params for the
query. Solr will faithfully ignore and log any parameters it doesn¹t
recognize, so it¹d show up in your {lot of params}.
That means your log parser would need more intelligence, and your client
would have to pass in the dat
We do something similar and include the server's hostname in solr's response.
To accomplish this you'll have to write a class that extends
org.apache.solr.servlet.SolrDispatchFilter and put your custom class in place
as the SolrRequestFilter in solr's web.xml.
Thanks,
Greg
On Mar 27, 2014, at
Thanks a lot, it was exactly what I need, sorry for not being so clear with
my question :).
Gian Maria.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, March 19, 2013 3:04 PM
To: solr-user@lucene.apache.org; alkamp...@nablasoft.com
Subject: Re
what do you mean " log information into solar from a custom analyzer"? Have
info go from your custom analyzer into the Solr log? In which case, just do
something
like:
private static final Logger log =
LoggerFactory.getLogger(YourPrivateClass.class.getName());
and then in your code something like
Hi Gora,
I'm solrj4.1 with spring data solr.
here is my code.
PartialUpdate update = new PartialUpdate("id", "123");
update.setValueOfField("mutiValuedField", null);
solrTemplate.saveBean(update);
solrTemplate.commit();
On Fri, Jan 18, 2013 at 6:44 PM, Gora Mohanty wrote:
> On 18 January 2013
On 18 January 2013 18:34, Muhzin R wrote:
> Hi all, I'm trying to set the value of a field in my schema to null.The
> solr throws the following exception .
>
>
[...]
This is the relevant part of the error:
> INFO - 2013-01-18 18:13:35.409;
> org.
I have the same error. can you guide me how to solve this error?my id :
bhavesh.jogi...@gmail.com
--
View this message in context:
http://lucene.472066.n3.nabble.com/Logging-from-data-config-xml-tp3956009p4008540.html
Sent from the Solr - User mailing list archive at Nabble.com.
For anyone else who is still having this issue, the following may help. The
embedded SOLR server uses sl4j for logging, which is a facade over other
logging frameworks. It achieves this by looking for a 'binding' jar for the
implementation framework in the classpath. In my case I had the 'simple'
b
fixed the error, stupid typo, but log msg didn't appear until typo was
fixed. I would have thought they would be unrelated.
On 5/1/12 10:42 AM, "Twomey, David" wrote:
>
>
>I'm getting this error (below) when doing an import. I'd like to add a
>Log line so I can see if the file path is messe
You could configure your proxy or application to send any key/value pair not
being using by Solr. Solr will ignore the parameter but still log it as part
of params={}.
We use this to send various pieces of information that's being analyzed later
together with the query information.
On Wednesda
Does anyone know how I would be able to include the client ip address
for tomcat 6 with log4j?
Cheers,
Dan
On Wed, Sep 7, 2011 at 11:03 AM, Shalin Shekhar Mangar
wrote:
> On Wed, Sep 7, 2011 at 2:56 PM, dan sutton wrote:
>
>> Hi,
>>
>> We're using log4j with solr which is working fine and I'm w
On Wed, Sep 7, 2011 at 2:56 PM, dan sutton wrote:
> Hi,
>
> We're using log4j with solr which is working fine and I'm wondering
> how I might be able to log the client ip address?
>
> Has anyone else been able to do this?
>
Your application container should have an access log facility. That is t
You can also configure your logging framework to output the relevant logs to a
separate file:
log4j.logger.org.apache.solr.core.SolrCore=INFO, A1
This way you'll avoid too much noise from other componets, but you'll get all
update and admin requests as well, so you'll have to filter on core nam
> Is it possible to create a lean log file for queries and
> the number of
> hits these queries returned?
>
> We are running Solr under Tomcat.
I believe that many people do it at client side. But tomcat already logs that
info. If you set tomcat's log level to INFO you can extract hits, QTime an
I have added lines to my logging.properties for Tomcat:
6solr.org.apache.juli.FileHandler.level = FINE
6solr.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
6solr.org.apache.juli.FileHandler.prefix = solr.
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/solr].level
=
Thanks Jak! That was just what I was looking for!
-- Chris
On Mon, Sep 20, 2010 at 4:25 PM, Jak Akdemir wrote:
> It is quite easy to modify its default value. Solr is using default
> logging values that started to use in jvm. It can be bound as a start
> parameter or can be externally defined
It is quite easy to modify its default value. Solr is using default
logging values that started to use in jvm. It can be bound as a start
parameter or can be externally defined in
../tomcat/conf/logging.properties.
Simply it is enough to remove all contents (backup first) in
../tomcat/conf/logging
> So, Embedded Solr Server keeps logging queries and other
> stuff in my stdout.
I came across same problem. While looking for a solution I read your post.
I was able to find a solution by chance, so i wanted to share.
When I run my program with this parameter and logs disappeared.
java -Djava.
: Hi, thanks. I looked at these sites, and also the info about "java
: logging":
: http://java.sun.com/j2se/1.5.0/docs/guide/logging/overview.html
:
: But I couldn't really follow the info about configuration for logging.
typically you create a logging.properties file and put it in your
classp
Hello Kevin,
No, haven't worked.
I tried a lot of combinations between the jars of log4j, lsf4j and
log4j-slf4j and got no success.
As I said, for the solr.war, this you said seems to work, the same way I got
it working confiuring /lib/logging.properties, but not with embedded
server...
Anyone c
Not sure if it will solve your specific problem. We use Solr as a WAR as well
as Solrj. So the main solr distribution comes with slf4j-jdk-1.5.5.jar. I just
deleted that and replaced it with slf4j-log4j12-1.5.5.jar. And then it used my
existing log4j.properties file.
___
From: Chris Hostetter [hossman_luc...@fucit.org]
Sent: Wednesday, 24 February 2010 8:36 a.m.
To: solr-user@lucene.apache.org
Subject: Re: logging
: in the Solr example, how do I configure debug logging to a file?
http://wiki.apache.org/solr/SolrLogging
...and since you asked
: in the Solr example, how do I configure debug logging to a file?
http://wiki.apache.org/solr/SolrLogging
...and since you asked specificly about the example, which uses jetty...
http://wiki.apache.org/solr/SolrJetty#Logging
-Hoss
Hi Peter,
It depends on what you call a debug log and how you interface with Solr.
Anyway, if you use Solr over HTTP you can check out the logs of your
servlet container and configure the logging behaviour on the Solr web
admin page. Usually, the default logging is quite useful. Either way, see
t
On Wed, Dec 9, 2009 at 8:19 PM, Lee Smith wrote:
> Im trying to import data with DIH (mysql)
>
> All my SQL's are good having been tested manually.
>
> When I run full import ie:
> http://localhost:8983/solr/dataimport?command=full-import
>
> I get my XML result but nothing is being imported and
: Is there any way to get 1.3 Solr to use something other than java logging?
Solr 1.3 is compiled directly against the JUL logging APIs, so no.
: Am running solr inside tomcat and would like logging for solr to be directed
: to one set of (rotated) log files and leave tomcat logging in its own l
: - I think that the use of log files is discouraged, but i don't know if i
: can modify solr settings to log to a server (via rmi or http)
: - Don't want to drop down solr response performance
discouraged by who? ... having aseperate process tail your log file and
build an index that way is th
Or for my quick and dirty methods (this was just a test), I just removed the
jcl-over-slrj JAR, and it worked like normal.
From: Ryan McKinley
To: solr-user@lucene.apache.org
Sent: Friday, April 10, 2009 3:16:30 PM
Subject: Re: logging
If you use the off the
If you use the off the shelf .war, it *should* be the same. (if not,
we need to fix it)
If you are building your own .war, how SLF4 behaves depends on what
implementation is in the runtime path. If you want to use log4j
logging, put in the slf4j-log4j.jar in your classpath and you should
Ok, thanks Ryan!
On Thu, Nov 20, 2008 at 9:03 AM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> On Nov 20, 2008, at 11:57 AM, Erik Holstad wrote:
>
> Thanks for the help Ryan!
>> Using the start.jar with 1.3 and added the slf4j jar to the classpath.
>> When
>>
>
> with 1.3 -- the logging is java.
On Nov 20, 2008, at 11:57 AM, Erik Holstad wrote:
Thanks for the help Ryan!
Using the start.jar with 1.3 and added the slf4j jar to the
classpath. When
with 1.3 -- the logging is java.util.logging --
The slf4j advice only applies to 1.4-dev
ryan
Thanks for the help Ryan!
Using the start.jar with 1.3 and added the slf4j jar to the classpath. When
it comes to the setting up
of the log4j I wonder which method is better. To put the redirect to the log
server in the Jetty.xml file
or to put a log4j.properties file in the web library, and if it'
the trunk (solr-1.4-dev) is now using SLF4J
If you are using the packaged .war, the behavior should be identical
to 1.3 -- that is, it uses the java.util.logging implementation.
However, if you are using solr.jar, you select what logging framework
you actully want to use by including that c
ord) {
String logName = record.getLoggerName();
// do what ever forwarding you need to in here based on the framework
of your choice.
}
}
-Original Message-
From: Henrib [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 24, 2008 4:22 AM
To: solr-user@lucene.apache.org
Will,
I'd be definitely interested in your code but mostly in the config &
deployment options if you can share.
You did not happen to deploy on Websphere 6 by any chance ? I can't find a
way to configure jul to only log into our application logs (even less so in
our log4j logs); I'm not even sure
Henri,
There are some bridges out there but none had a version number > 0.1. I
found the simplest way was to configure JUL using a custom config file and
then tell it to use my custom handler to forward all messages to log4j.
There are obvious performance implications but it is doable and fairly
: Is there any way to get the logs to stderr/stdout to be in 24hour time?
http://wiki.apache.org/solr/FAQ#head-ffe035452f21ffdb4e4658c2f8f6553bd6ca
"How do I change the logging levels/files/format ?"
-Hoss
: I'm new to Solr and Tomcat and I'm trying to track down some odd errors.
: How do I set up Tomcat to do fine-grained Solr-specific logging? I have
: looked around enough to know that it should be possible to do per-webapp
: logging in Tomcat 5.5, but the details are hard to follow for a newbie
: Is there a way to filter the log that goes into resin by "bad/fatal" stuff
: separate from the usual request logging? I would like to put the solr errors
: somewhere else so it's more maintainable.
Resin actually has one of the best logging configuration mechanisms i've
seen, the docs from ca
Okay, I figured it out. The method invocation messages are being
generated by the java logging api. The default logging handler in the
solr+jetty setup is java.util.logging.ConsoleHandler. That handler (or
perhaps java.util.logging.SimpleFormatter, its default formatter)
causes a what-method-am-I-i
I think it's best to control log level by an external file; you don't
want to
reprogram when you need log.
Define the system property java.util.logging.config.file to point to
your
log properties file. I would copy
$JAVA_HOME/jre/lib/logging.properties and then add a line:
org.apache.solr.level = W
On 8/1/07, Stu Hood <[EMAIL PROTECTED]> wrote:
> I've been using Solr in an embedded situation, and its been working quite
> well. But as I've started scaling up the application, the logging that Solr
> does to stderr is getting excessive.
>
> I'd like to disable the INFO messages, and leave the
: Is this addressed in 1.2 or is running multiple instances of indexes
: such a Bad Idea that supporting this would be leading a fool further astray?
I still haven't had a chance to try it myself using Tomcat, but here's
what i found the last time someone asked about this...
http://www.nabble.co
Perhaps not the most elegant, but running each index on a
different container & port works pretty well. And we can tune
the jvm (and of course caches) differently.
--cw
FYI, the admin page has a link, [LOGGING], that can be use to change Solr's
logging on the fly.
Bill
On 3/4/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Hi Brian, all you have to do is create a logging.properties file and
: call this before starting up solr:
:
: System.setProperty("java.u
: Hi Brian, all you have to do is create a logging.properties file and
: call this before starting up solr:
:
: System.setProperty("java.util.logging.config.file", home+"/conf/
: logging.properties");
it's not neccessary to execute any javacode to configurate
java.util.logging ... that property c
sweet.
the logging is java logging... (not one i really know how to deal with)
Can you try setting system property like this:
http://www.exampledepot.com/egs/java.util.logging/Props.html
Brian Whitman wrote:
I'm trying to disable all logging from Solr, or at least re-route it to
a file.
I
On Mar 3, 2007, at 12:56 PM, Brian Whitman wrote:
I'm trying to disable all logging from Solr, or at least re-route
it to a file.
Hi Brian, all you have to do is create a logging.properties file and
call this before starting up solr:
System.setProperty("java.util.logging.config.file",
91 matches
Mail list logo
