Open mueller-ma opened 5 months ago
I admit I've never seen that one before - googling did come up with this: https://stackoverflow.com/questions/63301495/pdoexception-packets-out-of-order-expected-0-received-1-packet-size-23
Stack OverflowI have a Laravel Spark project that uses Horizon to manage a job queue with Redis. Locally, (on my Homestead box, Mac OS) everything works as expected, but on our new Digital Ocean (Forge provision...
Setting max_allowed_packet to 200M didn't help. The issue still persists.
I discovered two things:
https://snipeit.mydomain/login
I get redirected to https://snipeit.mydomain/setup
. This instance is already installed, so no setup should be required.When I try to execute that select statement manually, I get the following error: Unknown column 'snipeit' in 'where clause'
.
After adding the missing quotes (select * from information_schema.tables where table_schema = 'snipeit' and TABLE_NAME = 'migrations' and table_type = 'BASE TABLE';
) I can run the command and it selects one line.
I'm having this same issue and I can't figure out how to get Snipe-It back up and running. I've tried multiple versions going back to 6.3 and I still get this same error as Mueller-ma. I even tried creating a new stack w/no data and I still get the error.
Is there any requirement for a specific version of MySQL? The docs doesn't mention one: https://snipe-it.readme.io/docs/requirements
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. 📘NOTE ON SHARED HOSTING:If you're installing Snipe-IT on shared...
This stuff all seems very database-ey to me. And, no, there's no specific mysql database version you need, just about any of them should work. If you set your .env
variables correctly as per https://snipe-it.readme.io/docs/docker - you should be in good shape.
Snipe-IT DocumentationNote very loudly that additional Docker options should be set in the env file, and they require a full container rebuild!
Debug mode
Describe the bug
When updating the Docker image from 6.3.3 to any 6.4.X version, SnipeIT only displays
500 Server Error
.When I enable debug mode, SnipeIT works and doesn't display the 500 error.
Reproduction steps
Expected behavior
SnipeIT is working after the update.
Screenshots
No response
Snipe-IT Version
6.4.2
Operating System
Docker on Debian
Web Server
from Docker image
PHP Version
from Docker image
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages