Mailing List Archive

I have not used the --single option, so no input there.

I also just run scripts to clear those stalled jobs, and I wish I knew why they happened, but haven't been able to nail it down. I suspected it had to do with the target of the deployment being unresponsive(because I know sometimes it is unresponsive).

I know that wasn't really helpful, but I wanted you to know that you weren't alone in your frustration.

Adam

-----Original Message-----
From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On Behalf Of Phillip Smith
Sent: Thursday, July 17, 2014 11:06 AM
To: users@lists.bricolagecms.org
Subject: bric_queued in --single mode


Howdy,

Just wondering if anyone has used bric_queued with the --single option to run separate distribution and publish daemons? And, if so, how does that impact performance?

I'm also curious what others do when jobs are mysteriously and rather permanently stuck in the queue just "executing" (but never finishing).

I have scripts to clear those items, but I'm wondering what the conditions are for creating them in the first place?


Phillip.

Same here. Usually this happens when our internal server that is running Bricolage loses connectivity with the public internet or the target is unresponsive, or the server itself has some issue. Often, simply restarting Bricolage once the source problem has been resolved does the trick, but there are a few cases when individual jobs have to be dealt with directly.

Haven't tried the --single option.

Chris

> -----Original Message-----
> From: users@lists.bricolagecms.org
> [mailto:users@lists.bricolagecms.org] On Behalf Of Adam Wilson
> Sent: Thursday, July 17, 2014 9:46 AM
> To: users@lists.bricolagecms.org
> Subject: RE: bric_queued in --single mode
>
> I have not used the --single option, so no input there.
>
> I also just run scripts to clear those stalled jobs, and I wish I knew
> why they happened, but haven't been able to nail it down. I suspected
> it had to do with the target of the deployment being
> unresponsive(because I know sometimes it is unresponsive).
>
> I know that wasn't really helpful, but I wanted you to know that you
> weren't alone in your frustration.
>
> Adam
>
> -----Original Message-----
> From: users@lists.bricolagecms.org
> [mailto:users@lists.bricolagecms.org] On Behalf Of Phillip Smith
> Sent: Thursday, July 17, 2014 11:06 AM
> To: users@lists.bricolagecms.org
> Subject: bric_queued in --single mode
>
>
> Howdy,
>
> Just wondering if anyone has used bric_queued with the --single option
> to run separate distribution and publish daemons? And, if so, how does
> that impact performance?
>
> I'm also curious what others do when jobs are mysteriously and rather
> permanently stuck in the queue just "executing" (but never finishing).
>
> I have scripts to clear those items, but I'm wondering what the
> conditions are for creating them in the first place?
>
>
> Phillip.
>
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------

On 2014-07-17, at 12:45 PM, Adam Wilson <AWilson@RFXTechnologies.com> wrote:

> I also just run scripts to clear those stalled jobs, and I wish I knew why they happened, but haven't been able to nail it down. I suspected it had to do with the target of the deployment being unresponsive(because I know sometimes it is unresponsive).

Also, it's odd that there's no information in the job table about those jobs.

Looking at a database with more than 17M jobs, and there's not one entry in the error_message column…?


> I know that wasn't really helpful, but I wanted you to know that you weren't alone in your frustration.

Glad to know that there's some folks still alive on this list! :)

Phillip.

About to give this --single switch a try.

Will update y'all shortly. :)

Happy Friday!

Phillip.

On 2014-07-17, at 12:57 PM, Chris Schults <chris.schults@pccsea.com> wrote:

> Same here. Usually this happens when our internal server that is running Bricolage loses connectivity with the public internet or the target is unresponsive, or the server itself has some issue. Often, simply restarting Bricolage once the source problem has been resolved does the trick, but there are a few cases when individual jobs have to be dealt with directly.
>
> Haven't tried the --single option.
>
> Chris
>
>> -----Original Message-----
>> From: users@lists.bricolagecms.org
>> [mailto:users@lists.bricolagecms.org] On Behalf Of Adam Wilson
>> Sent: Thursday, July 17, 2014 9:46 AM
>> To: users@lists.bricolagecms.org
>> Subject: RE: bric_queued in --single mode
>>
>> I have not used the --single option, so no input there.
>>
>> I also just run scripts to clear those stalled jobs, and I wish I knew
>> why they happened, but haven't been able to nail it down. I suspected
>> it had to do with the target of the deployment being
>> unresponsive(because I know sometimes it is unresponsive).
>>
>> I know that wasn't really helpful, but I wanted you to know that you
>> weren't alone in your frustration.
>>
>> Adam
>>
>> -----Original Message-----
>> From: users@lists.bricolagecms.org
>> [mailto:users@lists.bricolagecms.org] On Behalf Of Phillip Smith
>> Sent: Thursday, July 17, 2014 11:06 AM
>> To: users@lists.bricolagecms.org
>> Subject: bric_queued in --single mode
>>
>>
>> Howdy,
>>
>> Just wondering if anyone has used bric_queued with the --single option
>> to run separate distribution and publish daemons? And, if so, how does
>> that impact performance?
>>
>> I'm also curious what others do when jobs are mysteriously and rather
>> permanently stuck in the queue just "executing" (but never finishing).
>>
>> I have scripts to clear those items, but I'm wondering what the
>> conditions are for creating them in the first place?
>>
>>
>> Phillip.
>>
> ---------------------------------------------------------------------------------------
> This email has been scanned for email related threats and delivered safely by Mimecast.
> For more information please visit http://www.mimecast.com
> ---------------------------------------------------------------------------------------
>

Well that was a learning experience!

The --single option means "run a single time, processing a single item in the job queue, and exit."

Phillip.

On 2014-07-25, at 8:35 AM, Phillip Smith <ps@phillipadsmith.com> wrote:

>
> About to give this --single switch a try.
>
> Will update y'all shortly. :)
>
> Happy Friday!
>
> Phillip.
>
> On 2014-07-17, at 12:57 PM, Chris Schults <chris.schults@pccsea.com> wrote:
>
>> Same here. Usually this happens when our internal server that is running Bricolage loses connectivity with the public internet or the target is unresponsive, or the server itself has some issue. Often, simply restarting Bricolage once the source problem has been resolved does the trick, but there are a few cases when individual jobs have to be dealt with directly.
>>
>> Haven't tried the --single option.
>>
>> Chris
>>
>>> -----Original Message-----
>>> From: users@lists.bricolagecms.org
>>> [mailto:users@lists.bricolagecms.org] On Behalf Of Adam Wilson
>>> Sent: Thursday, July 17, 2014 9:46 AM
>>> To: users@lists.bricolagecms.org
>>> Subject: RE: bric_queued in --single mode
>>>
>>> I have not used the --single option, so no input there.
>>>
>>> I also just run scripts to clear those stalled jobs, and I wish I knew
>>> why they happened, but haven't been able to nail it down. I suspected
>>> it had to do with the target of the deployment being
>>> unresponsive(because I know sometimes it is unresponsive).
>>>
>>> I know that wasn't really helpful, but I wanted you to know that you
>>> weren't alone in your frustration.
>>>
>>> Adam
>>>
>>> -----Original Message-----
>>> From: users@lists.bricolagecms.org
>>> [mailto:users@lists.bricolagecms.org] On Behalf Of Phillip Smith
>>> Sent: Thursday, July 17, 2014 11:06 AM
>>> To: users@lists.bricolagecms.org
>>> Subject: bric_queued in --single mode
>>>
>>>
>>> Howdy,
>>>
>>> Just wondering if anyone has used bric_queued with the --single option
>>> to run separate distribution and publish daemons? And, if so, how does
>>> that impact performance?
>>>
>>> I'm also curious what others do when jobs are mysteriously and rather
>>> permanently stuck in the queue just "executing" (but never finishing).
>>>
>>> I have scripts to clear those items, but I'm wondering what the
>>> conditions are for creating them in the first place?
>>>
>>>
>>> Phillip.
>>>
>> ---------------------------------------------------------------------------------------
>> This email has been scanned for email related threats and delivered safely by Mimecast.
>> For more information please visit http://www.mimecast.com
>> ---------------------------------------------------------------------------------------
>>
>

--
Phillip Smith
http://phillipadsmith.com