Date
1 - 7 of 7
Fail to stage application when scale the DEA
Layne Peng
Hi, my cf-release is v200. And I met an issue when scale out the DEA number with BOSH. When I ssh to my DEA_NEXT node, the log shows:
{"timestamp":1440419081.440199,"message":"em-http-request.errored","log_level":"error","source":"Staging","data":{"error":"Error downloading: Response status: unknown, Error: ","data":{"droplet_uri":"http://staging_upload_user:PASSWORD(a)20.0.0.5:9022/v2/buildpacks/608407a4-6c63-4bf2-a64f-02ed8d0db0ce/download"}},"thread_id":17109100,"fiber_id":26594680,"process_id":30334,"file":"/var/vcap/packages/dea_next/lib/dea/utils/download.rb","lineno":43,"method":"block in download!"} Then I tried to download it manually, get the following error: --2015-08-24 13:20:09-- http://staging_upload_user:*password*@20.0.0.5:9022/v2/buildpacks/608407a4-6c63-4bf2-a64f-02ed8d0db0ce/download Connecting to 20.0.0.5:9022... connected. HTTP request sent, awaiting response... 401 Unauthorized Unknown authentication scheme. Username/Password Authentication Failed. And I have ssh to my cloud controller to check /var/vcap/jobs/cloud_controller_ng/config/cloud_controller_ng.yml, the username and password seems to be correct: # App staging parameters staging: timeout_in_seconds: 900 minimum_staging_memory_mb: 1024 minimum_staging_disk_mb: 4096 minimum_staging_file_descriptor_limit: 16384 auth: user: staging_upload_user password: "PASSWORD" Any clue for this issue? |
|
James Bayer
layne,
toggle quoted message
Show quoted text
does this 401 issue only affect the new DEAs (previous ones work fine) or does it affect all DEAs (previously existing and the new scaled out ones)? On Mon, Aug 24, 2015 at 6:42 AM, Layne Peng <layne.peng(a)emc.com> wrote:
Hi, my cf-release is v200. And I met an issue when scale out the DEA --
Thank you, James Bayer |
|
Layne Peng
i found all new apps cannot be created now. caused by this issue. Any clue for it?
|
|
Gwenn Etourneau
Hi,
toggle quoted message
Show quoted text
You never change the password right ? it was working before ? On Tue, Aug 25, 2015 at 1:44 AM, Layne Peng <layne.peng(a)emc.com> wrote:
i found all new apps cannot be created now. caused by this issue. Any clue |
|
Layne Peng
yes, it work before.
|
|
Layne Peng
Finally, I find out the problem, but may not the one I said above. It seems a little bug exsited.
In my deployment, it will install some buildpacks by default, but perhaps caused by some network issues, the buildpack not compete. Which make the dea_next start check the SHA is not match. It continue try to download the buildpacks. I have to delete all buildpack in CF, as well as clean the folder /var/vcap/data/dea_next/tmp/* in each DEA, and restart DEA_NEXT. |
|
James Bayer
i'm glad you found it! i'll make sure that amit gupta sees this report as
toggle quoted message
Show quoted text
he is currently PM for the MEGA team that is responsible for the DEAs. thanks for sharing the results. On Mon, Aug 24, 2015 at 10:06 PM, Layne Peng <layne.peng(a)emc.com> wrote:
Finally, I find out the problem, but may not the one I said above. It --
Thank you, James Bayer |
|