Posts by: Dr. Xiujiao Gao 高秀娇

If you do not have a BOSH-Lite installed with bosh2 locally on your VirtualBox yet, you can follow Bootstrap BOSH on VirtualBox with BOSH 2.0 to do so. If you already have BOSH-Lite installed, make sure you are logged into your director as admin user. Also make sure your are using bosh cli v2. In

Do you feel a little bit disappointed when you can not simply run vagrant up to bring up a bosh-lite on your local environment anymore? Anyways I did. Not for long though. This blog will show you how to bring up a BOSH-Lite directly on your VirtualBox using bosh2 quickly. Requirements on your machine 8GB

When you see the Timed out waiting for connection to Loggregator (wss://doppler.bosh-lite.com:4443) error while pushing an App after you upgraded your CF, you may want to quickly try the following fixes. Check your cf_cli version, if it is older version, please update it the latest version (v6.25+ works for me). Log out you cf api

When MKB and I were pairing on concourse-tutorial task 12, the following error occurred when we ran the pipeline. resource script ‘/opt/resource/check []’ failed: exit status 1 stderr: failed to fetch digest: 401 Unauthorized In the tutorial, there is a bump-timestamp-file.yml which was using the following docker image resource: image_resource: type: docker-image source: { repository:

In the Cloud Foundry(CF) architecture, two of the CF components CF components have databases, one is Cloud Controller(CC), the other is OAuth2 Server (UAA). The reliability of these two databases is extremely important to the success of the CF system. PostgreSQL has become a very popular open source relational database for many enterprises. Amazon RDS

当我在AWS中的Cloud Foundry发布应用的时候，下面的Staging错误出现了。 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 such file or directory @ rb_sysopen – /tmp/warden/cgroup/cpu/instance-19qntmnpnj1/cpu.shares 我运行bosh ssh登录到其中一个Runner虚拟机，运行sudo su -以及ls /tmp/warden/cgroup来查看到底发生了什么。我发现在cgroup路径里竟然什么文件都没有！我一时不知道从哪里着手进行调试，因为我觉得问题出在Warden本身，而我对Warden内部代码并不熟悉。我在CF的slack中找到#runtime-org组进行求助，Dan Lavine和Sandy

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