Topic: yum update issue

[xof]

Hi,

I was running 'yum update' through a Putty session when that session crashed. Stupid me! Forgot to use 'screen' this time.

I guess 'yum update' has been brutally stopped in the middle. When I run the command again now I get missing dependencies.

Any way how to fix this?

I've had this with another CentOS machine as well (not SME) and I fixed it with running the command yum-complete-transaction. That command doesn't seem to work in SME though...

Any hints/tips?

[Stefano]

please report here the message.. let's try to solve..

[xof]

As this was kind of an urgent issue, I reverted back to a disk image I took before running the 'yum update'.

After putting the image back to the disk, I ran the update command again (from the GUI this time). All is well now.

I'm still wondering what happens when you interrupt yum while updating the system. I guess there's no fixed answer to that. Probably depends on where it is in the process. Still it's strange that running yum-complete-transaction on another CentOS machine fixes the issue and SME hasn't got that package on board...

[Stefano]

I'm still wondering what happens when you interrupt yum while updating the system. I guess there's no fixed answer to that. Probably depends on where it is in the process.

indeed

Still it's strange that running yum-complete-transaction on another CentOS machine fixes the issue and SME hasn't got that package on board...

well, open a NFR in bugzilla..

[cactus]

Still it's strange that running yum-complete-transaction on another CentOS machine fixes the issue and SME hasn't got that package on board...

That is because CentOS installs yum-utils which provides this tool ans SME Server does not as this is not required for normal use. Your issue originates from an interrupted yum update, which should not occur when using the normal SME Server methods. You should be able to install this manually if you like to be able to run it.

[janet]

xof

This may clean things up, and allow you to correctly run yum again. There have been similar reports recently fixed this way, without the need to install additional tools. It is in the FAQ too, so when you have an urgent need, please read available resources, as you have lost the opportunity to test that fix now under the circumstances you encountered.

yum clean all