http://bugzilla.opensuse.org/show_bug.cgi?id=1001668 http://bugzilla.opensuse.org/show_bug.cgi?id=1001668#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eduardoescofet@gmail.com Flags| |needinfo?(eduardoescofet@gm | |ail.com) --- Comment #1 from Michael Andres --- 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)? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1001668 http://bugzilla.opensuse.org/show_bug.cgi?id=1001668#c3 --- Comment #3 from Michael Andres --- 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

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1001668 http://bugzilla.opensuse.org/show_bug.cgi?id=1001668#c5 --- Comment #5 from Eduardo Escofet --- 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 -- You are receiving this mail because: You are on the CC list for the bug.