Atomicorp

What you really need to do is upgrade to 5.3 from the ART repo. You can do this before you upgrade to Plesk 10, and I think in this case you need to. Faris thank you for the reply and for the nice warning. By the quote above you mean yum upgrade php* . This is not updating... So is yum install php5...

Thx for the attention and the message. Ples 10.4. offers a PHP5.3 support and the ability to jump to PHP5.3. That is when I ment packages from PLESK. I will try to update by removing first the ioncube ignoring dependencies. One more question: if php53-* are installed through EL5, does that count as ...

If you select PHP 5.3 in the Plesk autoinstaller on EL5 then the php53-* packages will be installed, not the PHP 5.3 php-* packages from Atomic. I'm not sure which of these two PHP distributions you intend to use, you might have some packages mixed up right now. I'd start by getting an overview of ...

Any help`?
yun upgrade php-ioncube-loader.* does not do anything...

Try upgrading it with yum instead. You're invoking a manual "install" event rather than an "upgrade", which treats the package as new rather than pathed-same. Hey Scott, Thx for replying. I did a yum clean all to remove all headers. Runned a yum update and the list does not show...

OK, no problem. Seriously, Nginx is too slow! I am gonna try installing a second Apache instance for serving static content. At the moment my actual apache is loaded with PHP and other modules and is faster serving files from the same server than nginx which is configured with no mods at all. Yes, ...

After selecting the version 5.3 the autoinstaller downloads the necessary files but suddenly fails with: ERROR: Unable to proceed with the installation until the package php-ioncube-loader-1:3.3.20-1.el5.art.x86_64 is removed from the system. Not all packages were installed. Please resolve this issu...

Scott,
Are you ever planning on offering apache upgrades through your yum repo?

scott wrote:What IP are you coming from?

82.165.147.43

How can we solve it?
It is still going and I can access your server just fine from other servers.

I am having some problems reaching the atomicorp.com from my server. The server is hosted on the same network as atomicorp. tracert atomicorp.com traceroute to atomicorp.com (82.165.242.46), 30 hops max, 40 byte packets 1 myhostname.hostdomain.com (82.165.147.xx) 3000.470 ms !H 3000.474 ms !H 3000.4...