queue:listen not working

[ryanhungate]

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

[taylorotwell]

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.

[ryanhungate]

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[taylorotwell]

When's the last time you composer updated?

On Mar 14, 2013, at 6:49 PM, Ryan Hungate notifications@github.com wrote:

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[taylorotwell]

You may also try logging something like the connection name in Queue\Worker

On Mar 14, 2013, at 6:49 PM, Ryan Hungate notifications@github.com wrote:

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[ryanhungate]

if the queue:work command works fine wouldn't everything be kosher? Where would I log it, i feel like there are a lot of moving pieces in that workflow, so any help would speed things up…

Thanks for the help, hopefully I can nail this one down real quick.

On Mar 14, 2013, at 4:53 PM, Taylor Otwell wrote:

You may also try logging something like the connection name in Queue\Worker

On Mar 14, 2013, at 6:49 PM, Ryan Hungate notifications@github.com wrote:

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[ryanhungate]

sorry for the double post… so how do you recommend running this on a production server to constantly listen and respond?

On Mar 14, 2013, at 4:53 PM, Taylor Otwell wrote:

You may also try logging something like the connection name in Queue\Worker

On Mar 14, 2013, at 6:49 PM, Ryan Hungate notifications@github.com wrote:

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[taylorotwell]

We use supervisord at work to keep the queue:listen process up... Skype me (userscape.taylor)

On Mar 14, 2013, at 7:01 PM, Ryan Hungate notifications@github.com wrote:

sorry for the double post… so how do you recommend running this on a production server to constantly listen and respond?

On Mar 14, 2013, at 4:53 PM, Taylor Otwell wrote:

You may also try logging something like the connection name in Queue\Worker

On Mar 14, 2013, at 6:49 PM, Ryan Hungate notifications@github.com wrote:

no not an error, it just doesn't seem to pick up the queued item. I'll try it again but it doesn't seem to be right now.

just running:
php artisan queue:listen

I am doing a print statement right before the new Process() part to debug it, and it says :
php artisan queue:work --queue=default --delay=0 --memory=128 --sleep

Does the --sleep need to be set or something?

On Mar 14, 2013, at 4:36 PM, Taylor Otwell wrote:

Do you get an error? Also, which exact command are you running?

On Mar 14, 2013, at 6:07 PM, Ryan Hungate notifications@github.com wrote:

Is there anything that I could be missing here, where the queue:work command works fine, but the queue:listen does not pick up the queued items on demand... really frustrating. Please let me know what your doing on this. I am also using IronMQ at the moment, everything seems to work fine other than the listen part, which is really the most important.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[ryanhungate]

Hey Taylor, I am starting a process in the --env=staging environment, but the listener doesnt actually pick up the right environment. I think that it needs to be checked if any extra configs were set, to also write those out to the makeProcess() method...

[taylorotwell]

OK, will check that out.

[taylorotwell]

Just pushed a fix!

[ryanhungate]

NICE! Thanks dude... really appreciate the help.

[ryanhungate]

Hey Taylor... just so you know, I was getting an error saying that laravel was not an object jin the Console/ListenCommand construct() function...

I dont know what Im talking about, but I think it needs to be in:

    public function fire()
    {
            $this->listener->setEnvironment($this->laravel->environment());
    }

section... I changed that and it worked. Is this right?

[taylorotwell]

I made a fix for this last night I believe

On Mar 20, 2013, at 8:30 PM, Ryan Hungate notifications@github.com wrote:

Hey Taylor... just so you know, I was getting an error saying that laravel was not an object jin the Console/ListenCommand construct() function...

I dont know what Im talking about, but I think it needs to be in:

public function fire()
{
        $this->listener->setEnvironment($this->laravel->environment());
}

section... I changed that and it worked. Is this right?

—
Reply to this email directly or view it on GitHub.

[ryanhungate]

Cool... ill check and beat it up tomorrow. Thanks
On Mar 20, 2013 6:35 PM, "Taylor Otwell" notifications@github.com wrote:

I made a fix for this last night I believe

On Mar 20, 2013, at 8:30 PM, Ryan Hungate notifications@github.com
wrote:

Hey Taylor... just so you know, I was getting an error saying that
laravel was not an object jin the Console/ListenCommand construct()
function...

I dont know what Im talking about, but I think it needs to be in:

public function fire()
{
$this->listener->setEnvironment($this->laravel->environment());
}
section... I changed that and it worked. Is this right?

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/579#issuecomment-15214742
.