Problems with loggregator

[Leandro David Cacciagioni]

Hey guys I'm having troubles to retrieve my logs does this happen to you?

cf push go-sample
Updating app go-sample in org pepe / space admin as admin...
OK


Uploading go-sample...
Uploading app files from: /home/ubuntu/workspace/go-sample
Uploading 950, 2 files
Done uploading              
OK


Stopping app go-sample in org pepe / space admin as admin...
OK


Starting app go-sample in org pepe / space admin as admin...


FAILED
Server error, status code: 400, error code: 170004, message: App staging failed in the buildpack compile phase


TIP: use 'cf logs go-sample --recent' for more information
ubuntu@workstation:~/workspace/go-sample$ ls
_godir  main.go
ubuntu@workstation:~/workspace/go-sample$ cf logs go-sample --recent
Connected, dumping recent logs for app go-sample in org pepe / space admin as admin...

ubuntu@workstation:~/workspace/go-sample$

 I didn't get anything and I really don't know why, BTW the cf version is 192

[Alexander Jackson]

Hi,

   Your app might be failing to stage before it has the opportunity to write anything out.   Can you `cf logs go-sample` in another window as you do the cf push in the current one?    Do you get any output then?    We do have a few bugs in 192 that can result in failed output but if you try a few times, at least one should succeed.   The logging bugs should be fixed in the upcoming 194 release.  

     - Alex.

--
You received this message because you are subscribed to the Google Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/567a810c-1cda-42b9-91b7-4627da816132%40cloudfoundry.org.

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+u...@cloudfoundry.org.

[Leandro David Cacciagioni]

cf logs go-sample --recent
Connected, dumping recent logs for app go-sample in org pepe / space admin as admin...

I continue to have the same issue doesn't matter how much I can try, have you any working version for this because I have tried with v191 and it does the same.

Thanks,

Leandro.-

[Alexander Jackson]

Sorry I didn't understand if you tried cf logs without the --recent in another window as you where staging or not?   

    - Alex.

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/e9989bf9-08c6-4b27-9467-eac584c6a58d%40cloudfoundry.org.

[Leandro David Cacciagioni]

I just tried this like in 4 differents windows at same time and none of those work. BTW I tried with --recent and without it and that doesn't change anything. That's why I don't even have any single clue about whats happening here.-

Thanks,
Leandro.-

Cacciagioni, Leandro David
leandro...@gmail.com
System Administrator - Development Operations
lcacciagioni.github.io - about.me/cacciald
Cel: +549 341 3673294

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAN-TLMDA%2B3mynybjHH0MdvYLyzCXJtd1aERrKdXZ_tNiD10u8Q%40mail.gmail.com.

[Daniel Mikusa]

You might try checking the logs from the dea.  It might provide you with more details about what happened, for example if something failed prior to the build pack running.  Also worth checking the logs for the loggregator servers.  These would be helpful if it's an issue with logging.

Dan

--

[jo...@tuley.org]

It looks like staging is failing very early in the process — before any output would be logged. The output you pasted mentions a failure of the build pack to compile. I'd start there; once your app is progressing further through staging, and actually being deployed, you should start to see logs in loggregator.

— John Tuley

[Alexander Lomov]

Hi, Leandro.

To debug this issue you can prevent DEA remove crashed containers by changing this parameter [1] in warden config (/var/vcap/jobs/dea_next/config/warden.yml). This parameters sets time before crashed containers are removed. After that you'll be able to get access to crashed instances and figure out what is wrong. You can find details here [2].

[1] https://github.com/cloudfoundry/warden/blob/master/warden/config/linux.yml#L16

[2] https://groups.google.com/a/cloudfoundry.org/forum/#!searchin/vcap-dev/crashed$20app/vcap-dev/szqqlUbsxX4/v_cKxFm4LogJ

On Thu, Nov 27, 2014 at 4:26 AM, <jo...@tuley.org> wrote:

It looks like staging is failing very early in the process — before any output would be logged. The output you pasted mentions a failure of the build pack to compile. I'd start there; once your app is progressing further through staging, and actually being deployed, you should start to see logs in loggregator.

— John Tuley

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

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/e4039365-f7de-4e5a-8498-0c4fec537b7b%40cloudfoundry.org.

[Alexander Jackson]

CF 194 was released today and contains the stability fixes for loggregator.   We also moved to the go 1.3 runtime which should also address some lockup issues that other teams have reported with go 1.2.   Release Notes[0] for 194.

  - Alex.

[0] https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/v194

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CADrG920gHwu1DJSEpP6_5KJ03Vu4BKHOWrMKZTv8sbn6cEwKyQ%40mail.gmail.com.

[Leandro David Cacciagioni]

Thanks Guys!!! I'll be checking all this ASAP.

Cacciagioni, Leandro David
leandro...@gmail.com
System Administrator - Development Operations
lcacciagioni.github.io - about.me/cacciald
Cel: +549 341 3673294

To view this discussion on the web visit https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAN-TLMDF1ODV4NVp%2BWeyeRrhw8QHuBExdQt%2BJQyHYSzA%2BGu5xQ%40mail.gmail.com.