Bug 579910

Summary:	Zypper.log takes the whole filesystem
Product:	[openSUSE] openSUSE 11.1	Reporter:	David Montero Isusi <dark.orion>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description David Montero Isusi 2010-02-15 10:45:46 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6

Happened twice in two weeks. The laptop where it happens, is not updated frequently, so zypper log shouldnt be very big.

The problem was spotted when it prevented from logging in to kde, as the filesystem was full. I checked the /tmp dir, and was empty, so I looked for the problem, and I was surprised that /var/log was about 15GB, and all that info was on zypper.log

It's my gf laptop, so I have "limited" access, and she just wants it to work, so I made a init script, that deletes the zypper.log every time she boots.

She usually hibernates the laptop, but I am the one who updates the system (maybe once per month)

the content in /var/log/zypper.log was trivial to me (lots of repeated lines), but I'll take a look at it if necessary

Reproducible: Sometimes

Steps to Reproduce:
I dont know how to reproduce, as it's log related and we didnt use zypper
Actual Results:  
The log fills the / filesystem, resulting in login problems (specially graphical related)

Comment 1 Jan Kupec 2010-02-19 13:23:24 UTC

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.0)
> Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6
> 
> Happened twice in two weeks. The laptop where it happens, is not updated
> frequently, so zypper log shouldnt be very big.

Well, in this case, you should update :O) Seem you have hit bug 469872. Zypper 1.0.17 has the cure.

> Steps to Reproduce:
> I dont know how to reproduce, as it's log related and we didnt use zypper

The error happens on network timeouts, so it's pretty random. BTW, maybe it was a cron job (do you have Automatic Online Update configured?) or an updater applet that called zypper. In any case, it must have been zypper that caused this.

*** This bug has been marked as a duplicate of bug 469872 ***

Comment 2 David Montero Isusi 2010-02-19 13:38:26 UTC

ok, i'll try it next week (cant do it right now, as its not my laptop), i think its going to be solved with the update...

I should have tried updating first (its strange i didnt find the solved bug :S)

thanks