snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
11.12k stars 3.19k forks source link

Unable to run 'php artisan migrate' #9901

Open stephenregisterTJT opened 3 years ago

stephenregisterTJT commented 3 years ago

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

Describe the bug A clear and concise description of what the bug is. I am going down an upgrade track. We had stayed on 4.6.5 for a long time and began suffering from problems when searching - for example a search result would return an empty page when there should have been several matches.

I upgraded from 4.6.5 tp 4.6.10 last week and that immediately resolved the problem. With no additional changes, we have now begun to see an "oops, something went wrong" error when trying to list any assets.

Naturally, I decided to try another upgrade. Now from 4.6.10 to latest.

In this process, I am stuck at the 'php artisan migrate' step. Screenshot below depicts error message.

"Illuminate\Database\QueryException : 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')"

I have attempted to follow the steps written here: https://snipe-it.readme.io/docs/installation-issues#during-database-migrations-max-key-length-is-1000-bytes

The change to Innodb went through without issue but did not change the error.

To Reproduce Upgrade from 4.6.5 to 4..6.10, then wait four days. Upgrade from 4.6.10 to latest, and try running 'php artisan migrate'.

Expected behavior I expected artisan to migrate without issue.

Screenshots If applicable, add screenshots to help explain your problem. https://imgur.com/t8nIpL1

Server (please complete the following information):

welcome[bot] commented 3 years 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.