https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c1 --- Comment #1 from David Rankin 2008-01-19 19:31:05 MST --- The problem looks like it is in the oss repository: root@bonza:/home/david # zypper up -t package * Reading repository 'x11' cache * Reading repository 'mail' cache * Reading repository 'samba' cache * Reading repository 'kde-backports' cache * Reading repository 'php' cache * Reading repository 'nvidia' cache * Reading repository 'packman' cache * Reading repository 'main' cache * Reading repository 'kde-community' cache * Reading repository 'nonoss' cache | Reading repository 'oss' cacheSegmentation fault rebuilding the cache db removed ~ 30Meg from the zypp.db root@bonza:/var/cache/zypp # l total 120916 drwxr-xr-x 3 root root 4096 2008-01-19 19:46 ./ drwxr-xr-x 18 root root 4096 2008-01-04 14:39 ../ -rw-r--r-- 1 root root 76540928 2008-01-19 18:09 oldzypp.db drwxr-xr-x 16 root root 4096 2008-01-19 19:46 raw/ -rw-r--r-- 1 root root 47127552 2008-01-19 19:46 zypp.db I can now run yast2 ncurses without the segfault, but this bandaid doesn't explain how the oss repo cache was corrupted in the first place. y2logs to follow. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191099|text/plain |application/x-gzip mime type| | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c3 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |drankinatty@suddenlinkmail.com Summary|YaST2 ncurses crashes on Online Update or |crash on Online Update or Software Management |Software Management |start --- Comment #3 from Ladislav Slezak 2008-01-23 01:56:17 MST --- The problem is not ncurses UI specific if it crashes also in zypper. What had you done before it stopped working? Please try to reproduce in the debugger and attach the backtrace. (see http://en.opensuse.org/Bugs/YaST#How_can_I_start_YaST_in_debugger_.28gdb.29.... for details how to do it.) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c5 --- Comment #5 from David Rankin 2008-01-26 00:58:49 MST --- Guys, So far, I haven't been able to create the bug with the new repository refresh. The repository state that caused the crash is available for your download at the address in comment #4. Let me know if you want me just to submit the file, but I thought you would rather just download it at your convenience. Thanks -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c7 --- Comment #7 from David Rankin 2008-02-11 10:46:19 MST --- Guys, I will have to wait until the system crashes to provide you with information additional to the logs captured and referenced above. One problem we continue to regularly experience that is probably the root cause of this bug is the dramatic growth in /var/cache/zypp/zypp.db size. Just this weekend I had to delete and refresh zypp.db that had again grown from its normal refresh size of 43M to over 105M. At the time I deleted it, it was still functional, but getting very slow. This growth is occurring each time zypper or YOU or Yast2 software management is run. (i.e. each time the repositories are refreshed prior to update or install) I would like for you to provide me with some feedback so I know I am not wasting my time monitoring this bug. I haven't had any feedback since 1/23 despite making two sets of suspect zypp.db available. Were you successful in reproducing the lockup using the http://www.rbpllc.com/download/oldzypp.db.bz2 I provided? Let me know what else to do. Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c9 David Rankin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|drankinatty@suddenlinkmail.com | --- Comment #9 from David Rankin 2008-02-20 22:37:53 MST --- Sorry, I forgot the mark the information provided in my prior posts -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c10 --- Comment #10 from David Rankin 2008-03-03 19:24:52 MST --- Devs, It looks like a bulk of the problems were caused by a spurious memory address failure in one of the ocz platinum ram sticks. The sticks checked fine with memtest86+ only a few months ago at 10.3 install. Subsequent to the install it looks like one of the stick just "went bad" and started failing at several memory addresses. I replaced the sticks four days ago and I haven't experienced and of the zypp.db wild cache size growth that had been occurring. I'll watch it for a few more days and come back and close the bug it the memory replacement resolved the problem. Thanks for you help. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=354963 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354963#c12 --- Comment #12 from David Rankin 2008-04-25 15:50:58 MST --- Yes, Weird error, but having OCZ RMA the memory fixed the issue. -- 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.