Atomicorp

qlex wrote:

Code: Select all

Downloading packages
Running rpm_check_debug
Running Transaction Test
Killed

Qlex

OK. I know what this is. It is an OOM (Out Of Memory) issue in your Virtuozzo VPS.

Bottom line: You have centos 5.x (where x < 6) installed at the moment, and when you run yum update things go wrong because yum uses too much memory when doing so as there's a heck of a lot for yum to do and figure out. Unfortunately this causes Virtuozzo to kill the yum process and leave you with incomplete transactions. BUT, worst of all, when you try to do run yum update again, yum will simply stall, unkillably, invisibly. It does not help that you are trying to update Atomic stuff (e.g. php) at the same time.

Here's my suggestion. No guarantees. At your own risk! I'd let your provider do whatever he things best personally, as he'll be able to see what's happening and deal with it as required. But if you decide not to, here's what might help:

1) Reboot your VPS
2) Install yum-utils [yum install yum-utils](You will see an error when you do anything with yum following your earlier "killed" issue, which talks about incomplete transaction. Do not worry. We will deal with this shortly, and yum-utils is what we'll use to deal with it.

2a) I'd disable the Atomic repo in order not to upgrade php to 5.3 right now. Update the OS THEN update php/mysql etc.

3) Follow the Centos-recommended method to update from an ealier version of Centos Centos (5.4) to Centos 5.6. If you already have 5.5 it isn't strictly necessary to do this, but it will help you anyway.

This is as follows:

yum clean all
yum update glibc\*
yum update yum\* rpm\* pyth\*
yum clean all
yum update mkinitrd nash
yum update (do not do this yet though!)

4) Now, instead of running yum update right at the end there, reboot your VPS THEN run yum update. This should allow yum to do its thing with plenty of memory.

5) Re-enable the Atomic repo.

6) run yum-complete-transactions
This will clear your previous errors. It may well also install the atomic php and other stuff because they will be incomplete from the first time you ran yum update, and yum-complete-transactions will resolve that.

HOWEVER, I'm not completely sure what will happen with the Atomic repo disabled in step 2a. In may be that doing that is a bad idea and you should leave it enabled. I'm suggesting that you disable it in order to reduce the potential for problems, but there's a possibility that it will cause more problems with it disabled than with it enabled. I'm sorry but I don't know for sure -- maybe someone else will comment on this?

Incidentally, I know it is an OOM because it has happened on three Centos 5 VPS I've updated from 5.5 to 5.6 under Virtuozzo, and I know this is a VPS and I'm reasonably sure it is a Virtuozzo one. The method I've outlined (rebooting before final yum update) worked 100% of the time on the other VPSes I updated once I'd figured out what was going on. You will not find anything in /var/log/messages in the contrainer, but your hosting company will see the OOM errors in /var/log/messages in the hardware node itself.

Faris.

scott: i wrote to support, they first offered paid professional services but when i sent a request to perform that update of php, they wrote back that they dont accept my request - first time ever, a provider express disinterest of earning money !

faris,
first of all, thanx a lot for your fantastic tutorial - you spent much time writing that post.I must say I almost (!) finished it.

followed your tutorial to the stage where i (after restarting container using the Power Panel) i run yum update.
After this process downloaded all packages i get a "killed" message with the last rows from ssh saying:
(104/105): libgcj-4.1.2-50.el5.i386.rpm | 16 MB 00:02
(105/105): java-1.6.0-openjdk-1.6.0.0-1.21.b17.el5.i386. | 37 MB 00:12
------------------------------------------------------------------------------
Total 2.7 MB/s | 195 MB 01:12
Running rpm_check_debug
Running Transaction Test
Killed
[root@vps147363 ~]#


Then, when i tried to run yum-complete transactions i got:

[root@vps147363 ~]# yum-complete-transactions
-bash: yum-complete-transactions: command not found
[root@vps147363 ~]# php -v
PHP 5.1.6 (cli) (built: Nov 29 2010 16:47:37)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies


Obviously enabling atomic repo now with:
wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh
and typing 'yes' to allow license, it stalls again at:
Installing the Atomic GPG key:

arrghhhh!
I will try several more times (without disabling the repo maybe) and will report if anything changes

I noticed, that when performing yum update, that php 5.3 was "scrolling" among other packages but it ended with this "killed"

Qlex

Really? What was the case number?

That being said you're in the weird world of one-off VPS problems here. Its not a packaging problem here, I suspect that even with access to the system its not fixable. The problem I'm guessing is the way the host OS is restricting resources to the guest OS.

scott: so you're saying that i shouldnt even bother trying to update php to higher than 5.1.6 myself ?

they havent provided a reason why they dont want to take this request.

edit: how do i disable atomic repo - just want to follow faris' tutorial but i believe i havent disabled it ?
is it yum --disablerepo==atomic
?

they havent provided a reason why they dont want to take this request.

Who hasnt responded?

My VPS provider, who's supposed to perform the php update for me
www.superhost.pl are those guys

so the VPS provider didnt respond, or we didnt? If you ever open a case with us you'll get a tracking number sent to you automatically

I meant, my VPS didnt want to update the php (which i ordered them to do), so im back to doing it myself and that's why i wanted to follow atomicrepo tutorial to update manually

any further hints on how to do it, without ending up with "killed" message? BTW, my centos is 5.5

SOLVED !

I browsed around and used this tutorial:
http://www.webtatic.com/packages/php53/

Maybe a hint to atomic, to check what are the differences in both repos, that this webtatic repo seemed to work for me

Theres nothing wrong with the packages, thats a message coming from your OS. Not yum or our packages.

Thanx anyways, you helped a lot and i appreciate it.