Submitted by anwoke8204 on Sun, 08/12/2018 - 00:40
I haven't done anything to remove php 5x on my system, I went to go setup a new site, and now it appears that php 5x is no longer on my server, just php 7. was this done as part of the process of upgrading from gpl to pro?
Status:
Closed (fixed)
Comments
Submitted by andreychek on Sun, 08/12/2018 - 08:47 Comment #1
Howdy -- nope! Virtualmin wouldn't remove your PHP packages there. When upgrading to Virtualmin Pro, it simply replaces one Virtualmin package with another.
What output do you receive if you run these commands:
ls /etc/yum.repos.d`rpm -qa | grep php
Also, can you paste in the output you receive when going into System Settings -> Re-Check Config?
Submitted by anwoke8204 on Sun, 08/12/2018 - 20:38 Comment #2
ls /etc/yum.repos.d
[root@websrv ~]# ls /etc/yum.repos.dCentOS-Base.repo CentOS-Vault.repo remi-php71.repo
CentOS-CR.repo epel.repo remi-php72.repo
CentOS-Debuginfo.repo epel-testing.repo remi-php73.repo
CentOS-fasttrack.repo remi-glpi91.repo remi.repo
CentOS-Media.repo remi-glpi92.repo remi-safe.repo
CentOS-SCLo-scl.repo remi-glpi93.repo virtualmin.repo
CentOS-SCLo-scl-rh.repo remi-php54.repo
CentOS-Sources.repo remi-php70.repo
rpm -qa | grep php
[root@websrv ~]# rpm -qa | grep phpphp-xml-7.0.31-1.el7.remi.x86_64
php-gd-7.0.31-1.el7.remi.x86_64
php-bcmath-7.0.31-1.el7.remi.x86_64
rh-php70-runtime-2.3-1.el7.x86_64
rh-php70-php-pdo-7.0.27-1.el7.x86_64
rh-php70-2.3-1.el7.x86_64
sclo-php70-php-mcrypt-7.0.27-1.el7.x86_64
php-tcpdf-dejavu-sans-fonts-6.2.13-1.el7.noarch
php70-php-common-7.0.31-1.el7.remi.x86_64
php-xmlrpc-7.0.31-1.el7.remi.x86_64
php-pear-1.10.5-6.el7.remi.noarch
rh-php70-php-xml-7.0.27-1.el7.x86_64
rh-php70-php-gd-7.0.27-1.el7.x86_64
rh-php70-php-opcache-7.0.27-1.el7.x86_64
wbm-php-pear-1.6-1.noarch
sclo-php70-php-imap-7.0.27-1.el7.x86_64
php70-php-json-7.0.31-1.el7.remi.x86_64
php-common-7.0.31-1.el7.remi.x86_64
php-pdo-7.0.31-1.el7.remi.x86_64
php-7.0.31-1.el7.remi.x86_64
php-mcrypt-7.0.31-1.el7.remi.x86_64
php-fpm-7.0.31-1.el7.remi.x86_64
rh-php70-php-zip-7.0.27-1.el7.x86_64
rh-php70-php-process-7.0.27-1.el7.x86_64
rh-php70-php-devel-7.0.27-1.el7.x86_64
rh-php70-php-bcmath-7.0.27-1.el7.x86_64
rh-php70-php-fpm-7.0.27-1.el7.x86_64
rh-php70-php-soap-7.0.27-1.el7.x86_64
php70-runtime-1.0-5.el7.remi.x86_64
php70-php-mysqlnd-7.0.31-1.el7.remi.x86_64
php-cli-7.0.31-1.el7.remi.x86_64
php-mysqlnd-7.0.31-1.el7.remi.x86_64
php-process-7.0.31-1.el7.remi.x86_64
php-ldap-7.0.31-1.el7.remi.x86_64
rh-php70-php-common-7.0.27-1.el7.x86_64
rh-php70-php-pear-1.10.1-3.el7.noarch
rh-php70-php-mysqlnd-7.0.27-1.el7.x86_64
rh-php70-php-pspell-7.0.27-1.el7.x86_64
php-tcpdf-6.2.13-1.el7.noarch
php70-php-pdo-7.0.31-1.el7.remi.x86_64
php-mbstring-7.0.31-1.el7.remi.x86_64
rh-php70-php-cli-7.0.27-1.el7.x86_64
rh-php70-php-mbstring-7.0.27-1.el7.x86_64
php-fedora-autoloader-1.0.0-1.el7.noarch
php-json-7.0.31-1.el7.remi.x86_64
php-tidy-7.0.31-1.el7.remi.x86_64
php-imap-7.0.31-1.el7.remi.x86_64
rh-php70-php-json-7.0.27-1.el7.x86_64
rh-php70-php-xmlrpc-7.0.27-1.el7.x86_64
php-php-gettext-1.0.12-1.el7.noarch
[root@websrv ~]#
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active .. Your system has 3.70 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB. BIND DNS server is installed, and the system is configured to use it.
TLSA DNS records will be added to new domains.
Mail server Postfix is installed and configured.
Postfix is configured to support per-domain outgoing IP addresses.
Apache is installed.
The following PHP versions are available : 7.0.27 (/opt/rh/rh-php70/root/usr/bin/php-cgi), 7.0 (mod_php)
PHP-FPM support is available on this system.
Webalizer is installed.
Apache is configured to host SSL websites.
MySQL is installed and running.
PostgreSQL is installed and running.
ProFTPD is installed.
Logrotate is installed.
SpamAssassin and Procmail are installed and configured for use.
ClamAV is installed and assumed to be running.
The System and Server Status module is installed and checking on schedule.
Plugin AWstats reporting is installed OK.
Plugin Administrator's Notes is installed OK.
Plugin DAV Login is installed OK.
Plugin DNS Domain Registration is installed OK.
Plugin New Mailbox Signup is installed OK.
Plugin PowerDNS Domain is installed OK.
Plugin Protected web directories is installed OK.
Plugin Slave DNS domain is installed OK.
Plugin Additional content styles is installed OK.
Plugin Additional content styles from OpenWebDesign.org is installed OK.
Plugin Virtualmin Support Links is installed OK.
Using network interface ens192 for virtual IPs.
IPv6 addresses are available, using interface ens192.
Default IPv4 address for virtual servers is 10.32.64.50.
Default IPv6 address for virtual servers is fe80::2485:f2a8:b55:4550.
Both user and group quotas are enabled for home and email directories.
All commands needed to create and restore backups are installed.
Resource limits are supported and configured correctly.
The selected package management and update systems are installed OK.
Chroot jails are available on this system
The Virtualmin YUM repository is configured correctly
.. your system is ready for use by Virtualmin.
Submitted by andreychek on Mon, 08/13/2018 - 08:51 Comment #3
Ah, it looks like several third party repositories have been enabled on the server there.
That's not something Virtualmin does, and can cause the issue you described.
What appears to have happened, is the third party repositories were enabled, and then next time updates were performed, packages from those third party repositories overwrote the standard ones that come from CentOS.
Our recommendation is not to enable any third party repositories since they're known to cause a variety of issues.
It's unfortunately not a simple process to correct that -- you'd need to review every package installed on the system, look for any that belong to a third party repository, and then replace it with the original that comes with CentOS.
Since it's such a complicated process, I'd probably suggest either just leaving things as they are and hoping for the best (but not having PHP 5), or, you might consider starting over with a fresh installation -- but on that one, don't enable any third party repositories.
Submitted by anwoke8204 on Wed, 08/15/2018 - 05:47 Comment #4
ok, which repo's do I need to disable/delete. I will probably work on building a replacement server but want to disable the repos that shouldn't be there so I dont foul more things up more. I think it happened when I was trying to figure out issues with getting drupal working and others that needed dependancies that would fail to install, so I took to google to try to solve the issue. won't make that mistake again on a production system.
Submitted by Jfro on Wed, 08/15/2018 - 06:23 Comment #5
First is this a live active production box?
Then if so you're sort of try on error with that? That combination is not so...
Then first things first.
Get a list of all Software/Apps that is really needed on that BOX first. Then wich versions and other needed extra's as also configs / settings for those.
Than have a look what is default / standard in Virtualmin Package. Then only after al this take a look to other repo's and things that are not default in Virtualmin or suplied by / for Virtualmin.
Yep we have running RemiPHP, orginal mariadb and CODEITGURU REPO's but that because at that time for example HTTP2 wasn't possible with Virtualmin CeNTOS repo. ( ONLY active one PHP 5.6 FPM REMI !!!) ( IF using third party repos take EXTRA care of testing and good complete backups, for Data and configs... also keep reading LOG FILES specially after updates)
If using other repos, you have to change mostly also yum config and yum update settings to block some <> repos changing / updating your wanted repo
Have in Mind Support from Virtualmin for other third party REPO"S is hard if they do you're lucky. ;)
and maybe read this topic https://www.virtualmin.com/comment/799065#comment-799065
Submitted by anwoke8204 on Wed, 08/15/2018 - 06:20 Comment #6
Yes this is an active box, currently hosting 7 domains with several sub domains for most of the sites for a total of 24 domains on the server. It is currently on Centos 7 (my preferred os), but if you recall some of the other tickets I opened I brought a debian based server online and had no issues with any of the scripts and dependancies being installed. so I am going to work to migrate the box over to a Debian based new server. That way I don't have to worry about having to install other repos for packages not found in the default repos, like I had with Centos 7 (my several tickets regarding this missing for this dependancy or that dependency for script installer). I am currently spinning up the Debian based VM as I type this.
Submitted by Jfro on Wed, 08/15/2018 - 06:27 Comment #7
Ok 'm not from Support. ;)
Question from me. At what date you did wich version installlation of Virtualmin on that BOX, this because at starting point Virtualmin 6 there where several problems with BUGS an defective incomplete downloads we experienced august, september 2017 and had to do more manual work.... ;)
Submitted by anwoke8204 on Wed, 08/15/2018 - 06:57 Comment #8
This box is only 4 or so months old.
Submitted by andreychek on Wed, 08/15/2018 - 09:43 Comment #9
We like the SCL repo for installing additional PHP versions, that should always be safe.
Using CentOS should work quite well, and there are a lot of PHP versions available when using the SCL repos. You should automatically get PHP 5.4 and 7.x on a new CentOS installation, and can install more yet from the SCL repo.
As far as what to disable -- all of the repos containing the name "remi" would need to be disabled.
Submitted by anwoke8204 on Mon, 09/03/2018 - 21:00 Comment #10
Submitted by anwoke8204 on Mon, 09/03/2018 - 21:43 Comment #11