-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
v2.0-95 checkin an item Server Error: 500 (Internal Server Error) #1174
Comments
Did you run migrations when you upgraded? That error doesn't look like a useful one... When you're tailing that log, can you hit enter a bunch of times to clear the older stuff offscreen, try to checkout again, and then tell me what new message shows up? |
Thank you for your super fast response. I did run migrations when I upgraded it. Everything works fine except when I check in an item cat app/storage/logs/log-cli-2015-09-15.txt Next exception 'Illuminate\Database\QueryException' with message 'SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'thread_id' (SQL: alter table |
That looks like something that would come from a migration, not from a checkout/checkin. Checkout and checkin doesn't try to create columns. Is this what you're seeing during the migration? |
yes. it's something I saw during the migration |
Okay, if a migration ever fails, you should post an issue about it. They should never, ever fail, and if they do, other stuff will break, since the migration is what adds database tables, columns, etc, which the code is expecting to be able to use. Can you show me the contents of your migrations table? |
Here it is |
Another question - do you have any file uploads in your asset log? |
I do |
Okay - I suspect that may be the issue behind the bug. In your 2015_07_29_230054_add_thread_id_to_asset_logs_table with |
Do you really wish to run this command? yes |
Can you tell me if you still see the same issue on checkin now? |
Nope. It works. Thank you very much for your help ;) |
Okay, so somehow that migration got donked up. It's been difficult to reproduce in the past, only affecting some users but not others, and I think the uploads bit is the key. We'll push out a fix for the migration shortly. Thanks for your patience, and for the debugging info. |
Super. Thanks for your awesome app |
When I check in a item, it throws this message Server Error: 500 (Internal Server Error). This issue happened after I upgraded it a few days ago
tail -f app/storage/logs/log-apache2handler-2015-09-15.txt
#17 /opt/snipe-it/bootstrap/compiled.php(715): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#18 /opt/snipe-it/bootstrap/compiled.php(696): Illuminate\Foundation\Application->dispatch(Object(Illuminate\Http\Request))
#19 /opt/snipe-it/vendor/barryvdh/laravel-debugbar/src/Middleware/Stack.php(34): Illuminate\Foundation\Application->handle(Object(Illuminate\Http\Request), 1, true)
#20 /opt/snipe-it/bootstrap/compiled.php(7825): Barryvdh\Debugbar\Middleware\Stack->handle(Object(Illuminate\Http\Request), 1, true)
#21 /opt/snipe-it/bootstrap/compiled.php(8432): Illuminate\Session\Middleware->handle(Object(Illuminate\Http\Request), 1, true)
#22 /opt/snipe-it/bootstrap/compiled.php(8379): Illuminate\Cookie\Queue->handle(Object(Illuminate\Http\Request), 1, true)
#23 /opt/snipe-it/bootstrap/compiled.php(11079): Illuminate\Cookie\Guard->handle(Object(Illuminate\Http\Request), 1, true)
#24 /opt/snipe-it/bootstrap/compiled.php(657): Stack\StackedHttpKernel->handle(Object(Illuminate\Http\Request))
#25 /opt/snipe-it/public/index.php(49): Illuminate\Foundation\Application->run()
#26 {main} [] []
The text was updated successfully, but these errors were encountered: