dmikusa
commented
10 years ago Some notes here:
1.) The change that have been to the build pack in Jan are minimal. Most of them are simply package upgrades. Beyond that there was one HTTPD configuration change (shouldn't cause a staging problem), one change that was reverted and some logging that I added. You can see the logging is working on this line.
Started: [2014-01-25 01:12:51.242728]2.) What I'd suggest here is to run "cf events" (or gcf events, if you're using the go cf client). That should give you a confirmation that the staging script failed and with what error code (probably -1). If that's the case then you know that the script compile exited early for some reason, which seems to be the case because there should be a line "Finished: ..." showing when the compile script completed that is not listed in your output.
3.) From looking at the output above, I'd guess it might have something to do with this download.
Downloading [http://test.repo.standingcloud.net/repo/apps/cloudfoundry/cf-php-apache-buildpack/php/5.4/php-5.4.24-bin.tar.gz]The output shows that it started downloading, but never shows the corresponding "Downloaded ..." message. The package in question PHP 5.4.24 was one of the upgrades made in Jan.
Hope that helps!
Dan
nshenry03
Hello, I'm not sure if this is a problem with the buildpack, cloud foundry, or something on our end; however, we haven't changed anything recently and it looks like there were some changes committed recently to this buildpack so I thought I would start here (I apologize in advance if I'm in the wrong spot :-) )
Here is the error that we are getting when we try to push a new app to cloud foundry: