Bugzilla – Bug 1001668
Zypper update (apper also) crashes os (log fill all available space)
Last modified: 2016-09-28 15:39:05 UTC
Created attachment 694740 [details] zypperlog When updating using zypper or Apper, it crashes the OS because zypper.log increases its size to fill all hd available space.
Does a single(!) zypper call write such a big logfile? Or is the log growing normaly with each call, but never rotated (i.e. compressed and saved as zypper.log-YYYYMMDD.gz or .bz2 or .xz)?
Hi Michael This is the result of a single update (zypper), there's not rotation policy but the second time it crashed the system I created a zero-size zypper.log and in less than 2 minutes it's 8gb. I think this is a zypper (or libzypper) malfunctioning because the update never stops and it crashes the opensuse 13.2 if you let it "work" (I've got +50Gb free in this partition, so no room issue). Thanks
Zypper logs the output of the packages install scripts. If the update does not stop and the log is growing beyond limits, it might be some of the packages install script is running wild. I'd need the log to see what's going on. Please use the following command to extract the initial portion of the log, and attach the created /tmp/bsc1001668.log file. > cat /var/log/zypper.log | gzip | head -c 10M > /tmp/bsc1001668.log Then please save the original log in case I need some more data from it: > mv /var/log/zypper.log /var/log/zypper.log.bsc1001668
Created attachment 694778 [details] zypperlogok
I deleted it because it was binary gibberish. I tried twice with the same results (Apper update process at the os booting produced the same result). Then I deleted it, touch a new zypper.log and run Yast2 update and everything was ok. Now zypper is working as usual (I attached it), but I don't know why it was creating such a huge log file and crashed the system. Thanks
(In reply to Eduardo Escofet from comment #5) > everything was ok. Now zypper is working as usual (I attached it), but I > don't know why it was creating such a huge log file and crashed the system. To figure out which package update actually caused the trouble it would need the broken log. It may be that finally the package got updated, and the trouble is gone. It may of course be that the next update of this package will cause the same trouble again. We will see. In case it happens again, please try to save the broken log and REPOEN the bug.