Re: CF Diego Apps logging on stdout

Prashant Ghorpade


Any updates? I am not getting application staging logs for CF v259 as well. Same observations for CF v255/256 and 257.


From: Prashant Ghorpade
Sent: Wednesday, April 26, 2017 3:14 PM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)>
Subject: RE: [cf-dev] Re: CF Diego Apps logging on stdout


Yes you right! I really mean to say application staging logs and following are sample output which I am not able to see for CF v255/256/257 for Diego as a default backend. It’s working for me for CF v254.

2017-04-24T13:00:31.67-0400 [STG/0] OUT Successfully created container
2017-04-24T13:00:31.67-0400 [STG/0] OUT Downloading app package...
2017-04-24T13:00:33.68-0400 [STG/0] OUT Staging...
2017-04-24T13:00:33.68-0400 [STG/0] OUT Downloaded app package (43.8M)
2017-04-24T13:00:35.32-0400 [STG/0] OUT -----> Java Buildpack Version: v3.14 (offline) |
2017-04-24T13:00:35.51-0400 [STG/0] OUT -----> Downloading Open Jdk JRE 1.8.0_121 from (found in cache)
2017-04-24T13:00:36.84-0400 [STG/0] OUT Expanding Open Jdk JRE to .java-buildpack/open_jdk_jre (1.3s)
2017-04-24T13:00:36.84-0400 [STG/0] OUT -----> Downloading Open JDK Like Memory Calculator 2.0.2_RELEASE from (found in cache)
2017-04-24T13:00:36.87-0400 [STG/0] OUT Memory Settings: -Xms1363148K -XX:MetaspaceSize=209715K -Xmx1363148K -XX:MaxMetaspaceSize=209715K -Xss699K
2017-04-24T13:00:36.87-0400 [STG/0] OUT -----> Downloading Container Certificate Trust Store 2.0.0_RELEASE from (found in cache)
2017-04-24T13:00:37.24-0400 [STG/0] OUT Adding certificates to .java-buildpack/container_certificate_trust_store/truststore.jks (0.3s)
2017-04-24T13:00:37.24-0400 [STG/0] OUT -----> Downloading Spring Auto Reconfiguration 1.10.0_RELEASE from (found in cache)
2017-04-24T13:00:48.25-0400 [STG/0] OUT Uploading droplet...
2017-04-24T13:00:48.25-0400 [STG/0] OUT Exit status 0
2017-04-24T13:00:48.25-0400 [STG/0] OUT Staging complete
2017-04-24T13:00:48.25-0400 [STG/0] OUT Uploading droplet, build artifacts cache...
2017-04-24T13:00:48.25-0400 [STG/0] OUT Uploading build artifacts cache...
2017-04-24T13:00:48.32-0400 [STG/0] OUT Uploaded build artifacts cache (109B)
2017-04-24T13:00:53.13-0400 [STG/0] OUT Uploaded droplet (89.1M)
2017-04-24T13:00:53.16-0400 [STG/0] OUT Uploading complete
2017-04-24T13:00:53.19-0400 [STG/0] OUT Destroying container
2017-04-24T13:00:53.49-0400 [CELL/0] OUT Creating container
2017-04-24T13:00:54.04-0400 [CELL/0] OUT Successfully created container
2017-04-24T13:00:54.09-0400 [STG/0] OUT Successfully destroyed container
2017-04-24T13:00:57.49-0400 [CELL/0] OUT Starting health monitoring of container

From: ronak banka [mailto:ronakbanka.cse(a)]
Sent: Wednesday, April 26, 2017 2:54 PM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)<mailto:cf-dev(a)>>
Subject: [cf-dev] Re: CF Diego Apps logging on stdout


By "application startup logs", do you mean application staging logs??

Can you paste log lines which are missing?


On Wed, Apr 26, 2017 at 14:25 Prashant Ghorpade <prashant.ghorpade(a)<mailto:prashant.ghorpade(a)>> wrote:

I have seen some changes related to “cf logs app_name” command from CF v255 onwards on Openstack using Diego as a default container. CF v254 is working for me.

I am not getting application startup logs after running “cf logs app_name” command on stdout.

I am able to see logs when I try to access the sample application from browser but I am more interested in application startup logs.

Kindly let me know in case any additional details are required for the same.


Join { to automatically receive all group messages.