Upgrade not working - 6.0.13 to 7 or lastest

sakthimj commented 4 months ago

Debug mode

[X] I have enabled debug mode
[X] I have read checked the Common Issues page

Describe the bug

[diginaga@server asset]$ git pull There is no tracking information for the current branch. Please specify which branch you want to merge with. See git-pull(1) for details.

git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=<remote>/<branch> master

[diginaga@server asset]$ /usr/local/bin/ea-php81 upgrade.php

WELCOME TO THE SNIPE-IT UPGRADER!

This script will attempt to:

validate some very basic .env file settings
check your PHP version and extension requirements
check directory permissions
do a git pull to bring you to the latest version
run composer install to get your vendors up to date
run migrations to get your schema up to date
clear out old cache settings

STEP 1: Checking .env file:

Your .env is located at /home/diginaga/public_html/asset/.env

√ Your APP_KEY is not blank. √ Your APP_URL is not null or blank. It is set to https://asset.diginaga.com √ Your APP_URL is set to https://asset.diginaga.com and starts with the protocol (https:// or http://) √ Your APP_URL (https://asset.diginaga.com) does not have a trailing slash.

STEP 2: Checking PHP requirements:

Current PHP version: (8.1.29) is at least 7.4.0 - continuing... FYI: The php.ini used by this PHP is: /opt/cpanel/ea-php81/root/etc/php.ini

Checking Required PHP extensions...

√ bcmath is installed! √ curl is installed! √ fileinfo is installed! √ gd is installed! √ json is installed! √ ldap is installed! √ mbstring is installed! √ mysqli is installed! √ openssl is installed! √ PDO is installed! √ sodium is installed! √ tokenizer is installed! √ xml is installed! √ zip is installed!

STEP 3: Checking directory permissions:

√ /home/diginaga/public_html/asset/bootstrap/cache is writable √ /home/diginaga/public_html/asset/storage is writable √ /home/diginaga/public_html/asset/storage/logs is writable √ /home/diginaga/public_html/asset/storage/logs/laravel.log is writable √ /home/diginaga/public_html/asset/storage/framework is writable √ /home/diginaga/public_html/asset/storage/framework/cache is writable √ /home/diginaga/public_html/asset/storage/framework/sessions is writable √ /home/diginaga/public_html/asset/storage/framework/views is writable √ /home/diginaga/public_html/asset/storage/app is writable √ /home/diginaga/public_html/asset/storage/app/backups is writable √ /home/diginaga/public_html/asset/storage/app/backup-temp is writable √ /home/diginaga/public_html/asset/storage/private_uploads is writable √ /home/diginaga/public_html/asset/public/uploads is writable

STEP 4: Backing up database:

-- Starting backup... Dumping database diginaga_asset... Determining files to backup... Zipping 344 files and directories... Created zip containing 344 files and directories. Size is 30.55 MB Copying zip to disk named backup... Successfully copied zip to disk named backup. Backup completed!

STEP 5: Putting application into maintenance mode:

-- Application is now in maintenance mode.

STEP 6: Pulling latest from Git (master branch):

Git is installed. Already on 'master' There is no tracking information for the current branch. Please specify which branch you want to merge with. See git-pull(1) for details.

git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=<remote>/<branch> master

-- Saved working directory and index state WIP on master: 2f3b640 Initial commit -- M .htaccess M public/.htaccess

STEP 7: Cleaning up old cached files:

√ No bootstrap/cache/compiled.php, so nothing to delete. √ Deleting bootstrap/cache/services.php. It is no longer used. √ No bootstrap/cache/config.php, so nothing to delete. √ No vendor/symfony/translation/TranslatorInterface.php, so nothing to delete.

-- Configuration cache cleared! -- Application cache cleared! -- Route cache cleared! -- Compiled views cleared!

STEP 8: Updating composer dependencies: (This may take a moment.)

-- Running the app in production mode. √ Local composer.phar detected, so we'll use that.

-- Updating local composer.phar

You are already using the latest available Composer version 2.7.7 (stable channel).

Installing dependencies from lock file Verifying lock file contents can be installed on current platform. Nothing to install, update or remove Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead. Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead. Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested. Generating optimized autoload files

Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover --ansi @php artisan vendor:publish --force --tag=livewire:assets --ansi 84 packages you are using are looking for funding. Use the composer fund command to find out more! Illuminate\Foundation\ComposerScripts::postAutoloadDump @php artisan package:discover --ansi @php artisan vendor:publish --force --tag=livewire:assets --ansi Generating optimized autoload files Discovered Package: arietimmerman/laravel-scim-server Discovered Package: barryvdh/laravel-debugbar Discovered Package: barryvdh/laravel-dompdf Discovered Package: eduardokum/laravel-mail-auto-embed Discovered Package: facade/ignition Discovered Package: fideloper/proxy Discovered Package: fruitcake/laravel-cors Discovered Package: intervention/image Discovered Package: laravel/passport Discovered Package: laravel/slack-notification-channel Discovered Package: laravel/tinker Discovered Package: laravel/ui Discovered Package: laravelcollective/html Discovered Package: livewire/livewire Discovered Package: maatwebsite/excel Discovered Package: mediconesystems/livewire-datatables Discovered Package: nesbot/carbon Discovered Package: nunomaduro/collision Discovered Package: pragmarx/google2fa-laravel Discovered Package: spatie/laravel-backup Discovered Package: unicodeveloper/laravel-password Package manifest generated successfully. Copied Directory [/vendor/livewire/livewire/dist] To [/public/vendor/livewire] Publishing complete. Generated optimized autoload files containing 8568 classes

Discovered Package: arietimmerman/laravel-scim-server Discovered Package: barryvdh/laravel-debugbar Discovered Package: barryvdh/laravel-dompdf Discovered Package: eduardokum/laravel-mail-auto-embed Discovered Package: facade/ignition Discovered Package: fideloper/proxy Discovered Package: fruitcake/laravel-cors Discovered Package: intervention/image Discovered Package: laravel/passport Discovered Package: laravel/slack-notification-channel Discovered Package: laravel/tinker Discovered Package: laravel/ui Discovered Package: laravelcollective/html Discovered Package: livewire/livewire Discovered Package: maatwebsite/excel Discovered Package: mediconesystems/livewire-datatables Discovered Package: nesbot/carbon Discovered Package: nunomaduro/collision Discovered Package: pragmarx/google2fa-laravel Discovered Package: spatie/laravel-backup Discovered Package: unicodeveloper/laravel-password Package manifest generated successfully. Copied Directory [/vendor/livewire/livewire/dist] To [/public/vendor/livewire] Publishing complete.

STEP 9: Migrating database:

Nothing to migrate.

STEP 10: Checking for OAuth keys:

√ OAuth keys detected. Skipping passport install.

STEP 11: Taking application out of maintenance mode:

-- Application is now live.

---------------------- FINISHED! ----------------------- All done! Clear your browser cookies and re-login to use your upgraded Snipe-IT!

[diginaga@server asset]$

Reproduction steps

git pull 2.php upgrade.php

Expected behavior

Upgrade not Done.

Screenshots

No response

Snipe-IT Version

6.0.13

Operating System

Centos 7

Web Server

Apache

PHP Version

8.1

Operating System

ubuntu

Browser

google chrome

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

Upgrade not Done Still in 6.0.3
[diginaga@server asset]$ php -m
[PHP Modules]
bcmath
calendar
Core
ctype
curl
date
dom
enchant
exif
fileinfo
filter
ftp
gd
gettext
hash
iconv
imap
intl
json
ldap
libxml
mbstring
mongodb
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
pspell
readline
Reflection
session
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
tidy
tokenizer
xml
xmlreader
xmlrpc
xmlwriter
xsl
zip
zlib

[Zend Modules]

[diginaga@server asset]$

Additional context

No response

welcome[bot] commented 4 months ago

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

Shakura8 commented 4 months ago

Does the application works after upgrade? if not,try php artisan up If artisan have errors going live, try my thread about upgrade from 6 to 7 https://github.com/snipe/snipe-it/issues/15087

sakthimj commented 4 months ago

Application running now, but upgrade not working... still i am stuck from Snipe-IT versionv6.0.13 build

snipe commented 4 months ago

What's the output of the git pull?

sakthimj commented 4 months ago

[diginaga@server asset]$ git pull There is no tracking information for the current branch. Please specify which branch you want to merge with. See git-pull(1) for details.

git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=<remote>/<branch> master

[diginaga@server asset]$

snipe commented 4 months ago

Try git pull master

sakthimj commented 4 months ago

Same Issue ,

[diginaga@server asset]$ git pull master fatal: 'master' does not appear to be a git repository fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. [diginaga@server asset]$

sakthimj commented 3 months ago

Hi, Wating for your update

uberbrady commented 3 months ago

git remote -v will list what your 'remotes' are.

git branch -u origin/master master if your remote is named 'origin'

then maybe you can do git pull ?

sakthimj commented 3 months ago

[diginaga@server asset]$ git remote -v [diginaga@server asset]$

When i use git remote -v is result is blank

snipe / snipe-it