Date
1 - 5 of 5
stdout.log and stderr.log not show in CF197 with loggregator enabled
|
Shruthi Ravindra
Hi ,
We are having the same problem where we are not able to see the stdout.log and stderror.log for all the application deployed in the cloud. Could you please let me know how do we access the logs other than cf logs "appname" command which is not giving us the full logs. Thanks, Shruthi |
|
|
|
Shruthi Ravindra
Hi,
we are also facing the same issue when we check the "cf files pfh-cos-dicomobjectstore-dev /logs" we are able to see only the staging logs and not the stdout.log abd stderror.log. we need to access these logs to debug the error. how do we enable the stdout and stderror logs |
|
|
|
Daniel Mikusa
Have you tried running `cf logs` instead? Anything written to STDOUT or
STDERR should be visible there for some period of time. For long term storage, you should look at setting up a log drain on your application. http://docs.cloudfoundry.org/devguide/services/log-management.html Dan On Wed, Sep 2, 2015 at 9:08 AM, Shruthi Ravindra <Shruthi.ravindra(a)ge.com> wrote: Hi, |
|
|
|
Erik Jasiak
Dan is correct - "cf file" for getting stdout/stderr files directly was
toggle quoted message
Show quoted text
deprecated some time ago. I'll try to locate when that happened (it was before my time.) From the cli, "cf logs" for streaming, and "cf logs --recent" for a quick dump are the way to go. Erik PM - loggregator Daniel Mikusa wrote:
|
|
|
|
ramonskie
the only option here is to route the log output to something like graylog or logstash
toggle quoted message
Show quoted text
and to my knowledge what i understood from release 215 you can set a longer retention log for the --recent log options but i'm not sure -----Original Message-----
From: "Ravindra, Shruthi (GE Healthcare)" <Shruthi.Ravindra(a)ge.com<mailto:%22Ravindra,%20Shruthi%20%28GE%20Healthcare%29%22%20%3cShruthi.Ravindra(a)ge.com%3e>> Reply-to: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org> To: cf-dev(a)lists.cloudfoundry.org <cf-dev(a)lists.cloudfoundry.org<mailto:%22cf-dev(a)lists.cloudfoundry.org%22%20%3ccf-dev(a)lists.cloudfoundry.org%3e>> Subject: [cf-dev] Re: stdout.log and stderr.log not show in CF197 with loggregator enabled Date: Wed, 2 Sep 2015 13:04:18 +0000 Hi , We are having the same problem where we are not able to see the stdout.log and stderror.log for all the application deployed in the cloud. Could you please let me know how do we access the logs other than cf logs “appname” command which is not giving us the full logs. Thanks, Shruthi ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** |
|
|