ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Snipe-IT PHP 5.6 upgrade to 7.1

    Scheduled Pinned Locked Moved IT Discussion
    snipe-itupgradephpphp 5php 7centos 7
    54 Posts 7 Posters 7.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403
      last edited by

      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.

      travisdh1T 1 Reply Last reply Reply Quote 0
      • travisdh1T
        travisdh1 @DustinB3403
        last edited by

        @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.

        Do-Not-Poke-the-Dragon.jpg

        1 Reply Last reply Reply Quote 1
        • zachary715Z
          zachary715
          last edited by zachary715

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

          0_1516996282776_Pre-flight.PNG

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

          0_1516996553858_Whoops.PNG

          black3dynamiteB 1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

            the 404 page, IIRC means its working as intended

            and that this test, actually is a false alarm.

            zachary715Z 1 Reply Last reply Reply Quote 0
            • zachary715Z
              zachary715 @DustinB3403
              last edited by

              @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.

              1 Reply Last reply Reply Quote 0
              • black3dynamiteB
                black3dynamite @zachary715
                last edited by

                @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.

                0_1516996282776_Pre-flight.PNG

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

                0_1516996553858_Whoops.PNG

                Temporary disable SELinux and try again.
                setenforce 0

                zachary715Z 1 Reply Last reply Reply Quote 1
                • zachary715Z
                  zachary715 @black3dynamite
                  last edited by

                  @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.

                  0_1516996282776_Pre-flight.PNG

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

                  0_1516996553858_Whoops.PNG

                  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?

                  black3dynamiteB 1 Reply Last reply Reply Quote 0
                  • black3dynamiteB
                    black3dynamite @zachary715
                    last edited by

                    @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.

                    0_1516996282776_Pre-flight.PNG

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

                    0_1516996553858_Whoops.PNG

                    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.

                    JaredBuschJ 1 Reply Last reply Reply Quote 1
                    • JaredBuschJ
                      JaredBusch @black3dynamite
                      last edited by

                      @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.

                      0_1516996282776_Pre-flight.PNG

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

                      0_1516996553858_Whoops.PNG

                      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.

                      1 Reply Last reply Reply Quote 0
                      • black3dynamiteB
                        black3dynamite
                        last edited by

                        @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
                        
                        1 Reply Last reply Reply Quote 1
                        • 1
                        • 2
                        • 3
                        • 3 / 3
                        • First post
                          Last post