Database gets stuck in migration with seeder on production with --force in Laravel 5

Question

Database gets stuck in migration with seeder on production with --force in Laravel. Same effect I have on Laravel Homestead and EC2 AWS running Amazone linux. No messages in laravel.log.

It just never ends. If I halt it with <ctrl>+<c>, I see the table created but seeder was not run, the table is empty.

Detalis:

My migration:

public function up()
{
    Schema::create('products', function (Blueprint $table) {
        $table->increments('id');
        $table->string('name', 50);
        $table->decimal('price', 8, 2); //up to 999,999.99
    });

    Artisan::call('db:seed', ['--class' => 'ProductsSeeder']);
}

I call it like so:

$ php artisan migrate --force

my .env

#APP_ENV=local

APP_DEBUG=false

the database seeds.

class ProductsSeeder extends Seeder
{
    public function run()
    {
        DB::table('products')->insert([
            'id'                   => 1,
            'name'                 => 'super product',
            'price'                => 999.99,
        ]);
    }

Tested Laravel 5.6

Posted the seeder code, but it is sad that the comment requesting the seeder has attracted 2 vote-ups, when it has nothing to do with the seeder code. — Yevgeniy Afanasyev, May 22 '18 at 02:39
What happens when you do the `php artisan db:seed` command from terminal? Does it work as expected? You could also try running migrate with the verbose flag `php artisan migrate --force -vvv` to see if you get any error messages. — Jeemusu, May 22 '18 at 02:48
@YevgeniyAfanasyev very hard for everyone else to tell that without having the access to it — DevK, May 22 '18 at 02:53
This class is not a part of default seed, but if I do `php artisan db:seed --class=[ProductsSeeder]` - then everything goes fine. — Yevgeniy Afanasyev, May 22 '18 at 02:54
No output when using the `-vvv` verbose flag? I wonder if you also need to add the `--force` flag to the seed call in this case, as you are using it on the migration? — Jeemusu, May 22 '18 at 02:59
Using `--force` and/or `-vvv` does not seem to make a difference. My config is correct. — Derk Jan Speelman, Apr 10 '19 at 09:02

score 6 · Accepted Answer · answered May 22 '18 at 03:04

6

Try including the -vvv flag in your migration command, this will increase the verbosity of any messages, which might uncover the problem.

--verbose (-v|vv|vvv) Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

$ php artisan migrate --force

As for the problem itself, try including the --force flag in your db:seed call, as you have included it in the migration.

Artisan::call('db:seed', ['--class' => 'ProductsSeeder', '--force' => true,]);

answered May 22 '18 at 03:04

Jeemusu

10,415
3
42
64

3

`'--force' => true,` did help. Thank you. – Yevgeniy Afanasyev May 22 '18 at 03:10
`'--force' => true` does not work without call migration with --force. – Kostiantyn May 22 '20 at 00:32

score 1 · Answer 2 · answered Aug 10 '18 at 11:17

1

I had same issue running php artisan migrate and nothing happens, stays stuck. --force or verbose wouldn't help.

The problem I had is the DB_PORT in .env was not set correctly.

answered Aug 10 '18 at 11:17

antoni

5,001
1
35
44

I have the same problem, it's getting stuck even when usimg --force. I checked the port and it's pointing to the right port (3306). Any other idea? – MrCujo Aug 13 '18 at 06:18
@MrCujo I have the same issue – Derk Jan Speelman Apr 10 '19 at 09:00

Database gets stuck in migration with seeder on production with --force in Laravel 5

2 Answers2

Linked