Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System Unavailable after upgrade to v4.7.5 #7242

Closed
2 tasks done
dvogelho opened this issue Jul 11, 2019 · 6 comments
Closed
2 tasks done

System Unavailable after upgrade to v4.7.5 #7242

dvogelho opened this issue Jul 11, 2019 · 6 comments
Labels

Comments

@dvogelho
Copy link

dvogelho commented Jul 11, 2019

Actual Behavior

We have upgraded our SnipeIT virtual machine to Debian 10 (buster), installed all PHP7.3 modules which are required to run SnipeIT, but after the upgrade only the System Unavailable message will be shown.

image


Please confirm you have done the following before posting your bug report:


Provide answers to these questions:

  • Is this a fresh install or an upgrade?
    Upgrade
  • Version of Snipe-IT you're running
    4.7.5
  • Version of PHP you're running
    PHP 7.3.4-2
  • Version of MySQL/MariaDB you're running
    mysql Ver 15.1 Distrib 10.3.15-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
  • What OS and web server you're running Snipe-IT on
    Debian GNU/Linux 10 (buster)
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
    Github
  • WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
    I'm only receiving the error "System Unavailable"
  • Any errors that appear in your browser's error console.
    No errors
  • Include any additional information you can find in storage/logs and your webserver's logs.

There are no errors in the apache2 error or access log

laravel.log
[2019-07-11 12:00:00] production.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Call to undefined method App\Console\Kernel::load() in /var/www/html/snipe-it/app/Console/Kernel.php:59
Stack trace:
#0 /var/www/html/snipe-it/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(117): App\Console\Kernel->commands()
#1 /var/www/html/snipe-it/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 {main}
[2019-07-11 12:00:00] production.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Call to undefined method App\Console\Kernel::load() in /var/www/html/snipe-it/app/Console/Kernel.php:59
Stack trace:
#0 /var/www/html/snipe-it/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(117): App\Console\Kernel->commands()
#1 /var/www/html/snipe-it/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 {main}

Hopefully you can help to get the system running again.

@snipe
Copy link
Owner

snipe commented Jul 16, 2019

Uh, I think you just forgot to run php artisan up to bring it back out of maintenance mode?

@michaelc64
Copy link

I'm also seeing the same issue. Running on IIS. Have upgraded using "php upgrade.php". Getting the "System Unavailable" sad panda. No other error messages logged even with debug turned on. Have just tried php artisan up, but still the same. Anywhere else to look? Thanks!

@dvogelho
Copy link
Author

dvogelho commented Jul 16, 2019

Uh, I think you just forgot to run php artisan up to bring it back out of maintenance mode?

This is the result of 'php artisan up'

In Kernel.php line 59:

Call to undefined method App\Console\Kernel::load()

image

@davidmatthews85
Copy link

I used php artisan migrate and then was complaining about various tables in the database which had to dropped one by one within mysql and once done then that sorted the issue and able to access the asset manager :)

@stale
Copy link

stale bot commented Sep 16, 2019

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

@stale stale bot added the stale label Sep 16, 2019
@stale
Copy link

stale bot commented Sep 23, 2019

This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants