Closed xpfgsyb closed 3 years ago
Hi, I'm having a similar experience. Right now I'm going through this website: https://snipe-it.readme.io/docs/requirements At first glance, I can see some additional PHP extensions that weren't required with SnipeIT v4.9.5 (for example: JSON, BCMath, Tokenizer, etc. I am running on a Window Server 2016 Standard server. I have Git installed on the server and ran php upgrade.php I have to stop for now but will share if/when I figured this out. Thanks.
Snipe-IT DocumentationThe requirements for Snipe-IT are fairly standard for a modern web server, and most servers will have most or all of these components already installed. If for some reason you don't have them installed, they are relatively easy to add.
I'm seeing a few things here...
SHA384 is not supported by your openssl extension, could not verify the phar file integrity
As for the withCookieSerialization()
error, that's due to missing PHP extensions. (They were always required, since v2, but you could get away with not having them before.)
Also if you do a git pull from master, I have improved the upgrader to provide you with more feedback about what you might be missing.
Stack OverflowI get the error when i run composer self-update on Windows 10 Here is the full error message composer self-update Updating to version 1.8.4 (stable channel). Downloading (100%) ...
Snipe-IT DocumentationCommon installation/upgrading issues and solutions
What a challenge, but I got it working. Maybe my steps will help the others here too.
0) Always have a backup.
1) Make sure you have all PHP dependencies. That was no problem for me because I already had all of them installed and enabled.
2) I had to update composer:
mv composer.phar composer.phar.backup
curl -s https://getcomposer.org/installer | php
3) Remove everything from the vendor directory:
cd vendor
rm -r *
4) Run composer install:
php composer.phar install --no-dev
5) Run the upgrade:
php upgrade.php
That didn't work for me at the first try because the database migrations failed. I got errors like SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs (SQL: alter table 'settings' add 'depreciation_method' char(10) null default 'default')
. Additionally I was not able to login via LDAP/AD after the update. That took my some time, but I was able to fix it with the tip in https://github.com/snipe/snipe-it/issues/7949#issuecomment-613338277 and to run the DB migration again.
I hope this does help somebody else too. Additionally, I want to thank you for your great efforts in developing Snipe-IT! Most of the time it does work without a problem and Snipe-IT is a really big help in our daily life.
That’s great news. Thanks for sharing !!!
Cameshia
Get Outlook for iOShttps://aka.ms/o0ukef
From: xpfgsyb notifications@github.com Sent: Thursday, November 12, 2020 4:34:29 AM To: snipe/snipe-it snipe-it@noreply.github.com Cc: Cameshia Cargle ccargle@txamfoundation.com; Comment comment@noreply.github.com Subject: Re: [snipe/snipe-it] Upgrade from 4.9.5 to 5.0.4 fails - undefined method plus composer errors (#8677)
What a challenge, but I got it working. Maybe my steps will help the others here too.
Always have a backup.
Make sure you have all PHP dependencies. That was no problem for me because I already had all of them installed and enabled.
I had to update composer: mv composer.phar composer.phar.backup curl -s https://getcomposer.org/installer | php
Remove everything from the vendor directory: cd vendor rm -r *
Run composer install: php composer.phar install --no-dev
Run the upgrade: php upgrade.php
That didn't work for me at the first try because the database migrations failed. I got errors like SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs (SQL: alter table 'settings' add 'depreciation_method' char(10) null default 'default'). Additionally I was not able to login via LDAP/AD after the update. That took my some time, but I was able to fix it with the tip in #7949 (comment)https://github.com/snipe/snipe-it/issues/7949#issuecomment-613338277 and to run the DB migration again.
I hope this does help somebody else too. Additionally, I want to thank you for your great efforts in developing Snipe-IT! Most of the time it does work without a problem and Snipe-IT is a really big help in our daily life.
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/snipe/snipe-it/issues/8677#issuecomment-725992742, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGEAFJAMFYTWYSVWM5DOM5LSPO23LANCNFSM4TJ2C37Q.
Please confirm you have done the following before posting your bug report:
Describe the bug I tried to upgrade from 4.9.5 to 5.0.4 with the upgrade.php script. There are already some errors during the upgrade, but no hints about missing php modules:
After the upgrade I only get the error message "Whoops, looks like something went wrong" in the browser window, also in a private tab without cookies.
I already found the other tickets about the Passport::withCookieSerialization problem and the possible solution on the "Installation/Upgrading Issues" page, but if I remove the contents of the vendor directory and run "php composer.phar install --no-dev" I only get another error (see screenshot), so that's a dead end in my case. php-ldap and php-bcmatch are both available on the system.
I guess the composer error is the main problem here. So I tried to update composer by renaming the old composer.phar file and to reinstall it as per the instructions on the "Install Dependencies" page. It installs fine, but running "php composer.phar install --no-dev" with the new version (composer 2.0.4) only outputs a fatal error; see section error messages. So just another dead end.
Do you have any tips what else I can try?
To Reproduce Steps to reproduce the behavior:
Expected behavior A working Snipe-IT installation after the upgrade.
Screenshots
Server (please complete the following information): - Snipe-IT Version -> 4.9.5 - OS: [e.g. Ubuntu, CentOS] -> Debian 10.6 - Web Server: [e.g. Apache, IIS] -> Apache 2.4.38 - PHP Version -> 7.3.19-1~deb10u1
Additional context
Error Messages I post three things: the output of php upgrade.php, the error message in laravel.log of a single page visit and the output of the current composer version.
Output of php upgrade.php