joshisa
commented
7 years ago So ... technically most of these aren't errors ... but simply output from the buildpack staging process that unfortunately are being written to stderr rather than stdout. Some buildpacks are more chatty than others. For my successful deploy (I retried in a different org+space), I see a similar volume of output and the staging process seems to continue emitting these messages. The ones to be concerned about are ones under the APP prefix. You can filter for app messages (upper right dropdown) within the Bluemix web UI log view.
API/1encountered error: Staging error: failed to stage application: another staging request was initiated One odd error in your output is the indication of multiple staging requests. Not sure why that occurred.
Could you describe "fails" a bit more? Does your app url bring up the installation page at all?
If you have the cloudfoundry CLI installed and non-Windows OS, could you run in a bash/cmd terminal:
cf logs piwikeval --recent | grep 'error\|Error'
For Windows, you'd need something like Cygwin to run grep. Or you could look through the output of the logs command manually for the "error" string.
petschni
Thanks for the update!
I tried the deployment again and it deploys but fails with the following errors in the bluemix log: (these are only the errors within the log file)