Seth Vidal wrote:
On Wed, 25 Mar 2009, James Antill wrote:
Gerry Reno <greno@xxxxxxxxxxx> writes:
I've been noticing that when we do a 'yum update' and the package set
exceeds around 300 packages that we get a segmentation fault every now
and then. I've been restricting the updates to no more than 200 at a
time and we don't see the problem now.
This is with f9/f10 yum/rpm/etc. ?
My first guess would be that it's running out of memory, possibly
inside rpm itself (there was a bug with fingerprinting on kernel
updates that caused memory usage explosion).
But it's hard to say, can you get a backtrace from a core file?
Certainly nothing in yum can cause a SEGV without a bug somewhere
else.
It shouldn't be segfaulting - it could be oom-killing but not
segfaulting.
Run 'dmesg' and see what the system is reporting for that time.
-sv
The only segfault in dmesg is this:
python[9488]: segfault at 48 ip 073feb15 sp bfdbdaa0 error 4 in
libpython2.5.so.1.0[73a4000+125000]
Regards,
Gerry
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
