[Bug 207611] New: zmd fills /var/log, making the system unusable
https://bugzilla.novell.com/show_bug.cgi?id=207611 Summary: zmd fills /var/log, making the system unusable Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Zenworks AssignedTo: zlm-code10-bugs@forge.provo.novell.com ReportedBy: admin@eregion.de QAContact: jtariq@novell.com i'm running /var/log on a separate partition of 512 megs. now, zmd managed to FILL that in less than three weeks, mainly due to being overly verbose AND not having all of its logfiles (namely zmd-messages.log) configured in /etc/logrotate.d The results of a filled /var/log: - X11 refused to start - zmd and yast forgot ALL of their installation sources. since the machine in question is used as a desktop workstation, having no X11 is really annoying. Is there a way to stop zmd from sprouting megabytes of logfiles when doing nothing? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #1 from admin@eregion.de 2006-09-22 02:41 MST ------- i just found that yast still knows its sources. how do i get those back into zmd? refreshing them manually? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #2 from admin@eregion.de 2006-09-22 13:29 MST ------- i tried to add all the sources back, which first didnt work because zmd forgot to unlock its database. Anyways, I've set both log-level and syslog-level to "none" but /var/log/zmd-backend.log still keeps growing. just adding my installation sources back grew it from 0 bytes to over 60 megabytes! and since this source refresh happens at least once a day... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #3 from admin@eregion.de 2006-09-23 04:04 MST ------- i added zmd-backend.log to logrotate, and got a nice shiny empty logfile. then, i restarted zmd, which grew the logfile to FIFTY-SIX MEGABYTES! just now, the simple action of "rug sl" added another THIRTY MEGABYTES! btw, here's the output of "rug get -d|grep log: mathias@pippin:/var/log> rug get -d |grep log log-exception-traces | False log-level | off log-soap-xml | False syslog-level | off So i think the fact that four reboots (or rather, 4 restarts of zmd) are enough to fill /var/log (on a separate partition of 512megs) are enough to make my system unusable should be considered a critical flaw. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #4 from admin@eregion.de 2006-09-25 03:05 MST ------- just look at this: pippin:/var/log # head -1 zmd-backend.log ; tail -1 zmd-backend.log ; du -sch zmd-backend.log 2006-09-24 23:00:32 <1> pippin(32508) [parse-metadata] parse-metadata.cc(main):139 ------------------------------------- 2006-09-25 10:59:03 <1> pippin(26970) [media] MediaManager.cc(restoreAutoMounter):248 Restored HAL volume handling (automounter) 122M zmd-backend.log 122M total pippin:/var/log # its the first and the last line of zmd-backend.log. note the timestamps. note the size. tell me any valid reason for zmd being so chatty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|zlm-code10- |dmacvicar@novell.com |bugs@forge.provo.novell.com | ------- Comment #5 from visnov@novell.com 2006-09-25 06:08 MST ------- It's about the backend log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kkaempf@novell.com ------- Comment #6 from visnov@novell.com 2006-09-25 06:13 MST ------- Klaus, is this the bug you've fixed recently? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #7 from kkaempf@novell.com 2006-09-25 06:54 MST ------- Yes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #9 from admin@eregion.de 2006-09-25 06:57 MST ------- then put the fix out as an update to zmd... i'd even betatest it... oh and btw, /var/log/Yast2 is growing fast, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #10 from visnov@novell.com 2006-09-26 06:41 MST ------- Fixed for 10.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #11 from admin@eregion.de 2006-09-26 07:05 MST ------- and where's the patch for 10.1? i mean, this bug crippled my 10.1 machine once already... hence, reopened. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #12 from admin@eregion.de 2006-09-27 01:30 MST ------- just to get my point across: this morning my laptop wouldn't boot, again, due to /var/log full with 360megs of zmd-backend.log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dmacvicar@novell.com |visnov@novell.com Status|REOPENED |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 flucifredi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|jtariq@novell.com |visnov@novell.com ------- Comment #14 from flucifredi@novell.com 2006-10-11 16:00 MST ------- we are considering this fixed for 10.2, and we understand that NUE will use this bug to track a 10.1 patch. Stano, please route this to the appropriate QA contact. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 mauro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|visnov@novell.com |crivera@novell.com Status|ASSIGNED |NEW ------- Comment #15 from mauro@novell.com 2006-10-13 15:57 MST ------- Adding log rollback and delete old versions. Reassigning to Chris. Need to be released as patch for 10.1 users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 crivera@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #16 from crivera@novell.com 2006-10-16 12:21 MST ------- svn revision 35478 adds support for log-max-files-size preference in zmd. This is the total size of all zmd-messages.log files to keep around. The default is 50MB. Zmd uses log4net, which has support for rotating and removing old logs. This is fixed for 10.2. I set the log4net properties to stay at 50MB in the 10.1/SLED10 branch. I didn't add the preference here because it requires documentation and strings to be translated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #17 from admin@eregion.de 2006-10-16 13:21 MST ------- re #16:
This is fixed for 10.2.
and this helps me how? Remember, this bug was filed against 10.1. So, unless a patch for 10.1 is out, i can't consider this fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 flucifredi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |flucifredi@novell.com Status|REOPENED |RESOLVED QAContact|visnov@novell.com |mauro@novell.com Resolution| |FIXED ------- Comment #18 from flucifredi@novell.com 2006-10-16 16:11 MST ------- Mathias, the bug is first resolved in the HEAD of development, and if PM decides to, it is then backported to the previous releases as a Suse patch. This is the first step in fixing the problem, and now the bug will go to QA. Please watch your tone, as NUE has a standing practice to prioritize patient users over snappy ones so that the tone of the bugtracker remains civil. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #19 from flucifredi@novell.com 2006-10-16 16:11 MST ------- assigning to Mauro for testing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #21 from admin@eregion.de 2006-10-16 23:46 MST ------- re #18: Sorry, but this "we have a bug, we have a fix, we might not issue the fix for the current release, but we fix it in the next"-approach is not really helping to keep me patient. With the sheer number of 10.1 bugs that got a "fixed for 10.2" in this bugtracker, 10.1 customers should get a 10.2 for free. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #22 from ast@novell.com 2006-10-17 09:07 MST ------- released for 10.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #23 from admin@eregion.de 2006-10-17 09:20 MST ------- is that the libzypp-1.3.2-0.9 that came by RUG yesterday? thanks a lot, guys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #24 from admin@eregion.de 2006-10-17 12:22 MST ------- hm. pippin:/var/log # head -1 zmd-backend.log; tail -1 zmd-backend.log; du -sch zmd-backend.log 2006-10-17 20:08:15 <1> pippin(13231) [parse-metadata] parse-metadata.cc(main):139 ------------------------------------- 2006-10-17 20:14:09 <1> pippin(16328) [media] MediaManager.cc(restoreAutoMounter):248 Restored HAL volume handling (automounter) 2.7M zmd-backend.log close to 3 megs, just for starting zmd... and the content looks like zmd is still stuck on log-level=debug even when configured for "fatal"... And to put it out in the open, with log-level=fatal i expect nothing else than a timestamp like for starting zmd, a timestamp for stopping, and a line whenever an action fails to complete. For example, when zmd hits a 404 when getting a rpm file. nothing more. but still, its an improvement. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com