[opensuse] Strange RPM Problem
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'. What I've noticed is that this always seems to follow a yast RPM problem. I'll go into software management and the program just hangs before it should go into the search window. After that, the software management doesn't check sources, but after a long wait announces that the RPM catalog can't be accessed because another program is using it. No other program seems to be using it. Then when I reboot, everything seems fine ... until the next time it happens. Any ideas? Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Aug 17 2007 08:31, Jim Sabatke wrote:
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'.
First question: does `ls -n` NOT hang in that case? Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Engelhardt wrote:
On Aug 17 2007 08:31, Jim Sabatke wrote:
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'.
First question: does `ls -n` NOT hang in that case?
Jan
Yes, 'ls -n' does freeze the system. The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar. Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program. TIA, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Aug 17 2007 09:47, Jim Sabatke wrote:
Jan Engelhardt wrote:
On Aug 17 2007 08:31, Jim Sabatke wrote:
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'.
First question: does `ls -n` NOT hang in that case?
Yes, 'ls -n' does freeze the system.
The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar.
Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program.
That sounds much like a kernel issue. Or bad hardware. Other thoughts would be processes in D state, or hung network mounts. Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Engelhardt wrote:
On Aug 17 2007 09:47, Jim Sabatke wrote:
Jan Engelhardt wrote:
On Aug 17 2007 08:31, Jim Sabatke wrote:
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'. First question: does `ls -n` NOT hang in that case? Yes, 'ls -n' does freeze the system.
The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar.
Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program.
That sounds much like a kernel issue. Or bad hardware. Other thoughts would be processes in D state, or hung network mounts.
Jan
I do see a message on reboots that an NFS mount is in use. I didn't think much of it as I didn't have any programs that I know of accessing that NFS mount. I do have two NFS mounts attached to my home directory. Also, I seem to need to run rpm --rebuilddb to get yast's software install to work, and then it usually just works one time and won't again until I reboot. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jan Engelhardt wrote:
On Aug 17 2007 09:47, Jim Sabatke wrote:
Jan Engelhardt wrote:
On Aug 17 2007 08:31, Jim Sabatke wrote:
I'm having somewhat the same problem as I reported a few weeks ago. Occasionally my home directory locks up on an 'ls'. First question: does `ls -n` NOT hang in that case? Yes, 'ls -n' does freeze the system.
The problem usually (to my memory) if not always happen when a message comes from any program using the RPM database. I get errors that the RPM database is in use by another program, or that the program is waiting for a lock on the RPM database. After that point, my system is fubar.
Also, lsof doesn't return anything, so I can't search for what is grabbing the RPM database, but I suspect a lot of the time it's the update program.
That sounds much like a kernel issue. Or bad hardware. Other thoughts would be processes in D state, or hung network mounts.
Jan
I finally got an lsof to work, and it looks like Beagle was attaching itself to the NFS mounts. BTW, it was a real PITA to get rid of Beagle; I had to go through a LOT of dependency fixes to get it off the machine, including a lot of gnome functionality. I haven't had a crash since I removed Beagle, but I don't think the system has been running long enough to really tell. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On 8/18/07, Jim Sabatke <jsabatke@sbcglobal.net> wrote:
I finally got an lsof to work, and it looks like Beagle was attaching itself to the NFS mounts.
This would only be the case if your NFS mount was in your home directory. Rather than uninstalling Beagle, you could tell it not to index those directories. The "Search and Indexing" properties in the control panel (in GNOME; not sure how you get to it from KDE, but you can just run "beagle-settiings") is where you can configure that. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 8/18/07, Jim Sabatke <jsabatke@sbcglobal.net> wrote:
I finally got an lsof to work, and it looks like Beagle was attaching itself to the NFS mounts.
This would only be the case if your NFS mount was in your home directory. Rather than uninstalling Beagle, you could tell it not to index those directories.
Just why does not beagle come with an opt-in strategy rather than opt-out? It's so disgusting... Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Jan Engelhardt -
Jim Sabatke -
Joe Shaw