 |
Webh |
at Jan 9, 2013 at 2:59 pm
|
⇧ | 
| |
I have the same problem. There is no stager log, as you posted in another
thread, I checked cloud_controller.log, nothing fishy there.
What we should look for in the "stager.log"? Any configuration to check?
(used chef for installation, all seem working fine, all nodes running,
services can be created, apps can be listed, just we failed at staging the
app...)
Steve
On Wednesday, September 19, 2012 4:39:33 AM UTC-4, Ben Langfeld wrote:Check the stager log.
Regards,
Ben Langfeld
On 19 September 2012 02:59, <[email protected] <javascript:>> wrote:No, I didn't find any thing from cloud controller log.
I doubt that may communication between cloud_controller and dea have some
problems.
Because, there's no information in dea.log when I push a app.
But with the command netstat -an|grep :4222, a established
connection cloud_controller and dea could be found
在 2012年9月17日星期一UTC+8下午2时17分04秒，（未知）写道：
Hi all:
I want push a simple sinatra app to my cloud foundry.
But it give me error message like below:
[email protected]:~/temp# vmc push
Would you like to deploy from the current directory? [Yn]:y
Pushing application 'hello123'...
Creating Application: OK
Uploading Application:
Checking for available resources: OK
Packing application: OK
Uploading (1K): OK
Push Status: OK
Staging Application 'hello123': ..............................**.Error
(JSON 504): <html>
<head><title>504 Gatewa...
I see the nginx_cc_error.log
It said:
2012/09/17 13:59:17 [error] 27010#0: *1159 upstream timed out
(110: Connection timed out) while reading response header from upstream,
client: 192.168.161.63, server: _, request: "PUT /apps/hello123 HTTP/1.0",
upstream: "http://unix:/tmp/cloud_**controller.sock:/apps/**hello123",
host: "api.vcap.me"
