Re: no more stdout in app files since upgrade to 214

Home Messages Hashtags Subgroups

James Bayer #1254 here are some things that should help us troubleshoot: does "cf logs APPNAME --recent" show anything different? how did you create your deployment manifest? how many availability zones do you have in your deployment? how many traffic controllers and doppler instances do you have? is the dea_logging_agent co-located with the DEAs and your "runner" VMs configured with jobs something like this [0]? with our installations, we typically use the affectance tests (CATS) [1] to cover platform functionality. there is also a set of acceptance tests just for loggregator [2]. [0] https://github.com/cloudfoundry/cf-release/blob/master/example_manifests/minimal-aws.yml#L229-L239 [1] https://github.com/cloudfoundry/cf-acceptance-tests [2] https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs/loggregator-acceptance-tests toggle quoted message Show quoted text On Mon, Aug 17, 2015 at 1:11 AM, ramonskie <ramon.makkelie(a)klm.com> wrote: okay so no problem there the only thing now is that there is no streaming logs with the cf logs command from my APP only RTS any ideas there? -- View this message in context: http://cf-dev.70369.x6.nabble.com/no-more-stdout-in-app-files-since-upgrade-to-214-tp1197p1217.html Sent from the CF Dev mailing list archive at Nabble.com. -- Thank you, James Bayer attachment.html attachment.html
More All Messages By This Member

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.