Atomicorp

Hello,

Probably due to a plesk update i don´t have multiple PHP anymore
I had the Plesk PHP Panda installed with Nucleus PHP 5.3 as my common PHP
After u yum upgrade i noticed in plesk panel i only had PHP 5.4 from the Atomic REPO
Eventhough I have done:
If you are using the Atomic repository you must add the line at the end of the [atomic] section in the /etc/yum.repos.d/atomic.repo file:
exclude=php*

I downgraded back to 5.3, and reinstalled plesk-php53-panda but i still have no multiple php.

If i do a yum upgrade it asks to upgrade to php 5.4 from the Atomic Repo eventhough i excluded it in the atomic.repo file.

Any idea on how to fix this and have multiple PHP back on my server with the Nucleus Repo?

Thanks

What does /usr/local/psa/admin/bin/php_handlers_control --list say you have?

PHP-FPM support for nginx service in plesk cp was stopped after start i could set the hostingsettings for domains back to fast-cgi and then i had a choice of multiple php.

sudo /usr/local/psa/admin/bin/php_handlers_control --list
id: display name: version: type: cgi-bin: php.ini:
module 5.3.28 5.3.28 module /usr/bin/php-cgi /etc/php.ini
fastcgi 5.3.28 5.3.28 fastcgi /usr/bin/php-cgi /etc/php.ini
cgi 5.3.28 5.3.28 cgi /usr/bin/php-cgi /etc/php.ini
fastcgi-54 Atomic 5.4 5.4.24 fastcgi /opt/atomic/atomic-php54/root/usr/bin/php-cgi /opt/atomic/atomic-php54/root/etc/php.ini
fastcgi-55 Atomic 5.5 5.5.8 fastcgi /opt/atomic/atomic-php55/root/usr/bin/php-cgi /opt/atomic/atomic-php55/root/etc/php.ini

When i now do yum update, I get 5.4.25 as default php and in the scroll-down menu i can choose between 5.4.25, atomic 5.4 and atomic 5.5 evethough php is excluded in the atomic.repo file.

in vi end of the atomi.repo file looks like this:
enabled = 0
priority = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
gpgcheck = 1
exclude=php*
~
~
~

After yum upgrade:
sudo /usr/local/psa/admin/bin/php_handlers_control --list
id: display name: version: type: cgi-bin: php.ini:
module 5.4.25 5.4.25 module /usr/bin/php-cgi /etc/php.ini
fastcgi 5.4.25 5.4.25 fastcgi /usr/bin/php-cgi /etc/php.ini
cgi 5.4.25 5.4.25 cgi /usr/bin/php-cgi /etc/php.ini
fastcgi-54 Atomic 5.4 5.4.25 fastcgi /opt/atomic/atomic-php54/root/usr/bin/php-cgi /opt/atomic/atomic-php54/root/etc/php.ini
fastcgi-55 Atomic 5.5 5.5.9 fastcgi /opt/atomic/atomic-php55/root/usr/bin/php-cgi /opt/atomic/atomic-php55/root/etc/php.ini

After 9 times downgrading i have it back to 5.3

So, is it OK? It wasnt clear from your post

Sorry scoot partly it is solved. I have multiple PHP but...
When i do a yum update my php53 get´s upgraded to the latest atomic54, eventhou th php is excluded in the atomic;repo file

So then i can choose in the dropdownmenu in hostingsettings in plesk cp between 5.4.25, atomic 54 and atomic 55

How to solve this;

That with yum upgrade my nucleus 5.3 gets updated when available and not overwritten by atomic 5.4. And the others from Plesk PHP Panda also gets updated,

Thanks in advance

12lamat wrote: (...) in vi end of the atomi.repo file looks like this (...)

If you read the atomic.repo file carefully you'll notice that the end of the file is for the atomic-testing channel.

So, you probably did not exclude the PHP packages from the atomic yum channel, which is why yum is proposing you to update PHP.

oops, yes i see,
Thank you many thanks,

Just to learn and ub-nderstand.....

When does this atomic.repo file gets overwritten, because it was there before?

I updated many times before!

and today suddenly atomic repo updated php.

12lamat wrote:oops, yes i see,
Thank you many thanks,

Just to learn and ub-nderstand.....

When does this atomic.repo file gets overwritten, because it was there before?

I updated many times before!

and today suddenly atomic repo updated php.

Recently an update to the package 'atomic-release' was released, which overwrites /etc/yum.repos.d/atomic.repo with the new file. The old file was saved to /etc/yum.repos.d/atomic.repo.rpmsave. A notification about overwriting configuration files would have been visible when the update was performed.

IMHO you should always pay close attention when performing updates, and never do unsupervised automatic updates, especially not with third-party repositories that provide additional packages, may update base packages, may not have a thorough QA, and may not follow EL package guidelines.

I would much rather have that the atomic-release package would not undo own customizations by activating the new configuration by default. This is a decision that Scott has made, and we sys admins have to live with Perhaps Scott can be convinced to place the repofile under "%config(noreplace)" in the rpmspec, effecitvely disabling the overwrite on updates. You would of course still have to diff and merge after an update to the repo file, but you can rest assured that your set excludes won't suddenly become inactive.