[opensuse] /var/log/zypp-refresh.log Size on 11.0? ( 275 Megabytes -- WTF? )
Peter, Listmates, My /var/log/zypp-refresh.log had grown alarmingly big: -rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log 275M for a logfile? How can I put this under some kind of logrotate or something to keep the size less than 10M or so? Do I just add it to the existing logrotate or do I just write a script to do it? For the curious, the last 1000 lines of the log file are available at: http://www.3111skyline.com/download/openSUSE_bugs/110/zypp-refresh-1000.log.... (size: 11k) Is this a bug, feature or result of all the repository failures lately? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-03-21 at 20:24 -0500, David C. Rankin wrote:
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log
Some got a log on the several gigabytes range, filling the entire partition. To repair the system the file was deleted, so that it is unknown why it is lo large. It was commented here not too long ago. Perhaps you could examine that log and determine why it is so large, then open a bugerport on bugzilla - sending the log to them is probably not practical. Perhaps try compressing with lzma - logs compress a lot with that one. Maybe it gets down to a practical size. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknFnkIACgkQtTMYHG2NR9WU7wCfXk6J4BPKNVAyNsWtGf4zMAr1 aRIAn3vaWefyNbe3cqFEOIU19gFoaa5L =mus2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/22/2009 10:11 AM, Carlos E. R. wrote:
On Saturday, 2009-03-21 at 20:24 -0500, David C. Rankin wrote:
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log
Some got a log on the several gigabytes range, filling the entire partition. To repair the system the file was deleted, so that it is unknown why it is lo large. It was commented here not too long ago.
Perhaps you could examine that log and determine why it is so large, then open a bugerport on bugzilla - sending the log to them is probably not practical.
Perhaps try compressing with lzma - logs compress a lot with that one. Maybe it gets down to a practical size.
-- Cheers, Carlos E. R.
I had something similar happen again here on a different machine, but with zypper.log It had grown to over 16 GB and filled up my root partition. I had left it updating with Kupdater. After it was restarted, a regular user couldn't even log in. This has happened to me on 2 different computers. Not nice at all. So for me, after my over 16 GB log files, 250 MB seem small. -- Joe Morris Registered Linux user 231871 running openSUSE 11.1 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 21 March 2009 09:11:07 pm Carlos E. R. wrote:
On Saturday, 2009-03-21 at 20:24 -0500, David C. Rankin wrote:
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log
Some got a log on the several gigabytes range, ... Perhaps you could examine that log and determine why it is so large, then open a bugerport on bugzilla - sending the log to them is probably not practical.
They want to see what is the problem. grep '<0>' drankin-zypp-refresh-1000.log | wc 618 7737 93063 Somewhat increased log level :-) The time difference is 5 sec. I don't have lines with <0> log level in zypper.log, and I can't see zypper-refresh.log . -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Saturday 21 March 2009 09:11:07 pm Carlos E. R. wrote:
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log Some got a log on the several gigabytes range, ... Perhaps you could examine that log and determine why it is so large, then open a bugerport on bugzilla - sending the log to them is probably not
On Saturday, 2009-03-21 at 20:24 -0500, David C. Rankin wrote: practical.
They want to see what is the problem.
grep '<0>' drankin-zypp-refresh-1000.log | wc 618 7737 93063 Somewhat increased log level :-) The time difference is 5 sec.
I don't have lines with <0> log level in zypper.log, and I can't see zypper-refresh.log .
Rajko, How do I change the log level for the zypp-refresh.log?? My *zypper.log* is fine and rotates nicely: -rw-r----- 1 1308829 2009-03-22 00:37 zypper.log -rw-r----- 1 374110 2009-01-22 05:01 zypper.log-20090122.bz2 -rw-r----- 1 448671 2009-01-29 05:01 zypper.log-20090129.bz2 It is the zypp-refresh.log that's killing me. I haven't ever monkeyed with the log level on anything except samba and ppp (for debugging), and maybe a few others over the years, but nothing on my 11.0 laptop. Where should I look? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Saturday, 2009-03-21 at 20:24 -0500, David C. Rankin wrote:
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log
Some got a log on the several gigabytes range, filling the entire partition. To repair the system the file was deleted, so that it is unknown why it is lo large. It was commented here not too long ago.
Perhaps you could examine that log and determine why it is so large, then open a bugerport on bugzilla - sending the log to them is probably not practical.
Perhaps try compressing with lzma - logs compress a lot with that one. Maybe it gets down to a practical size.
-- Cheers, Carlos E. R.
Here are the alarming stats. Roughly 24 hours ago, I cleaned the zypp-refresh.log by archiving the old stuff and starting a new log: bzip2 zypp-refresh.log && touch zypp-refresh.log Since last night, the log has grown to over 25 Meg comprised of 18,388 lines: -rw-r----- 1 root root 9491674 2009-03-20 22:51 zypp-refresh-20090321.log.bz2 -rw-r----- 1 root root 2547826 2009-03-21 22:50 zypp-refresh.log [00:27 alchemy:/var/log] # wc -l zypp-refresh.log 18388 zypp-refresh.log Is there some way to turn down the log level for zypper refresh? As another test, I reset the zypp-refresh.log and tested with a single zypper ref to see how much was generated: [00:33 alchemy:/var/log] # bzip2 zypp-refresh.log && mv zypp-refresh.log.bz2 zypp-refresh-$(date '+%Y%m%d.%H%M').log.bz2 && touch zypp-refresh.log && zypper ref Repository 'Updates for 11.0' is up to date. <snip all repos already up to date> All repositories have been refreshed. [00:37 alchemy:/var/log] # l zypp-re* -rw-r----- 1 root root 9491674 2009-03-20 22:51 zypp-refresh-20090321.log.bz2 -rw-r----- 1 root root 92172 2009-03-21 22:50 zypp-refresh-20090322.0036.log.bz2 -rw-r--r-- 1 root root 0 2009-03-22 00:36 zypp-refresh.log Surprisingly, no log information was generated. I don't know whether this is because the repo data was already up to date (my guess) or whether using 'zypper ref' doesn't write to the zypp-refresh.log. In any case, log file growth of 25M/day isn't something that is acceptable. I can imagine the surprise of you guys finding 16G log files. I guess the solution until this is fixed is to write a script to call by cron each day that will compress the current file if it is over 10M and move it to somewhere convenient. I went ahead a created a script to check log file size that you can add to the root cron tab to run once daily. I called the script cklogsize, and a cron entry to run it at 10 minutes after 4 am each day would be: 10 4 * * * /home/david/linux/scripts/log/cklogsize zypp-refresh.log The script and explanation follows. To make sure you don't have any line wrap problems, you can also download a copy here: http://www.3111skyline.com/download/linux/scripts/cklogsize #!/bin/bash --norc ## ## Title: Check Log Size ## Name: cklogsize ## Usage: cklogsize logfilename [maxsize [newzipfiledir]] ## Version: 0.0.1 ## Date: 03/22/2009, 01:02:14 AM ## Author: David C. Rankin, J.D.,P.E ## Summary: cklogsize will check the size of a log file supplied as a command line ## argument against the default size of 10M (or the size supplied as the second argument ## on the command line in bytes) and if the log file size exceeds the maximum, compress ## the log files with bzip2 to the original log file directory (or new directory if ## provided as the third argument on the command line) and create a new empty log file. ## It is intended to be called by cron. ## ## Run as: log file owner or root ## Requires: bzip2 ## ## # [[ -z $1 ]] && { echo -e "\n\tUsage:\t'${0##*/} logfilename [maxsize [zipfiledir]]'\ , exiting...\n"; exit 1; } [[ ! -r $1 ]] && { echo -e "\n\tFile: '${1}' not readable, check your filename.\n"; exit 1; } LOGFILE=$1 MAXSIZE=${2:-10000000} CURRENTDIR=$(pwd) NEWDIR=${3:-${1%/*}} [[ $NEWDIR == $LOGFILE ]] && NEWDIR=$CURRENTDIR declare -a FSIZESTR FSIZESTR=( $(ls -l ${LOGFILE}) ) if [[ ${FSIZESTR[4]} -gt $MAXSIZE ]]; then bzip2 $LOGFILE if [[ ! -d $NEWDIR ]]; then if ! mkdir $NEWDIR; then echo "Unable to create directory '$NEWDIR', check that your have permission." exit 1 fi fi [[ $NEWDIR != $CURRENTDIR ]] && mv $LOGFILE.bz2 $NEWDIR touch $LOGFILE fi exit 0 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
I went ahead a created a script to check log file size that you can add to the root cron tab to run once daily. I called the script cklogsize, and a cron entry to run it at 10 minutes after 4 am each day would be:
10 4 * * * /home/david/linux/scripts/log/cklogsize zypp-refresh.log
The script and explanation follows. To make sure you don't have any line wrap problems, you can also download a copy here:
<snip> Looks like there is also a much easier way than rolling a custom script and crontab. Just edit /etc/logrotate.d/zypper.lr and add a section for /var/log/zypp-refresh.log. I just copied the entry for /var/log/zypper.log. When you are done, the file should look like: /var/log/zypper.log { compress dateext notifempty missingok nocreate maxage 60 rotate 99 size 10M } /var/log/zypp-refresh.log { compress dateext notifempty missingok nocreate maxage 60 rotate 99 size 10M } Oh well, a fun hour spent on the script itself. Cheers. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 22 Mar 2009 19:05:40 David C. Rankin wrote:
David C. Rankin wrote:
I went ahead a created a script to check log file size that you can add to the root cron tab to run once daily. I called the script cklogsize, and a cron entry to run it at 10 minutes after 4 am each day would be:
10 4 * * * /home/david/linux/scripts/log/cklogsize zypp-refresh.log
The script and explanation follows. To make sure you don't have any line wrap problems, you can also download a copy here:
<snip>
Looks like there is also a much easier way than rolling a custom script and crontab. Just edit /etc/logrotate.d/zypper.lr and add a section for /var/log/zypp-refresh.log. I just copied the entry for /var/log/zypper.log. When you are done, the file should look like:
/var/log/zypper.log { compress dateext notifempty missingok nocreate
maxage 60 rotate 99 size 10M }
/var/log/zypp-refresh.log { compress dateext notifempty missingok nocreate
maxage 60 rotate 99 size 10M }
Oh well, a fun hour spent on the script itself. Cheers.
Thanks for the heads-up, David. I just checked mine (haven't visited /var/log much recently) and found 573M, so I added the section to the logrotate on my machines too... I think this might be worth a bugzilla - this should be in there by default and I can't see anyone objecting to it being there. It is such an easy fix for them to roll out, too... Cheers, Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-22 at 21:06 +1030, Rodney Baker wrote:
Thanks for the heads-up, David. I just checked mine (haven't visited /var/log much recently) and found 573M, so I added the section to the logrotate on my machines too...
I think this might be worth a bugzilla - this should be in there by default and I can't see anyone objecting to it being there. It is such an easy fix for them to roll out, too...
Absolutely! But it is you both, Rodney and David, who have to write that Bugzilla. I don't even have a /var/log/zypp-refresh.log! (remember to try compressing with lzma - much higher ratio for text - in order to send them the log) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknGH20ACgkQtTMYHG2NR9Xw8ACfTci4+F3bIw3ACjif5/eBJVkJ XzMAnRMZPKeinLTMoY5oCCcat3CFrTBc =Y3Fk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 11:22:15 Carlos E. R. wrote:
On Sunday, 2009-03-22 at 21:06 +1030, Rodney Baker wrote:
Thanks for the heads-up, David. I just checked mine (haven't visited /var/log much recently) and found 573M, so I added the section to the logrotate on my machines too...
I think this might be worth a bugzilla - this should be in there by default and I can't see anyone objecting to it being there. It is such an easy fix for them to roll out, too...
Absolutely! But it is you both, Rodney and David, who have to write that Bugzilla. I don't even have a /var/log/zypp-refresh.log!
(remember to try compressing with lzma - much higher ratio for text - in order to send them the log)
-- Cheers, Carlos E. R.
Let us know the bug number, and I'll vote for it. My zypp-refresh.log grew to 9.2GB a few days ago. Then I discovered this thread. :) Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.19-3.2-default, KDE 4.2.1 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009 03:35:40 am David C. Rankin wrote:
David C. Rankin wrote:
I went ahead a created a script to check log file size that you can add to the root cron tab to run once daily. I called the script cklogsize, and a cron entry to run it at 10 minutes after 4 am each day would be:
10 4 * * * /home/david/linux/scripts/log/cklogsize zypp-refresh.log
The script and explanation follows. To make sure you don't have any line wrap problems, you can also download a copy here:
<snip>
Looks like there is also a much easier way than rolling a custom script and crontab. Just edit /etc/logrotate.d/zypper.lr and add a section for /var/log/zypp-refresh.log. I just copied the entry for /var/log/zypper.log. When you are done, the file should look like:
/var/log/zypper.log { compress dateext notifempty missingok nocreate
maxage 60 rotate 99 size 10M }
/var/log/zypp-refresh.log { compress dateext notifempty missingok nocreate
maxage 60 rotate 99 size 10M }
I missed that you are using 11.0 . I have zypp-refresh.lr , but as said there is no /var/log/zypp-refresh.log . I guess they removed it in 11.1. It is obviously bug in 11.0. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Sonntag, 22. März 2009 schrieb Rajko M.:
[...] I have zypp-refresh.lr , but as said there is no /var/log/zypp-refresh.log . I guess they removed it in 11.1. [...]
I do not think so, since on my 11.1 installation, there is /var/log/zypp- refresh.log (and /etc/logrotate.d/zypp-refresh.lr). Gruß Jan -- The mind is like a parachute, it works better when it's open. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-22 at 03:03 -0500, David C. Rankin wrote:
Here are the alarming stats. Roughly 24 hours ago, I cleaned the zypp-refresh.log by archiving the old stuff and starting a new log:
bzip2 zypp-refresh.log && touch zypp-refresh.log
Use lzma instead. Takes a long time, but text compresses a lot, and then you might be able to send the file for study to Novell.
Is there some way to turn down the log level for zypper refresh?
I don't know.
I guess the solution until this is fixed is to write a script to call by cron each day that will compress the current file if it is over 10M and move it to somewhere convenient.
But it will not be fixed until somebody with that problem writes a bugzilla! And that means _you_. >:-) As to the compress, remember that there is a service to rotate logs. Just add this file. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknGIN0ACgkQtTMYHG2NR9UEYQCdGqVkhYUe3A7BQ+fuhq1sWZe3 ELMAn0hC7pk+UqEwW9Gx+JRblq35l2Xp =lHNV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 22, 2009 at 12:28:27PM +0100, Carlos E. R. wrote:
On Sunday, 2009-03-22 at 03:03 -0500, David C. Rankin wrote:
Here are the alarming stats. Roughly 24 hours ago, I cleaned the zypp-refresh.log by archiving the old stuff and starting a new log:
bzip2 zypp-refresh.log && touch zypp-refresh.log
Use lzma instead. Takes a long time, but text compresses a lot, and then you might be able to send the file for study to Novell.
Is there some way to turn down the log level for zypper refresh?
I don't know.
I guess the solution until this is fixed is to write a script to call by cron each day that will compress the current file if it is over 10M and move it to somewhere convenient.
But it will not be fixed until somebody with that problem writes a bugzilla! And that means _you_. >:-)
just did. https://bugzilla.novell.com/show_bug.cgi?id=487613 Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-22 at 14:12 +0100, Marcus Meissner wrote:
But it will not be fixed until somebody with that problem writes a bugzilla! And that means _you_. >:-)
just did.
Thanks. But, from the posts here, the problem is not only that it is not rotated, but that the log can be huge, several gigabytes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknGQDkACgkQtTMYHG2NR9WITQCfYIP4P2xIvBpZQiblmlOnxg4D xh8An0CNdTlsg/mM307+DIS+NZfdYzaX =bP1H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 22, 2009 at 02:42:11PM +0100, Carlos E. R. wrote:
On Sunday, 2009-03-22 at 14:12 +0100, Marcus Meissner wrote:
But it will not be fixed until somebody with that problem writes a bugzilla! And that means _you_. >:-)
just did.
Thanks.
But, from the posts here, the problem is not only that it is not rotated, but that the log can be huge, several gigabytes.
Because it is not rotated daily, if needed... If it gets that large in one day, something else is amiss. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-22 at 15:18 +0100, Marcus Meissner wrote:
Thanks.
But, from the posts here, the problem is not only that it is not rotated, but that the log can be huge, several gigabytes.
Because it is not rotated daily, if needed...
Even so; I keep logs for years and the total is not one gig. Even rotating logs of 15 GB, compressed, would involve too much space for a single log. I also have my doubts that you can gzip such a file.
If it gets that large in one day, something else is amiss.
That's the idea, that there are some unknown cases where it grows out of bounds. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknGUlEACgkQtTMYHG2NR9UsuwCdGJTL8YubxL2Xyr+J5OP1VDhh vgkAniMQbxEyS8rlRdmLQY9EhJC1f5YD =sUuo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 22, 2009 at 03:59:23PM +0100, Carlos E. R. wrote:
On Sunday, 2009-03-22 at 15:18 +0100, Marcus Meissner wrote:
Thanks.
But, from the posts here, the problem is not only that it is not rotated, but that the log can be huge, several gigabytes.
Because it is not rotated daily, if needed...
Even so; I keep logs for years and the total is not one gig. Even rotating logs of 15 GB, compressed, would involve too much space for a single log. I also have my doubts that you can gzip such a file.
It will be compressed nearly to nothing. Also rotation will only keep a backlog of "n" (configurable) old rotated ones.
If it gets that large in one day, something else is amiss.
That's the idea, that there are some unknown cases where it grows out of bounds.
These are seperate bugs :) Ciao, MArcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Marcus Meissner wrote:
On Sun, Mar 22, 2009 at 03:59:23PM +0100, Carlos E. R. wrote:
On Sunday, 2009-03-22 at 15:18 +0100, Marcus Meissner wrote:
But, from the posts here, the problem is not only that it is not rotated, but that the log can be huge, several gigabytes. Because it is not rotated daily, if needed... Even so; I keep logs for years and the total is not one gig. Even rotating logs of 15 GB, compressed, would involve too much space for a single log. I also have my doubts that you can gzip such a file.
It will be compressed nearly to nothing.
Also rotation will only keep a backlog of "n" (configurable) old rotated ones.
If it gets that large in one day, something else is amiss. That's the idea, that there are some unknown cases where it grows out of bounds.
These are seperate bugs :)
Ciao, MArcus
The strange thing is that I can't find where to change the loglevel of that file. It grows by about 25M each time it gets written to. The logrotate works perfectly once you add the file to the logrotate scheme. To clean up /var/log a little bit, I changed both zypper.log and zypp-refresh.log to move the compressed log files to the directory /var/log/zypper-old: /var/log/zypper.log { compress dateext notifempty missingok nocreate olddir /var/log/zypper-old maxage 60 rotate 99 size 10M } /var/log/zypp-refresh.log { compress dateext notifempty missingok nocreate olddir /var/log/zypper-old maxage 60 rotate 99 size 10M } Moving the existing old logs really helps /var/log. Keeps it to one screen with ls -al. It wouldn't be bad to add a generic /var/log/old directory to openSuSE 11.2 and have all old logs rotated there. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-03-24 at 18:04 -0500, David C. Rankin wrote:
To clean up /var/log a little bit, I changed both zypper.log and zypp-refresh.log to move the compressed log files to the directory /var/log/zypper-old:
Mmm. There are some utilities for reporting to suse that make tar copies of log files to attach to a report, which I think may not work if you change the default directories. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknJcFAACgkQtTMYHG2NR9UbKACdFG+2a5BjljwcvQZL66jlaLcN SZYAmQFbjSF6MGEYTAzUfJFEatsxAT/c =iRAm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Tuesday, 2009-03-24 at 18:04 -0500, David C. Rankin wrote:
To clean up /var/log a little bit, I changed both zypper.log and zypp-refresh.log to move the compressed log files to the directory /var/log/zypper-old:
Mmm. There are some utilities for reporting to suse that make tar copies of log files to attach to a report, which I think may not work if you change the default directories.
-- Cheers, Carlos E. R.
You thinking y2logs stuff?? I'll have to check to see if it makes a difference. I hadn't even considered it.. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-03-25 at 04:11 -0500, David C. Rankin wrote:
Mmm. There are some utilities for reporting to suse that make tar copies of log files to attach to a report, which I think may not work if you change the default directories.
You thinking y2logs stuff?? I'll have to check to see if it makes a difference. I hadn't even considered it.. Thanks.
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknKJ5EACgkQtTMYHG2NR9UhpgCfSE6vZen68aPyMvsx1MpYWk5o nIMAn0EU2ivYJo69KjJTNjRMQrfw34MU =sns0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 25 March 2009 07:46:07 am Carlos E. R. wrote:
On Wednesday, 2009-03-25 at 04:11 -0500, David C. Rankin wrote:
Mmm. There are some utilities for reporting to suse that make tar copies of log files to attach to a report, which I think may not work if you change the default directories.
You thinking y2logs stuff?? I'll have to check to see if it makes a difference. I hadn't even considered it.. Thanks.
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more.
It will work as it looks in standard directories which will have current logs. If developers need older stuff David can upload those manually. They are already compressed. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 25 March 2009 12:46:07 Carlos E. R. wrote:
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more. ^^^^^^^^^ Is nothing safe from Customs & Revenue?
Ooops. Follow up to opensuse-offtopic, please ;) Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.19-3.2-default, KDE 4.2.1 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-03-25 at 15:34 -0000, Bob Williams wrote:
On Wednesday 25 March 2009 12:46:07 Carlos E. R. wrote:
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more. ^^^^^^^^^ Is nothing safe from Customs & Revenue?
Huh? :-?? http://en.wiktionary.org/wiki/dunno ] Written form of a reduction of "do not know" or of "does not know".
Ooops. Follow up to opensuse-offtopic, please ;)
Sorry, not subscribed O:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknKWtYACgkQtTMYHG2NR9WnaACeOJqlIMdd6K6kL7n/0eLFfbQX keEAni7UbU9Abu5QA/euWfplDdcLQHJL =RZXl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 25 March 2009 16:24:53 Carlos E. R. wrote:
On Wednesday, 2009-03-25 at 15:34 -0000, Bob Williams wrote:
On Wednesday 25 March 2009 12:46:07 Carlos E. R. wrote:
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more.
^^^^^^^^^ Is nothing safe from Customs & Revenue?
Huh? :-??
http://en.wiktionary.org/wiki/dunno
] Written form of a reduction of "do not know" or of "does not know".
Ooops. Follow up to opensuse-offtopic, please ;)
Sorry, not subscribed O:-)
-- Cheers, Carlos E. R.
Hi Carlos, My carets were carefully placed under the word sintax (which implies, to me, a tax on sin, whereas I think you meant syntax). Your mailreader moved them one word to the right :( Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.19-3.2-default, KDE 4.2.1 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-03-25 at 17:03 -0000, Bob Williams wrote:
Yep. And the resolver test case. From inside yast and from zypper, I forgot the sintax. Dunno if there is something more.
^^^^^^^^^ Is nothing safe from Customs & Revenue?
Huh? :-??
My carets were carefully placed under the word sintax (which implies, to me, a tax on sin, whereas I think you meant syntax). Your mailreader moved them one word to the right :(
Ah! X'-) I see. Your joke misfired :-) But I don't think it was moved, but rather, that you are using a viewer with proportional font and I one with fixed font. Proportional fonts use small spaces, so you have to add more than letters. That's why we should use fixed fonts with text only email >:-) (this time I remembered to pass the spell-checker ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknKfp4ACgkQtTMYHG2NR9XRowCdHAQZgGGUW3/3CaeMUr3GRrZs hJIAn1xcL7huqddDpdNVe581h+JSgP16 =mYJ3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 22 March 2009, David C. Rankin wrote:
Peter, Listmates,
My /var/log/zypp-refresh.log had grown alarmingly big:
-rw-r----- 1 root root 275072020 2009-03-20 22:51 zypp-refresh.log
275M for a logfile? How can I put this under some kind of logrotate or something to keep the size less than 10M or so? Do I just add it to the existing logrotate or do I just write a script to do it? For the curious, the last 1000 lines of the log file are available at:
http://www.3111skyline.com/download/openSUSE_bugs/110/zypp-refresh-1000.log .bz2
(size: 11k)
Is this a bug, feature or result of all the repository failures lately?
I have logrotated zypp-refresh.log files dating back to November with size ~10MB, also zypper-1.1.0 (factory) includes the related logrotate file, and the log was last appended to in December (opensuse 11.1).
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
auxsvr＠gmail.com -
Bob Williams -
Carlos E. R. -
David C. Rankin -
Jan Ritzerfeld -
Joe Morris -
Marcus Meissner -
Rajko M. -
Rodney Baker