On 2014-15-07 23:12, Felix Frank wrote:
On 07/15/2014 01:47 PM, Daniel wrote:
I am also getting this problem. Did running the puppet master
within Apache/Passenger or nginx/Passenger help at all?
I was thinking it could be to do with a non ascii character making its
way into my code somewhere a
On 07/15/2014 01:47 PM, Daniel wrote:
> I am also getting this problem. Did running the puppet master
> within Apache/Passenger or nginx/Passenger help at all?
>
> I was thinking it could be to do with a non ascii character making its
> way into my code somewhere as that seems to cause dodgy stuff
I am also getting this problem. Did running the puppet master
within Apache/Passenger or nginx/Passenger help at all?
I was thinking it could be to do with a non ascii character making its way
into my code somewhere as that seems to cause dodgy stuff but that's not
it. I've seen lots of suggest
On Tuesday, April 23, 2013 9:38:34 AM UTC-4, jcbollinger wrote:
>
>
>
> On Monday, April 22, 2013 3:03:13 PM UTC-5, Matthew Burgess wrote:
>>
>> On Mon, Apr 22, 2013 at 4:56 PM, Jeff B wrote:
>>
>>> I've been hitting this issue for a long time. well over a year and I
>>> guess it's time to star
On Monday, April 22, 2013 3:03:13 PM UTC-5, Matthew Burgess wrote:
>
> On Mon, Apr 22, 2013 at 4:56 PM, Jeff B >wrote:
>
>> I've been hitting this issue for a long time. well over a year and I
>> guess it's time to start pushing it to try to find the root cause. I've
>> seen this reported sev
Thanks for the tip this sounds quite plausible and it looks like something
I'll need sooner or later.
On Monday, April 22, 2013 4:03:13 PM UTC-4, Matthew Burgess wrote:
>
> On Mon, Apr 22, 2013 at 4:56 PM, Jeff B >wrote:
>
>> I've been hitting this issue for a long time. well over a year and I
On Mon, Apr 22, 2013 at 4:56 PM, Jeff B wrote:
> I've been hitting this issue for a long time. well over a year and I guess
> it's time to start pushing it to try to find the root cause. I've seen
> this reported several times in the past but I've never seen a resolution
> found for this exact p
I've been hitting this issue for a long time. well over a year and I guess
it's time to start pushing it to try to find the root cause. I've seen
this reported several times in the past but I've never seen a resolution
found for this exact problems. There are other root causes for pson errors
