Closed jaredanderton closed 3 years ago
Hi @jaredanderton sorry I missed this issue initially. It's possible this has been fixed since you posted, so running swift package update
might be enough.
If the issue persists, please run your app with --log trace
and upload the full output leading up to the crash here. That will help me track it down. Thanks!
Ah I see now MySQL Version: 5.6.37
. This package requires MySQL 5.7 and up.
@tanner0101 thanks for the follow up! I totally missed that I am running 5.7 on my local, and 5.6 on my server. Nice catch, and thanks for letting me know!
Hello, I am new to Vapor and running into some odd issues when I try to select from a MySQL database. It works locally (on OSX), but it does not work when I deploy to a prod environment.
In production, my docker container is running on a host in AWS EC2, connecting to an RDS instance. My other containers (which are not vapor 4.0) on the host can connect. Also, this is not a connection issue, I have command ("moments") which can successfully insert into the database. However, it seems as soon as I select there is a problem reading bytes.
It works locally, and so I cannot replicate locally, but fails every time I try to select using code like this:
MySQL Version: 5.6.37
The app was created using
vapor-beta
, because I wanted the app dockerized.Here is the error:
Package.swift:
Package.resolved:
LogMoment (the model I'm just testing a select from):
Controller I'm using (I recognize the class is
TickerController
, not Moment controller. I had the same issue with theTickerModel
, so I wanted to test a different model):configure.swift:
I have
tlsConfiguration: .none
in there, because my of a SSL handshake error, when using.forClient()
Dockerfile:
docker-compose.yml:
Note, I have the port set to 8001, because I have multiple others containers on the host, so I am using
docker-compose.yml
to configure the port manually (which is also the reason for thenginx-proxy
I have tried to dig into why the
fatalError()
is being called, but I realized quickly this is way over my head.Nothing seems to be out of date (in terms of my Package.resolved).
Any ideas?
Any other information that I can provide?