Snipe-IT PHP 5.6 upgrade to 7.1

JaredBusch

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

I guess the core question I have that is irritating me is why can't I just point snipe-it to the updated version of php?

Did you attempt @black3dynamite's method above?

Not yet, as its mid-day and people are using the system.

That would be my recommendation then. shutdown the VM, make a snapshot, then power it on and try that.

Will do.

Would be wonderful to find a way to do this without having to "brute force it".

Something in the .env file or some other config file has to point to the php.ini location to be used.

DustinB3403

@jaredbusch It's not in the .env file, looking at mine currently.

JaredBusch

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch It's not in the .env file, looking at mine currently.

The entire point of using the IUS repo is not not use the default php.ini which is PHP 5.4 on CentOS 7, so there has to be something to find the php.ini file for the application.

DustinB3403

@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?

JaredBusch

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?

Nope. That is not how CentOS (RHEL) works.

DustinB3403

@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?

Nope. That is not how CentOS (RHEL) works.

Hrm. . .

Not that I'm disagreeing, I just don't know. In following a guide on D.O. 7.1 was in pre-release at the time and not available in the repo's yet. So if I was running the process at the time I would've had to add the repo to get it. . .

scottalanmiller

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch said in Snipe-IT PHP 5.6 upgrade to 7.1:

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@jaredbusch Is it possible that php5.6 was in a pre-release state and just not available on centos 7 at the time?

Nope. That is not how CentOS (RHEL) works.

Hrm. . .

Not that I'm disagreeing, I just don't know. In following a guide on D.O. 7.1 was in pre-release at the time and not available in the repo's yet. So if I was running the process at the time I would've had to add the repo to get it. . .

Those are coincidental. It was prerelease and not available in the repos. But even when released, doesn't go to the repos.

black3dynamite

I guess you can try this to confirm what version is being used with apache. Add this to the /var/www/html/ or whatever your root document path is.

# phpinfo.php
<?php
// Show all information, defaults to INFO_ALL
phpinfo();
?>

DustinB3403

@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:

I assume this would be the way to remove 5.x and install 7.x

# Stop httpd and mariadb
systemctl stop httpd
systemctl stop mariadb

# Remove all php and php modules
yum -y remove php*

# Add IUS Repo (Unless already added)
yum -y install epel-release
yum -y install https://centos7.iuscommunity.org/ius-release.rpm
rpm --import /etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY

# Install PHP 7.1
yum -y install php71u php71u-mysqlnd php71u-bcmath php71u-cli php71u-common php71u-embedded php71u-gd php71u-mbstring php71u-mcrypt php71u-ldap php71u-json php71u-simplexml

# Start httpd and mariadb
systemctl start httpd
systemctl start mariadb

Well this did work, which awesome thank you for that. Now using PHP 7.1.13.

Edit: I checked to see who was using the system (we have a handful and just skype'd em) and told them to give me a minute.

DustinB3403

So now to annoy @JaredBusch, is there a reason why with the install script that it can't pull down these updates?

I know you didn't create it from scratch, just poking you.

travisdh1

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

So now to annoy @JaredBusch, is there a reason why with the install script that it can't pull down these updates?

I know you didn't create it from scratch, just poking you.

https://dobrador.com/wp-content/uploads/2017/02/Do-Not-Poke-the-Dragon.jpg

zachary715

So just spun up a new Fedora VM and installed Snipe-IT via script.

If I click the link about testing the .env file, it goes to the 404 page as expected. If I click next...

DustinB3403

the 404 page, IIRC means its working as intended

and that this test, actually is a false alarm.

zachary715

@dustinb3403 said in Snipe-IT PHP 5.6 upgrade to 7.1:

the 404 page, IIRC means its working as intended

and that this test, actually is a false alarm.

Correct. Looking for logs now to post and see if someone can help spot the issue. Can't remember where I found them before.

black3dynamite

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

So just spun up a new Fedora VM and installed Snipe-IT via script.

If I click the link about testing the .env file, it goes to the 404 page as expected. If I click next...

Temporary disable SELinux and try again.
setenforce 0

zachary715

@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

So just spun up a new Fedora VM and installed Snipe-IT via script.

If I click the link about testing the .env file, it goes to the 404 page as expected. If I click next...

Temporary disable SELinux and try again.
setenforce 0

So that makes the .env file section of the pre-flight page go green, but next page still shows the "Whoops" page. Should I try to reinstall but precede the installation with setenforce 0?

black3dynamite

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

So just spun up a new Fedora VM and installed Snipe-IT via script.

If I click the link about testing the .env file, it goes to the 404 page as expected. If I click next...

Temporary disable SELinux and try again.
setenforce 0

So that makes the .env file section of the pre-flight page go green, but next page still shows the "Whoops" page. Should I try to reinstall but precede the installation with setenforce 0?

The script for Fedora should already be configured correctly, related SELinux.

JaredBusch

@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

@black3dynamite said in Snipe-IT PHP 5.6 upgrade to 7.1:

@zachary715 said in Snipe-IT PHP 5.6 upgrade to 7.1:

So just spun up a new Fedora VM and installed Snipe-IT via script.

If I click the link about testing the .env file, it goes to the 404 page as expected. If I click next...

Temporary disable SELinux and try again.
setenforce 0

So that makes the .env file section of the pre-flight page go green, but next page still shows the "Whoops" page. Should I try to reinstall but precede the installation with setenforce 0?

The script for Fedora should already be configured correctly, related SELinux.

Yes, this is an issue with F27. I remember that now. I never did figure it out as F27 dropped around SpiceWorld I think and I was a little busy being drunk.

I have a thread on here about it someplace I think.

black3dynamite

@zachary715
You can turn on debug by changing false to true in .env file, so you can see more information instead of Whoops, looks like something went wrong.

# REQUIRED: BASIC APP SETTINGS
# --------------------------------------------
APP_ENV=production
APP_DEBUG=true
APP_KEY=
APP_URL=
APP_TIMEZONE=America/Denver
APP_LOCALE=en