Illuminate\Database\QueryException #25

justoX · 2018-04-24T21:01:58Z

When I run $ docker-compose run --rm blog-server php artisan migrate , the first step of the 'Before Starting' section I get the following error message:
Illuminate\Database\QueryException : SQLSTATE[HY000] [2002] No such file or directory (SQL: select * from information_schema.tables where table_schema = laravel-blog and table_name = migrations) at /application/vendor/laravel/framework/src/Illuminate/Database/Connection.php: 664

I'm using Valet.

The text was updated successfully, but these errors were encountered:

guillaumebriday · 2018-04-24T21:28:16Z

Hey ! Did you follow steps in the Installation section before ?

Especially this one cp .env.example .env ?

justoX · 2018-04-24T21:29:14Z

Yes I did.

…

On Wed, 25 Apr 2018 at 00:28, Guillaume Briday ***@***.***> wrote: Hey ! Did you follow steps in the Installation section before ? Especially this one cp .env.example .env ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMtnX71CCuM8EQH-gP4If1fu5DH9N0Wqks5tr5jxgaJpZM4TiaWM> .

justoX · 2018-04-24T21:33:49Z

guillaumebriday · 2018-04-24T21:35:42Z

Ok, I've just tried and I have the same error. I think it's because mysql is not ready to handle connection. I've retried the command 3 times and it worked.

I will check how to fix this, thanks !

justoX · 2018-04-24T21:37:08Z

Ok, let me try again. I also ran multiple times to no success. Thank you.

guillaumebriday · 2018-04-24T21:49:05Z

More infos here https://docs.docker.com/compose/startup-order/ and here https://docs.docker.com/samples/library/mysql/ (at the end)

guillaumebriday · 2018-04-24T21:56:14Z

I don't like the workarounds that much but PR are welcome.

To use it until the fix, just run docker-compose up -d before the migration

justoX · 2018-04-24T21:56:38Z

Cool, I'll check it out.

…

On Wed, 25 Apr 2018 at 00:49, Guillaume Briday ***@***.***> wrote: More infos here https://docs.docker.com/compose/startup-order/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMtnXzfuiqIPtiNosGBDfltonFyiZiR8ks5tr53RgaJpZM4TiaWM> .

justoX · 2018-04-24T21:57:18Z

Ok, much appreciated.

…

On Wed, 25 Apr 2018 at 00:56, Guillaume Briday ***@***.***> wrote: I don't like the workarounds that much but PR are welcome. To use it until the fix, just run docker-compose up -d before the migration — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMtnX_QYhTCRd0tYw0A4lPramaLDsZKaks5tr59-gaJpZM4TiaWM> .

justoX · 2018-04-24T22:16:28Z

Result of running docker-compose up -d

mysql is definitely the culprit.

tompenzer · 2018-05-11T01:14:45Z

I don't think people can make branches or pull requests for this project, but I was able to get a fresh clone of master to work after changing the docker-compose.yml file to set mysql and mysql-test containers to specify the mysql:5.7 image rather than just mysql (I was having authentication issues with mysql 8.x that was getting pulled via mysql:latest), which I now see was fixed shortly after a cloned the repo a few days ago. I also noticed missing string enclosure single quotes for the port number on the echo-server container config [1], but don't know if that had any effect on getting it running properly.

One thing I'll note is I had to delete the (gitignored) contents of /storage/tmp/ in order for the mysql downgrade to work properly, in case you cloned and built the project before pulling the latest version of master. Also, the first attempt at migration/seeding got a PDO error, but a second attempt shortly after worked for me.

[1] https://github.com/guillaumebriday/laravel-blog/blob/master/docker-compose.yml#L59

guillaumebriday · 2018-05-11T12:48:09Z

Hey ! Yep I had the issue with the latest version of the mysql image and i had to remove /storage/tmp.

The support of mysql 8 is effective since this commit laravel/framework#23948 available in the 5.6.18. I need to upgrade the laravel version and try to upgrade the mysql too to check if it does not break anything.

And yes the single quotes change nothing in the docker-compose.yml but I will add for consistency, thanks !

guillaumebriday · 2018-05-11T12:56:01Z

The documentation as a note about string interpolation for ports https://docs.docker.com/compose/compose-file/#ports

Note: When mapping ports in the HOST:CONTAINER format, you may experience erroneous results when using a container port lower than 60, because YAML parses numbers in the format xx:yy as a base-60 value. For this reason, we recommend always explicitly specifying your port mappings as strings.

Even if I don't use port lower than 60 I will follow the documentation with double quotes everywhere

Commit : 73be5b8

prashantidealittechno · 2018-05-15T09:36:24Z

Please try to ssh into docker and then run command composer dump

    $ composer dump

and clear config with below command

    $ php artisan config:clear

and then check again it should work.

guillaumebriday · 2018-05-15T12:10:10Z

I don't think it will fix the issue because by running this command you let mysql started, which is the problem here. The migration command run before mysql is ready :/

tompenzer · 2018-05-15T16:54:25Z

Yeah, doing the front-end build before the migration/seeds seems to have resolved it for me. Alternatively, connecting to the mysql server on 0.0.0.0:3306 with the root/secret account creds in any SQL client will allow migrations to proceed as expected.

guillaumebriday · 2018-07-10T08:54:47Z

I'll try to implement wait-for-it.sh as soon as possible because it causes issues in production which is far more annoying than in development environnement

AldoRG · 2018-08-27T01:49:50Z

In the .env.example
DB_HOST=mysql
I just replaced that with my local and I added the port like this

DB_HOST=127.0.0.1
DB_PORT=3306

and it works perfectly.

guillaumebriday · 2018-08-27T07:49:01Z

Hum @AldoRG, how did you try ? Did you stop you containers before updating the DB_HOST ? Thanks

guillaumebriday · 2018-08-27T10:25:28Z

I will try today 👍

guillaumebriday · 2018-08-27T10:59:32Z

it does not work @AldoRG

ooking · 2018-10-31T08:48:20Z

When I run $ docker-compose run --rm blog-server php artisan migrate , the first step of the 'Before Starting' section I get the following error message:
Illuminate\Database\QueryException : SQLSTATE[HY000] [2002] No such file or directory (SQL: select * from information_schema.tables where table_schema = laravel-blog and table_name = migrations) at /application/vendor/laravel/framework/src/Illuminate/Database/Connection.php: 664

I'm using Valet.

find mysql.sock path and editing php.ini
pdo_mysql.default_socket=
change to
pdo_mysql.default_socket=/private/tmp/mysql.sock
or
editing database.php
'unix_socket' => '/private/tmp/mysql.sock'

good luck

hadiset · 2019-10-04T09:59:03Z

I have same problem like this, I am using docker and laradock, this is my solution,
(Be sure to set DB_HOST to mysql in .env)

Start docker
docker-compose up -d nginx mysql phpmyadmin workspace redis
Then check container id of workspace
docker container ls
After that command you'll see result then copy container_id of workspace
Then hit this command
docker exec -it <workspace container_id> bash
example docker exec -it d5cb46ad1f69 bash
If success, you'll see your terminal move to like root@d5cb46ad1f69:/var/www#
Then go to your laravel project and try to php artisan migrate or other command

Hope this can help!! Thanks!!

guillaumebriday added the Need answer label Apr 24, 2018

guillaumebriday self-assigned this Apr 24, 2018

guillaumebriday added bug and removed Need answer labels Apr 24, 2018

guillaumebriday added the enhancement label Apr 30, 2018

guillaumebriday mentioned this issue May 21, 2018

PHPUnit Testing Fail? #32

Closed

guillaumebriday mentioned this issue Jan 19, 2019

docker-compose run --rm blog-server php artisan migrate --seed not working #54

Closed

joaopmmartins mentioned this issue Sep 23, 2019

saving a comment triggers error in laravel.log #94

Closed

guillaumebriday removed the enhancement label Sep 23, 2019

guillaumebriday closed this as completed Jan 3, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Illuminate\Database\QueryException #25

Illuminate\Database\QueryException #25

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018 •

edited

Loading

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018

tompenzer commented May 11, 2018 •

edited

Loading

guillaumebriday commented May 11, 2018

guillaumebriday commented May 11, 2018 •

edited

Loading

prashantidealittechno commented May 15, 2018

guillaumebriday commented May 15, 2018 •

edited

Loading

tompenzer commented May 15, 2018 •

edited

Loading

guillaumebriday commented Jul 10, 2018

AldoRG commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

ooking commented Oct 31, 2018

hadiset commented Oct 4, 2019 •

edited

Loading

Illuminate\Database\QueryException #25

Illuminate\Database\QueryException #25

Comments

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018

guillaumebriday commented Apr 24, 2018 • edited Loading

guillaumebriday commented Apr 24, 2018

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018 via email

justoX commented Apr 24, 2018

tompenzer commented May 11, 2018 • edited Loading

guillaumebriday commented May 11, 2018

guillaumebriday commented May 11, 2018 • edited Loading

prashantidealittechno commented May 15, 2018

guillaumebriday commented May 15, 2018 • edited Loading

tompenzer commented May 15, 2018 • edited Loading

guillaumebriday commented Jul 10, 2018

AldoRG commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

guillaumebriday commented Aug 27, 2018

ooking commented Oct 31, 2018

hadiset commented Oct 4, 2019 • edited Loading

guillaumebriday commented Apr 24, 2018 •

edited

Loading

tompenzer commented May 11, 2018 •

edited

Loading

guillaumebriday commented May 11, 2018 •

edited

Loading

guillaumebriday commented May 15, 2018 •

edited

Loading

tompenzer commented May 15, 2018 •

edited

Loading

hadiset commented Oct 4, 2019 •

edited

Loading