solr-8983-console.log is huge

[CrazyDiamond]

That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?



--
View this message in context: http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[sara hajili]

You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
For more info look at:
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?



--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[Upayavira]

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?

I recently created this ticket:

https://issues.apache.org/jira/browse/SOLR-8232

It is all well and good saying you can change your logging to be less
aggressive, but if the log file is never rotated, it WILL use up disk
space one way or another. The correct way to fix this, I'd suggest is to
not log anything to the console, and use log4j.properties to send log
events to a file that *is* rotated.

Upayavira

[Shawn Heisey]

Post by Upayavira

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?

https://issues.apache.org/jira/browse/SOLR-8232
It is all well and good saying you can change your logging to be less
aggressive, but if the log file is never rotated, it WILL use up disk
space one way or another. The correct way to fix this, I'd suggest is to
not log anything to the console, and use log4j.properties to send log
events to a file that *is* rotated.

I just commented on SOLR-8232 with what I think is a viable solution to
the problem -- change CONSOLE logging in all the log4j.properties files
to only log at WARN severity or higher. There is some value to a
console log, but only if it doesn't duplicate every single informational
message that goes into the main log.

Thanks,
Shawn

[Erick Erickson]

How do you start solr? If you pipe console output
to a file it'll grow forever. Either pipe the
output to dev/null or follow Sara's link and
take the CONSOLE appender out of log4j.properties

Best,
Erick

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?
--
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[Upayavira]

Erick,

bin/start pipes stdout to solr-$PORT-console.log or such. With no
rotation. So we are setting people up to fail right from the get-go.

That's what I'm hoping the attached ticket will resolve.

Upayavira

Post by Erick Erickson
How do you start solr? If you pipe console output
to a file it'll grow forever. Either pipe the
output to dev/null or follow Sara's link and
take the CONSOLE appender out of log4j.properties
Best,
Erick

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?
--
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[Alexandre Rafalovitch]

What about the Garbage Collection output? I think we have the same
issue there. Frankly, I don't know how many people know what to do
with that in a first place.


----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/

Post by Upayavira
Erick,
bin/start pipes stdout to solr-$PORT-console.log or such. With no
rotation. So we are setting people up to fail right from the get-go.
That's what I'm hoping the attached ticket will resolve.
Upayavira

Post by Erick Erickson
How do you start solr? If you pipe console output
to a file it'll grow forever. Either pipe the
output to dev/null or follow Sara's link and
take the CONSOLE appender out of log4j.properties
Best,
Erick

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?
--
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[Erick Erickson]

Yep, I looked at the new JIRA and finally figured out what the
problem is.

It should be changed, but in the meantime one can go in and
take the CONSOLE appender out of the logging properties file.

Or restart Solr periodically. Ugly but it would work.

On Fri, Nov 6, 2015 at 8:13 AM, Alexandre Rafalovitch

Post by Alexandre Rafalovitch
What about the Garbage Collection output? I think we have the same
issue there. Frankly, I don't know how many people know what to do
with that in a first place.
----
http://www.solr-start.com/

Post by Upayavira
Erick,
bin/start pipes stdout to solr-$PORT-console.log or such. With no
rotation. So we are setting people up to fail right from the get-go.
That's what I'm hoping the attached ticket will resolve.
Upayavira

Post by Erick Erickson
How do you start solr? If you pipe console output
to a file it'll grow forever. Either pipe the
output to dev/null or follow Sara's link and
take the CONSOLE appender out of log4j.properties
Best,
Erick

Post by sara hajili
You can change solr loglevel.bydefault solr logs for every thing.
You can change this by go in solrconsole.inlog/level and edit levels for
just error for example.
And this is temporary way.
You can also change solrconfig.insolr_home
In /log and change logging4j
Config.
https://cwiki.apache.org/confluence/display/solr/Configuring+Logging
That log file is constantly growing. And it is now ~60GB. what can i change
to fix this?
--
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613.html
Sent from the Solr - User mailing list archive at Nabble.com.

[Shawn Heisey]

Post by Alexandre Rafalovitch
What about the Garbage Collection output? I think we have the same
issue there. Frankly, I don't know how many people know what to do
with that in a first place.

Turns out that Java has rotation capability built in to GC logging:

http://stackoverflow.com/a/12277309/2665648

Thanks,
Shawn

[davidphilip cherian]

From mail archives
<http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201510.mbox/%3CCADBFWQ_c0EwSZX-1QY6UAFNUfSuKM5ECnYSDhj+by=***@mail.gmail.com%3E>
https://support.lucidworks.com/hc/en-us/articles/207072137-Solr-5-X-Console-Logging-solr-8983-console-log

Post by Shawn Heisey

Post by Alexandre Rafalovitch
What about the Garbage Collection output? I think we have the same
issue there. Frankly, I don't know how many people know what to do
with that in a first place.

http://stackoverflow.com/a/12277309/2665648
Thanks,
Shawn

[CrazyDiamond]

Thx for answers. Is there any way to reload log4j.properities without
restarting solr?



--
View this message in context: http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613p4239067.html
Sent from the Solr - User mailing list archive at Nabble.com.

[davidphilip cherian]

I think, the collection reload, using collection apis[1] should do the
work. If you are not on solr-cloud setup, just navigate to coreadmin on
solr UI, and click on reload, and see if that works.


[1]
https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api2
http:
//localhost:8983/solr/admin/collections?action=RELOAD&name=newCollection

Post by CrazyDiamond
Thx for answers. Is there any way to reload log4j.properities without
restarting solr?
--
http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613p4239067.html
Sent from the Solr - User mailing list archive at Nabble.com.

[CrazyDiamond]

i use solr cloud.



--
View this message in context: http://lucene.472066.n3.nabble.com/solr-8983-console-log-is-huge-tp4238613p4239100.html
Sent from the Solr - User mailing list archive at Nabble.com.