[Dspace-tech] Log file size and management
All, I'm curious about how people are managing their log files. In particular, I've noticed that dspace.log.* and cocoon.log.* are around 200MB apiece, per day. We zip them at night, but even so, they're taking a ridiculous amount of storage space on our VPS. What are people doing with these logs? Offline archival? Also, while dspace.log.* are potentially useful if you have to go back and rerun legacy statistics, I'm not sure what cocoon logs are useful for...? Adios, -- Alan Orth alan.o...@gmail.com http://alaninkenya.org http://mjanja.co.ke I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -Bjarne Stroustrup, inventor of C++ -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Log file size and management
Hi Alan, take a look at logrotate. It's a standard unix tool to manage your logs, including splitting logs by day (DSpace does this itself), keeping the last N days around and compressing and/or moving the rest elsewhere. It's very configurable. Regards, ~~helix84 -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Log file size and management
Also, if some logs are too detailed for you which makes them grow too large, you can raise loglevel, e.g. from INFO to WARN. Although I personally wouldn't do it. https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-TurningonDebugging(optional) Regards, ~~helix84 -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Log file size and management
Hey, helix.
I zip my logs nightly with something like this:
find /home/dspace/log/ ! -iname *.gz -iname dspace.log.* -o ! -iname
*.gz -iname cocoon.log.* -daystart -mtime +1 -exec ionice -c2 -n7
gzip {} \;
I'm more wondering what people use these logs for, and how/if they
archive them (especially the cocoon logs).
Alan
On 04/19/2012 10:59 AM, helix84 wrote:
Hi Alan,
take a look at logrotate. It's a standard unix tool to manage your
logs, including splitting logs by day (DSpace does this itself),
keeping the last N days around and compressing and/or moving the rest
elsewhere. It's very configurable.
Regards,
~~helix84
--
Alan Orth
alan.o...@gmail.com
http://alaninkenya.org
http://mjanja.co.ke
I have always wished for my computer to be as easy to use as my telephone; my
wish has come true because I can no longer figure out how to use my telephone.
-Bjarne Stroustrup, inventor of C++
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Log file size and management
Al 19/04/12 09:53, En/na Alan Orth ha escrit: All, I'm curious about how people are managing their log files. In particular, I've noticed that dspace.log.* and cocoon.log.* are around 200MB apiece, per day. We zip them at night, but even so, they're taking a ridiculous amount of storage space on our VPS. What are people doing with these logs? Offline archival? Also, while dspace.log.* are potentially useful if you have to go back and rerun legacy statistics, I'm not sure what cocoon logs are useful for...? Adios, Hi Alan, In our case we set limits in log4j.properties for all log files (*.MaxLogs) and raised the log level for Cocoon, which was generating huge log files. We also archive the older dspace.log files. By the way, could someone clarify exactly which files are used for statistics and how? I mean, for example, after running daily stat-* commands, the logs which have been processed are needed again? And what about .dat files? Cheers, Àlex -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Log file size and management
As i know , the log files are not needed if you've generated your stat reports, you just keep that generated ones into archival, the log files are just the source for the task, not the outcomes. 2012/4/19 Alexandre Magaz Graça alexandre.ma...@udl.cat Al 19/04/12 09:53, En/na Alan Orth ha escrit: All, I'm curious about how people are managing their log files. In particular, I've noticed that dspace.log.* and cocoon.log.* are around 200MB apiece, per day. We zip them at night, but even so, they're taking a ridiculous amount of storage space on our VPS. What are people doing with these logs? Offline archival? Also, while dspace.log.* are potentially useful if you have to go back and rerun legacy statistics, I'm not sure what cocoon logs are useful for...? Adios, Hi Alan, In our case we set limits in log4j.properties for all log files (*.MaxLogs) and raised the log level for Cocoon, which was generating huge log files. We also archive the older dspace.log files. By the way, could someone clarify exactly which files are used for statistics and how? I mean, for example, after running daily stat-* commands, the logs which have been processed are needed again? And what about .dat files? Cheers, Àlex -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- TRUONG HOANG DUNG* **Librarian Researcher **Information and Library Centre Mobile: 0121.411.5322 Email: dun...@hpu.edu.vn* *Hai Phong Private University* http://lib.hpu.vn -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
