Blog

When I was pushing an app to my CF in AWS, the following staging error occurred. 2016-08-23T16:12:13.59+0000 [DEA/0] OUT Got staging request for app with id 71e82161-f1e8-408f-bd0f-fe8701284e83 2016-08-23T16:12:13.64+0000 [API/0] OUT Updated app with guid 71e82161-f1e8-408f-bd0f-fe8701284e83 ({"state"=>"STARTED"}) 2016-08-23T16:12:16.05+0000 [API/0] ERR Encountered error: Stager error: failed to stage application: 2016-08-23T16:12:16.05+0000 [API/0] ERR Failed setting cpu shares: No

当你的应用链接Cloud Foundry (CF) 的日志服务器超时，你该怎么办？ 当我往部署在AWS中的CF发布我的应用时，出现了以下错误： timeout connecting to log server, no log will be shown Starting app cf-env in org codex / space cf-app-testing as admin… FAILED Error restarting application: StagerError 为了获取更详细的错误日志，我运行了CF_TRACE=true cf push，我看到下面的信息一直停在那里，一动不动的。 WEBSOCKET REQUEST: [2016-08-17T19:45:38Z] GET /apps/e189be2e-770f-4d1c-94e2-d2168f2d292d/stream HTTP/1.1 Host: wss://doppler.system.staging.xiujiaogao.com:4443 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Version: 13 Sec-WebSocket-Key: [HIDDEN] Origin: http://localhost Authorization: [PRIVATE DATA

在我用cf push发布应用到在AWS中的 Cloud Foundry（CF）时，得到以下错误信息： Using manifest file /home/user/cf-env/manifest.yml Updating app cf-env in org codex / space cf-app-testing as admin… OK Uploading cf-env… FAILED Error processing app files: Error uploading application. Server error, status code: 500, error code: 10001, message: An unknown error occurred. 我想在日志中获得更多有效信息以帮助调试。很可惜，它除了告诉我 ”未知错误易发生（an unknown error occurred）“，什么别的信息都没有。我花了几分钟抱怨CF的日志系统不给力，速速冷静了下，来思考一下当我们发布应用的时候到底是怎么样一个过程。 错误是发生在应用上传的过程中，本来应该上传到Blobstore。我用的是Amazon的S3 bucket，于是我登陆AWS Console，发现我所需要的S3 buckets连个影儿都没有。我立刻在我部署CF的区域中创建了我需要的S3 buckets,再次运行cf push，几乎就要成功了，可是俺看到日志里有以下警告。 [2016-08-18

What can you do when your app timeout connecting to your log server in your CF deployment? The following error occurred when I pushed my app to CF in AWS. timeout connecting to log server, no log will be shown Starting app cf-env in org codex / space cf-app-testing as admin… FAILED Error restarting application:

When cf push failed to push my APP to CF in AWS, I got the following error. Using manifest file /home/user/cf-env/manifest.yml Updating app cf-env in org codex / space cf-app-testing as admin… OK Uploading cf-env… FAILED Error processing app files: Error uploading application. Server error, status code: 500, error code: 10001, message: An unknown error

Locking down your BOSH VMs? Here’s a handy guide for some options at your disposal for overriding the default password for BOSH’s vcap user: Customize it in your manifest In each resource pool (or VM type) configuration in your BOSH manifest (or cloud config manifest), you can specify env.bosh.password. This will overwrite the value of

我在AWS上部署CF的时候，在Go Router 前面设置了AWS ELB来对传入流量进行均衡。部署完毕，所有的虚拟机开始运行。可是在Amazon Console的网络界面中，EC2服务下的ELB实例却显示一个Go Router失效了（Out of Service)。 解决这个问题，我从以下三方面着手： 1）检查ELB 2）检查Go Router 3）检查ELB和Go Router之间的网络通信设置 首先curl ELB 没什么问题，并且另外一个Go Router在ELB的可用实例中正常运行，所以ELB本身应该没什么问题。 其次，我运行bosh vms查看Go Router虚拟机在正常运行，然后ssh远程登录到Go Router虚拟机，使用monit summary看到一切作业进程也都运行正常。 这些快速的调试技巧让我锁定了第三种可能。我看到ELB在Availability Zones中没有设置失效Go Router所在的子网，而为了使ELB能够路由流量到某个特定的子网或者Availability Zone，我们必须在ELB的实例中的Availability Zones进行设置添加那个子网。 接下来的工作很简单，登录AWS Console，去AWS的页面左上角点击Services会看到下拉菜单，选择EC2，进入了EC2管理页面后，点击Load Balancers选项，选择要设置的ELB，点击Instances一项就可以看到Edit Availability Zones，点击添加失效Go Router所在的子网段，点击保存。失效的Go Router开始作为ELB的实例运行了！ To read the English version, please click：Handling GoRouter Is "Out of Service" for AWS ELB.

When I deployed CF in AWS, I put an ELB in front of my two Go Routers to balance the incoming traffic. After the CF deployment completes all the VMs are running. However, one of the Go Router is showed as out of service in the Instances tab in the ELB dashboard. To debug this

You know when Spock does that thing on Star Trek and he just grabs the guy by the neck in the right place and blamo, he’s out cold? It’s called the Vulcan Nerve Pinch. The right move at the right time is all it takes to go from chaos to calm. Well we want to