[Bug 206658] New: Move malformed database disk image automatically and create new
https://bugzilla.novell.com/show_bug.cgi?id=206658 Summary: Move malformed database disk image automatically and create new Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Zenworks AssignedTo: zlm-code10-bugs@forge.provo.novell.com ReportedBy: sven.burmeister@gmx.net QAContact: jtariq@novell.com Zmd's DB can be corrupted. I had this once or twice. The bad thing about it was that apparently I had to move the malformed DB manually although it was known to zmd that it was malformed: Failed to parse XML metadata: database disk image is malformed Would it make sense to move the malformed DB and let zmd create a new one instead of just failing? If not automatically one could offer a button to trigger the move/delete of the malformed DB. -- 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=206658 flucifredi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Status|NEW |NEEDINFO Info Provider| |tambet@ximian.com ------- Comment #1 from flucifredi@novell.com 2006-10-11 18:27 MST ------- the suggestion is interesting. Tambet might have input on this, needinfo-ing him and asking for his point of view. flaggin as enhancement. -- 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=206658 tambet@ximian.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|tambet@ximian.com | Resolution| |FIXED ------- Comment #2 from tambet@ximian.com 2006-10-12 00:31 MST ------- The DB gets corrupted only when when zmd or any of it's zypp helpers segfaults. Since zmd is written in managed code, it pretty much never segfaults, so all the blame is for zypp helpers. zmd tries hard to detect corrupted database at the startup, the algorithm for that is updated in 10.2 branch and should catch it better than before. It's not worth to backport the fixes to code10 branch because older version of sqlite just segfaults itself happily on corrupted database. -- 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=206658 ------- Comment #3 from andreas.hanke@gmx-topmail.de 2006-10-12 01:14 MST ------- I wouldn't say that the managed tools pretty much never crash: Bug 199061 has 6 duplicates in Novell bugzilla and thousands outside. It's the managed zen-updater which crashes there. I just did cp /var/lib/rpm/Packages /var/lib/zmd/zmd.db in order to feed zmd with an unusable database, and zen-updater nicely crashes on it. zmd does not, but zen-updater does. System.NullReferenceException: A null value was found where an object instance was required. at Novell.Zenworks.Gui.ZenTrayIcon.CheckUpdatesLoop () [0x00000] at (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () The perception is quite different outside... -- 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=206658 ------- Comment #4 from andreas.hanke@gmx-topmail.de 2006-10-12 01:30 MST ------- #3 is on 10.2 alpha 5, not 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.
participants (1)
-
bugzilla_noreply＠novell.com