Description of problem: Update system, using the package updater, with security
update for hal hal, update completes and get request to reboot system. Click on
reboot and get an Exception error. (File attached)
Version-Release number of selected component (if applicable):
How reproducible: rerun package updater
Steps to Reproduce:
Created attachment 311646 [details]
How much memory does your machine have?
640Mb base + 384Mb other
That should be more than plenty -- the traceback is that there's not enough
memory to fork off and do the shutdown process. Have you seen this more than once?
I happens every time I try to run the update. Updates do not appear to
complete as they still show after reboot. I have a Hal and a bind update
showing. I can arrange access to the server should you need it, but would need
to exchange details over a more secure forum
When it happens, can you run 'free' and 'dmesg' in a terminal?
Ran update last night for 3 new patches, one of which was a kernal patch. It
threw the same error message when Tried to reboot, but after reboot the 3 new
patches appeared to have installed OK (no longer show on the updates list).
Tried to run update for the bind and hal update this morning in response to
your request,and system hangs resolving dependancies with the progress bar
about a quarter of the way along. The hard drive is being access continually.
It has now been running for at least half an hour. I will leave it til I get
home from work tonight and see what has happened and post any further info, and
hopefully the respose to your request.
Created attachment 312067 [details]
DMesg OUtput file
Update had finished when I got home. Attached the output file from dmesg.
Output from Free is a follows
total used free shared buffers cached
Mem: 384992 379912 5080 0 1580 32916
-/+ buffers/cache: 345416 39576
Swap: 0 0 0
The fact that swap is showing 0 accross the board worries me a bit as this was
a default installation which originally had a swap file in the LBV area of the
Yeah, based on that, the kernel is starting to OOM things which leaves little
room for us to actually do much about it. If you add swap back, I suspect
things will get a lot better. Running a full graphical session with 384 megs of
RAM is, sadly, a little optimistic sometimes these days :(
But as you noticed, the traceback won't at all affect the installation of
I would love to add swap back, as I have never taken it out. It still show up
as being present as a logical volume in the logical group. Where do I need to
go to fix.
I am also still unable to update the hal and bind packages. all other updates
seem to work
Check and make sure the swap partition is still listed in /etc/fstab, something like
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
(In reply to comment #13)
> Check and make sure the swap partition is still listed in /etc/fstab,
> /dev/VolGroup00/LogVol01 swap swap defaults 0 0
Many Thanks, That's solved all my problems