stdout.log and stderr.log not show in CF197 with loggregator enabled


James Bayer
 

i believe those files were removed since loggregator gives you access to
the files (and you get get the content via syslog). you may be able to
adjust the start command to write them out again.

On Tue, May 5, 2015 at 4:31 PM, Zhang, Yuan <Yuan.Zhang(a)emc.com> wrote:

Hi,



We upgrade from CF172 to CF197 and enable loggregator on CF197. But for
application deployed to CF197 (with loggregator enabled), we DO NOT

see stdout.log and stderr.log anymore in application logs directory
anymore. We can see logs/stdout.log and logs/stderr.log in CF172.



CF197:

cf file <app> logs

Getting file contents... OK



staging_task.log 1.3K



Can you tell us what setting in CF 197 can affect stdout.log and
stderr.log show up or not? How to let logs/stdout.log and logs/stderr.log
show up?



Thanks,

Tina Zhang



_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer


Tina Zhang
 

Hi,

We upgrade from CF172 to CF197 and enable loggregator on CF197. But for application deployed to CF197 (with loggregator enabled), we DO NOT
see stdout.log and stderr.log anymore in application logs directory anymore. We can see logs/stdout.log and logs/stderr.log in CF172.

CF197:
cf file <app> logs
Getting file contents... OK

staging_task.log 1.3K

Can you tell us what setting in CF 197 can affect stdout.log and stderr.log show up or not? How to let logs/stdout.log and logs/stderr.log show up?

Thanks,
Tina Zhang