I've just opened a ticket for this same issue. Seems like a bug.

On Tue, May 28, 2013 at 9:17 AM, dB. <[email protected]> wrote:
> Nope.
>
> ~/source/gravity/dblock$ cat Procfile
> ls: ls -1
>
> ~/source/gravity/dblock$ foreman start ls
> 09:16:03 ls.1     | started with pid 70436
> 09:16:04 ls.1     | Cheffile
> 09:16:04 ls.1     | Cheffile.lock
> 09:16:04 ls.1     | Gemfile
> 09:16:04 ls.1     | exited with code 0
> 09:16:04 ls.1     | Gemfile.lock
> 09:16:04 system   | sending SIGTERM to all processes
>
>
>
> On Tuesday, May 28, 2013 9:04:05 AM UTC-4, Neil Middleton wrote:
>>
>> Do you get the same locally when running under Foreman?
>>
>>
>> On Tue, May 28, 2013 at 1:54 PM, Daniel Doubrovkine <[email protected]>
>> wrote:
>>>
>>> It looks like the format of `heroku logs -p` has changed.
>>>
>>> ~/source/heroku-commander/dblock$ heroku logs -p run.4296
>>> 2013-05-28T12:48:21.372988+00:00 heroku[run.4296]: Starting process with
>>> command `(ls -1 2>&1 ; echo rc=$?)`
>>> 2013-05-28T12:48:22.188920+00:00 app[run.4296]: sequenceId="283416"]
>>> Gemfile.lock
>>> 2013-05-28T12:48:22.189065+00:00 app[run.4296]: sequenceId="283426"] tmp
>>> ...
>>> 2013-05-28T12:48:22.188920+00:00 app[run.4296]: sequenceId="283425"]
>>> script
>>> 2013-05-28T12:48:23.457796+00:00 heroku[run.4296]: Process exited with
>>> status 0
>>> 2013-05-28T12:48:23.471462+00:00 heroku[run.4296]: State changed from
>>> starting to complete
>>> 2013-05-28T12:48:31.445353+00:00 heroku[run.4296]: Error R99 (Platform
>>> error) -> Failed to launch the dyno within 10 seconds
>>> 2013-05-28T12:48:31.445517+00:00 heroku[run.4296]: Stopping process with
>>> SIGKILL
>>>
>>> This looks pretty weird, with an unbalanced ], and is certainly not
>>> what's documented in
>>> https://devcenter.heroku.com/articles/logging#log-format.
>>>
>>> Bug? By design?
>>>
>>> --
>>>
>>> dB. | Moscow - Geneva - Seattle - New York
>>> code.dblock.org - @dblockdotorg - artsy.net - github/dblock
>>>
>>> --
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku" group.
>>>
>>> To unsubscribe from this group, send email to
>>> [email protected]
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/heroku?hl=en_US?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google Groups
>>> "Heroku Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Heroku Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to