Laravel 5.4 - Issue with Jobs after move model

Question

I have this error on my console. I use Jobs from Laravel 5.4 and I have move the Feed Model in App\Models\Feed. Since two days, I have this error because Laravel doesn't find the Feed Model. I have restart my Jobs with php artisan queue:restart.

[2017-07-13 10:45:33] staging.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Class 'App\Feed' not found in /home/site_com/http/www/vendor/laravel/framework/src/Illuminate/Queue/SerializesAndRestoresModelIdentifiers.php:45

<?php

namespace App\Jobs;

use App\Models\Feed;
use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;

class FetchFeeds implements ShouldQueue {
    protected $feed;
    public function __construct(Feed $feed)
    {
        $this->feed = $feed;
    }
}

My Feed model:

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Jenssegers\Mongodb\Eloquent\HybridRelations;

class Feed extends Model
{
    use HybridRelations;

    protected $connection = 'mysql';

    protected $fillable = [
        //
    ];

    protected $dates = [
        'created_at',
        'updated_at'
    ];

    ...
}

So you have a `Feed` folder under `Models`? Please post the model as well — ka_lin, Jul 13 '17 at 09:12
You likely have old jobs in the queue. Passing Eloquent models to a job gets them serialized, but because you changed the namespace of the model it can't find them anymore. Clear out the queue, or put the model back temporarily to run them. — ceejayoz, Jul 13 '17 at 18:59
I dispatch job in a cron task : https://pastebin.com/r8AjTvY9 — pirmax, Jul 13 '17 at 19:39

score 1 · Accepted Answer · answered Jul 14 '17 at 10:38

1

I've changed the Job name, it works.

answered Jul 14 '17 at 10:38

pirmax

2,054
8
36
69

dparoli · Answer 2 · 2017-07-13T09:40:57.507

0

php artisan queue:restart relies on on the cache system to schedule the restart.

If you are using APCu there is a chance that the cache it is not working with cli jobs. In this case the recommendation is to add apc.enable_cli=1 to your APCu configuration

In any case I will try to do a complete stop/start of the queue listener/worker.

edited Jul 13 '17 at 09:40

answered Jul 13 '17 at 09:30

dparoli

8,891
1
30
38

I have already restart the Job with php artisan queue:restart and flush Redis database. It's a new dispatched job... – pirmax Jul 13 '17 at 15:25
1

instead of a queue:restart please try a complete stop and start of the queue worker/listener like I suggest you – dparoli Jul 13 '17 at 20:09
How I can do this? – pirmax Jul 13 '17 at 20:24

Laravel 5.4 - Issue with Jobs after move model

2 Answers2