Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: haymann on January 16, 2007, 05:06:05 PM

Title: Yum Running - Forever...
Post by: haymann on January 16, 2007, 05:06:05 PM
A few days ago I attempted to install the updates that were listed in the Software Installer panel. There were 502 updates available so I was expecting it to take awhile however my server has been stuck on 177 of the 502 for over 2 days now...

My question is, would rebooting the server help or hurt me? I have already noticed that the Horde webmail isn't working (I get a login screen, but then an error about redirect.php), but everything else seems to be working fine...

I am just a little concerned about rebooting while it is in the middle of updating...
Thanks,
Ryan
Title: Yum Running - Forever...
Post by: bpivk on January 16, 2007, 07:01:49 PM
This is't windows OS so reboot shouldn't hurt you.
I had some problems once and rebooting on linux didn't mess up my server (i won't even get into details for win).

As for your problem. Did you try and enter "yum update" in console?
Title: Yum Running - Forever...
Post by: haymann on January 16, 2007, 07:24:45 PM
Quote from: "bpivk"
Did you try and enter "yum update" in console?
I did and got this
Code: [Select]
Existing lock /var/run/yum.pid: another copy is running. Aborting.

I have rebooted a few times w/ Linux, but never as it was doing updates... My biggest fear is that it wouldn't load again.
Thanks,
Ryan
Title: Yum Running - Forever...
Post by: bpivk on January 16, 2007, 07:27:03 PM
Quote from: "haymann"
Quote from: "bpivk"
Did you try and enter "yum update" in console?
I did and got this
Code: [Select]
Existing lock /var/run/yum.pid: another copy is running. Aborting.


Just wait a little. This code means that yum is running. This happens when you reboot. Just wait a minute or two and then try it.

Well linux is quite good when it comes to updating. I never had an error when i rebooted in the midle of updating (note that i had to do it only three times on suse distro).
Title: Yum Running - Forever...
Post by: haymann on January 16, 2007, 08:04:41 PM
Sorry for the confusion, I still haven't rebooted yet... Yum is still running from last Friday... I'll try a reboot when I get home tonight, I don't have access from here.

Here is another thought... Can I force yum to close and try again? Would that be any different than rebooting?
Thanks,
Ryan
Title: Yum Running - Forever...
Post by: bpivk on January 16, 2007, 08:15:25 PM
Yes you could do that.
I think that
/ps aux|yum
/kill "pid number"
would do it. I don't know of any other simpler way.
Title: Yum Running - Forever...
Post by: stephen noble on January 16, 2007, 09:08:47 PM
problems to the bug tracker
see below maybe others
http://bugs.contribs.org/show_bug.cgi?id=2288
Title: Yum Running - Forever...
Post by: rkscscc on January 17, 2007, 09:54:09 AM
haymann, which version of SME are you running right now that you are getting 502 updates available?  Also, have you added extra repositories?

I'm running 7.0 at one site and the max amount of updates it gives me is 242, but I reckon I'd rather walk in there with a shiny new version 7.1 and just update the system from there...
Title: Yum Running - Forever...
Post by: chris burnat on January 17, 2007, 10:55:58 AM
I remember seeing a bug a Bugzilla to the effect that rebooting during a yum update could lead to problems.  Check it out before doing damage to your system...
Title: Yum Running - Forever...
Post by: haymann on January 18, 2007, 04:31:21 PM
Quote from: "rkscscc"
haymann, which version of SME are you running right now that you are getting 502 updates available?  Also, have you added extra repositories?

I'm running 7.0 at one site and the max amount of updates it gives me is 242, but I reckon I'd rather walk in there with a shiny new version 7.1 and just update the system from there...
It was 7.0 and I have SME Server - addons; SME Server - os; SME Server - updates; and SME Server - dungog as repositories.

I ended up rebooting the server and when it came back up (thank goodness :D  :D ) I tried using yum from the CLI. It kept failing a dependancy check for OpenSSH so I went back to server-manager -> Software Installer and de-selected the two OpenSSH updates. The update took awhile, but was successful. I still haven't gotten OpenSSH to update.

Server-manager now reports that I am using SME 7.1

I don't know where all of the "extra" updates came from... I am using Dansguardian, SARG, Awstats, and remoteuseraccess from dungog; perhaps that is why there were more??