cf-dev@lists.cloudfoundry.org | Reg the upgrade from cf-205 to cf-231

Home Messages Hashtags Subgroups

Date Date 1 - 15 of 15

Reg the upgrade from cf-205 to cf-231

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Amit Kumar Gupta

#4233

I'm not sure why it's taking >40 mins to compile some simple go binaries.
You may have network issues (compilation jobs taking a long time to
download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4236

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4249

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
     # external_groups: null
     # groups: null
      userids_enabled: true
      users:
      - admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
  #spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Amit Kumar Gupta

#4253

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but
I could not login to it with the credentials I have given in the
properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>

Authenticating...

Server error, status code: 400, error code: , message:

Password>

Authenticating...

Server error, status code: 400, error code: , message:

PROPERTIES::

scim:

     # external_groups: null

     # groups: null

      userids_enabled: true

      users:

      - admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

      - services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

  #spring_profiles: null

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.
You may have network issues (compilation jobs taking a long time to
download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Jayarajan Ramapurath Kozhummal (jayark) <jayark@...>

#4255

Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-


root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy# cf login
API endpoint: https://api.testinceptionjk.cisco.com<https://api.testinceptionjk.cisco.com/>

REQUEST: [2016-03-18T16:30:28Z]
GET /v2/info HTTP/1.1
Host: api.testinceptionjk.cisco.com
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 632
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997
X-Vcap-Request-Id: a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443"}

REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/1.1
Host: uaa.testinceptionjk.cisco.com
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/0.0
Host: uaa.testinceptionjk.cisco.com
Accept: application/json
Referer: http://uaa.testinceptionjk.cisco.com/login
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 487
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:35Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:35 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:42Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:42 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

Show quoted text

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
     # external_groups: null
     # groups: null
      userids_enabled: true
      users:
      - admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
  #spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Gwenn Etourneau

#4256

Hi,

What is the value of uaa.require_https in your manifest ? By default is
true, try to put to false

Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-

root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy#
cf login

API endpoint: https://api.testinceptionjk.cisco.com

REQUEST: [2016-03-18T16:30:28Z]

GET /v2/info HTTP/1.1

Host: api.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 632

Content-Type: application/json;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997

X-Vcap-Request-Id:
a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"
http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443"
}

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/0.0

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Referer: http://uaa.testinceptionjk.cisco.com/login

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 487

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b

X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"
http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"
}

Email> admin

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:35Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:35 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:42Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:42 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Thanks

Jayaraj

From: Amit Gupta <agupta(a)pivotal.io>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <
ngnanase(a)cisco.com>
Cc: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>

Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint,
but I could not login to it with the credentials I have given in the
properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>

Authenticating...

Server error, status code: 400, error code: , message:

Password>

Authenticating...

Server error, status code: 400, error code: , message:

PROPERTIES::

scim:

     # external_groups: null

     # groups: null

      userids_enabled: true

      users:

      - admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

      - services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

  #spring_profiles: null

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
<ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go
binaries.  You may have network issues (compilation jobs taking a long time
to download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4268

Thank you Gwenn and Amit
The fix works.

Regards
Nitiyasri

From: Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
Sent: Saturday, March 19, 2016 4:38 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Cc: Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is true, try to put to false


Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-


root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy# cf login
API endpoint: https://api.testinceptionjk.cisco.com<https://api.testinceptionjk.cisco.com/>

REQUEST: [2016-03-18T16:30:28Z]
GET /v2/info HTTP/1.1
Host: api.testinceptionjk.cisco.com<http://api.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 632
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997
X-Vcap-Request-Id: a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443"}

REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/0.0
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Referer: http://uaa.testinceptionjk.cisco.com/login
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 487
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:35Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:35 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:42Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:42 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
     # external_groups: null
     # groups: null
      userids_enabled: true
      users:
      - admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
  #spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Amit Kumar Gupta

#4277

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Thank you Gwenn and Amit

The fix works.

Regards

Nitiyasri

*From:* Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
*Sent:* Saturday, March 19, 2016 4:38 AM
*To:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Cc:* Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X
(ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is
true, try to put to false

Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-

root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy#
cf login

API endpoint: https://api.testinceptionjk.cisco.com

REQUEST: [2016-03-18T16:30:28Z]

GET /v2/info HTTP/1.1

Host: api.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 632

Content-Type: application/json;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997

X-Vcap-Request-Id:
a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com
","version":0,"description":"","authorization_endpoint":"
http://uaa.testinceptionjk.cisco.com","token_endpoint":"
http://uaa.testinceptionjk.cisco.com
","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"
ssh.testinceptionjk.cisco.com:2222
","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"
https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://
loggregator.testinceptionjk.cisco.com:80
","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443
"}

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/0.0

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Referer: http://uaa.testinceptionjk.cisco.com/login

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 487

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b

X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"
http://uaa.testinceptionjk.cisco.com","passwd":"
https://console.testinceptionjk.cisco.com/password_resets/new","login":"
http://login.testinceptionjk.cisco.com","register":"
https://console.testinceptionjk.cisco.com/register
"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com
","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:35Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:35 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:42Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:42 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Thanks

Jayaraj

*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Friday, March 18, 2016 at 11:37 AM
*To: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Cc: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>

*Subject: *Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,

Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but
I could not login to it with the credentials I have given in the
properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>

Authenticating...

Server error, status code: 400, error code: , message:

Password>

Authenticating...

Server error, status code: 400, error code: , message:

PROPERTIES::

scim:

     # external_groups: null

     # groups: null

      userids_enabled: true

      users:

      - admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

      - services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

  #spring_profiles: null

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.
You may have network issues (compilation jobs taking a long time to
download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4286

Hi Amit/Gwenn

We are getting the following error while doing cf push and unable to see the logs..

Warning: error tailing logs
Error dialing loggregator server: local error: record overflow.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint  is wss://loggregator.testinceptionjk.cisco.com:80).
Starting app logconsumerms in org vms / space app as admin..

I googled and  updated the loggegrator port from 80 to 4443. I observed a different error and the endpoint begins with ws:. Previously it was wss:

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint is ws://loggregator.testinceptionjk.cisco.com:4443).


Properties:

logger_endpoint:
    port: 4443

The spiff generated manifest has zero instances of loggregator. The same has been used by us.

Regards
Nithiyasri


From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Tuesday, March 22, 2016 2:16 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Cc: Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Thank you Gwenn and Amit
The fix works.

Regards
Nitiyasri

From: Gwenn Etourneau [mailto:getourneau(a)pivotal.io<mailto:getourneau(a)pivotal.io>]
Sent: Saturday, March 19, 2016 4:38 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is true, try to put to false


Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-


root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy# cf login
API endpoint: https://api.testinceptionjk.cisco.com<https://api.testinceptionjk.cisco.com/>

REQUEST: [2016-03-18T16:30:28Z]
GET /v2/info HTTP/1.1
Host: api.testinceptionjk.cisco.com<http://api.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 632
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997
X-Vcap-Request-Id: a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222<http://ssh.testinceptionjk.cisco.com:2222>","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80<http://loggregator.testinceptionjk.cisco.com:80>","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443<http://doppler.testinceptionjk.cisco.com:4443>"}

REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/0.0
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Referer: http://uaa.testinceptionjk.cisco.com/login
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 487
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com<http://login.testinceptionjk.cisco.com>","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:35Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:35 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:42Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:42 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
     # external_groups: null
     # groups: null
      userids_enabled: true
      users:
      - admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
  #spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4294

Hi

Gentle reminder.. Sorry it’s a kind of blocking issue for us.


Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Tuesday, March 22, 2016 5:29 PM
To: 'Amit Gupta' <agupta(a)pivotal.io>
Cc: Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
Subject: RE: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi Amit/Gwenn

We are getting the following error while doing cf push and unable to see the logs..

Warning: error tailing logs
Error dialing loggregator server: local error: record overflow.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint  is wss://loggregator.testinceptionjk.cisco.com:80).
Starting app logconsumerms in org vms / space app as admin..

I googled and  updated the loggegrator port from 80 to 4443. I observed a different error and the endpoint begins with ws:. Previously it was wss:

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint is ws://loggregator.testinceptionjk.cisco.com:4443).


Properties:

logger_endpoint:
    port: 4443

The spiff generated manifest has zero instances of loggregator. The same has been used by us.

Regards
Nithiyasri


From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Tuesday, March 22, 2016 2:16 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Gwenn Etourneau <getourneau(a)pivotal.io<mailto:getourneau(a)pivotal.io>>; Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Thank you Gwenn and Amit
The fix works.

Regards
Nitiyasri

From: Gwenn Etourneau [mailto:getourneau(a)pivotal.io<mailto:getourneau(a)pivotal.io>]
Sent: Saturday, March 19, 2016 4:38 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>
Cc: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>; Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is true, try to put to false


Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-


root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy# cf login
API endpoint: https://api.testinceptionjk.cisco.com<https://api.testinceptionjk.cisco.com/>

REQUEST: [2016-03-18T16:30:28Z]
GET /v2/info HTTP/1.1
Host: api.testinceptionjk.cisco.com<http://api.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 632
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997
X-Vcap-Request-Id: a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222<http://ssh.testinceptionjk.cisco.com:2222>","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80<http://loggregator.testinceptionjk.cisco.com:80>","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443<http://doppler.testinceptionjk.cisco.com:4443>"}

REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/0.0
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Referer: http://uaa.testinceptionjk.cisco.com/login
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 487
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com<http://login.testinceptionjk.cisco.com>","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:35Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:35 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:42Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:42 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
     # external_groups: null
     # groups: null
      userids_enabled: true
      users:
      - admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
      - services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
  #spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.  You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines.  You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in  rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
     Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
   Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da                              f-8dc5-b9c1924004c3' to be active (00:41:23)
   Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b' to be active (00:43:31)



   Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805                              2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri

attachment.html

Vik R <vagcom.ben@...>

#4296

Can you curl that endpoint. Have you added cert and private key for uaa?

Ben

On Tue, Mar 22, 2016 at 8:29 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi

Gentle reminder.. Sorry it’s a kind of blocking issue for us.

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Tuesday, March 22, 2016 5:29 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud
Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>;
Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi Amit/Gwenn

We are getting the following error while doing cf push and unable to see
the logs..

Warning: error tailing logs

Error dialing loggregator server: local error: record overflow.

Please ask your Cloud Foundry Operator to check the platform configuration
(loggregator endpoint  is wss://loggregator.testinceptionjk.cisco.com:80).

Starting app logconsumerms in org vms / space app as admin..

I googled and  updated the loggegrator port from 80 to 4443. I observed a
different error and the endpoint begins with ws:. Previously it was wss:

Warning: error tailing logs

Error dialing loggregator server: unexpected EOF.

Please ask your Cloud Foundry Operator to check the platform configuration
(loggregator endpoint is ws://loggregator.testinceptionjk.cisco.com:4443).

Properties:

logger_endpoint:

    port: 4443

The spiff generated manifest has zero instances of loggregator. The same
has been used by us.

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Tuesday, March 22, 2016 2:16 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud
Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>;
Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>

*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Thank you Gwenn and Amit

The fix works.

Regards

Nitiyasri

*From:* Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
*Sent:* Saturday, March 19, 2016 4:38 AM
*To:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Cc:* Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X
(ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is
true, try to put to false

Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-

root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy#
cf login

API endpoint: https://api.testinceptionjk.cisco.com

REQUEST: [2016-03-18T16:30:28Z]

GET /v2/info HTTP/1.1

Host: api.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 632

Content-Type: application/json;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997

X-Vcap-Request-Id:
a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com
","version":0,"description":"","authorization_endpoint":"
http://uaa.testinceptionjk.cisco.com","token_endpoint":"
http://uaa.testinceptionjk.cisco.com
","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"
ssh.testinceptionjk.cisco.com:2222
","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"
https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://
loggregator.testinceptionjk.cisco.com:80
","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443
"}

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/0.0

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Referer: http://uaa.testinceptionjk.cisco.com/login

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 487

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b

X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"
http://uaa.testinceptionjk.cisco.com","passwd":"
https://console.testinceptionjk.cisco.com/password_resets/new","login":"
http://login.testinceptionjk.cisco.com","register":"
https://console.testinceptionjk.cisco.com/register
"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com
","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:35Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:35 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:42Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:42 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Thanks

Jayaraj

*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Friday, March 18, 2016 at 11:37 AM
*To: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Cc: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>

*Subject: *Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,

Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint, but
I could not login to it with the credentials I have given in the
properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>

Authenticating...

Server error, status code: 400, error code: , message:

Password>

Authenticating...

Server error, status code: 400, error code: , message:

PROPERTIES::

scim:

     # external_groups: null

     # groups: null

      userids_enabled: true

      users:

      - admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

      - services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

  #spring_profiles: null

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries.
You may have network issues (compilation jobs taking a long time to
download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Amit Kumar Gupta

#4308

Just a heads up, while the community is committed to helping people use CF,
people here are essentially volunteering their time and hence cannot
respond differently to urgent or blocking issues.

Also, your new issue seems fairly different from your original issue.  I
would recommend starting a new thread with a clear title of the issue, it
will have a better chance of catching the eye of some of the logging
experts.  I would even recommend creating a GH issue at
github.com/cloudfoundry/loggregator.

Best,
Amit

Show quoted text

On Tue, Mar 22, 2016 at 9:27 PM, Ben R <vagcom.ben(a)gmail.com> wrote:

Can you curl that endpoint. Have you added cert and private key for uaa?

Ben

On Tue, Mar 22, 2016 at 8:29 PM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi

Gentle reminder.. Sorry it’s a kind of blocking issue for us.

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Tuesday, March 22, 2016 5:29 PM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud
Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>;
Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>
*Subject:* RE: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi Amit/Gwenn

We are getting the following error while doing cf push and unable to see
the logs..

Warning: error tailing logs

Error dialing loggregator server: local error: record overflow.

Please ask your Cloud Foundry Operator to check the platform
configuration (loggregator endpoint  is wss://
loggregator.testinceptionjk.cisco.com:80).

Starting app logconsumerms in org vms / space app as admin..

I googled and  updated the loggegrator port from 80 to 4443. I observed a
different error and the endpoint begins with ws:. Previously it was wss:

Warning: error tailing logs

Error dialing loggregator server: unexpected EOF.

Please ask your Cloud Foundry Operator to check the platform
configuration (loggregator endpoint is ws://
loggregator.testinceptionjk.cisco.com:4443).

Properties:

logger_endpoint:

    port: 4443

The spiff generated manifest has zero instances of loggregator. The same
has been used by us.

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Tuesday, March 22, 2016 2:16 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
<ngnanase(a)cisco.com>
*Cc:* Gwenn Etourneau <getourneau(a)pivotal.io>; Discussions about Cloud
Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>;
Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com>

*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Thank you Gwenn and Amit

The fix works.

Regards

Nitiyasri

*From:* Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
*Sent:* Saturday, March 19, 2016 4:38 AM
*To:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Cc:* Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X
(ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is
true, try to put to false

Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-

root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy#
cf login

API endpoint: https://api.testinceptionjk.cisco.com

REQUEST: [2016-03-18T16:30:28Z]

GET /v2/info HTTP/1.1

Host: api.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 632

Content-Type: application/json;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997

X-Vcap-Request-Id:
a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com
","version":0,"description":"","authorization_endpoint":"
http://uaa.testinceptionjk.cisco.com","token_endpoint":"
http://uaa.testinceptionjk.cisco.com
","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"
ssh.testinceptionjk.cisco.com:2222
","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"
https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://
loggregator.testinceptionjk.cisco.com:80
","doppler_logging_endpoint":"wss://
doppler.testinceptionjk.cisco.com:4443"}

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/0.0

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Referer: http://uaa.testinceptionjk.cisco.com/login

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 487

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b

X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"
http://uaa.testinceptionjk.cisco.com","passwd":"
https://console.testinceptionjk.cisco.com/password_resets/new","login":"
http://login.testinceptionjk.cisco.com","register":"
https://console.testinceptionjk.cisco.com/register
"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com
","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:35Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:35 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Authenticating...

REQUEST: [2016-03-18T16:30:42Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:42 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:

Password>

Thanks

Jayaraj

*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Friday, March 18, 2016 at 11:37 AM
*To: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Cc: *"Discussions about Cloud Foundry projects and the system overall."
<cf-dev(a)lists.cloudfoundry.org>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>

*Subject: *Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,

Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

Bosh deployment has completed successfully.  I could set the endpoint,
but I could not login to it with the credentials I have given in the
properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>

Authenticating...

Server error, status code: 400, error code: , message:

Password>

Authenticating...

Server error, status code: 400, error code: , message:

PROPERTIES::

scim:

     # external_groups: null

     # groups: null

      userids_enabled: true

      users:

      - admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

      - services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

  #spring_profiles: null

Regards

Nithiyasri

*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

  Started preparing dns > Binding DNS. Done (00:00:00)

Regards

Nithiyasri

*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
<ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go
binaries.  You may have network issues (compilation jobs taking a long time
to download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines.  You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
 rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..

Following is the one:

Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

     Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

   Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

   Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f                              4164b6b'
to be active (00:43:31)

   Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805                              2ebe5' to be
active (00:44:49)

Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active

Regards

Nithiyasri

attachment.html

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>

#4452

Hi Amit

I tried cf login after setting the endpoint. But it fails with the below msg.  Related property (uaa.require_https= false) Last time when I got the error, we changed this property.
But this time, instead of this setting, it fails. Cf logs below

root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes                                                                                                                             t1/cf-deploy# cf login
API endpoint: https://api.vikramdevtest1.io

Email> admin

Password>
Authenticating...
Server error, status code: 404, error code: , message:

Password> root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vi                                                                                                                             t1/cf-deploy# ls
cf-231-final-V.yml  cf-template-231.yml    service.yml
cf-settings.rb      cf-vikramdevtest1.yml
root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes                                                                                                                             t1/cf-deploy# vimdiff cf-template-231.yml cf-231-final-V.yml
2 files to edit
root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes                                                                                                                             t1/cf-deploy# CF_TRACE_true
CF_TRACE_true: command not found
root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes                                                                                                                             t1/cf-deploy# CF_TRACE=true cf login
API endpoint: https://api.vikramdevtest1.io

REQUEST: [2016-04-05T17:38:18Z]
GET /v2/info HTTP/1.1
Host: api.vikramdevtest1.io
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-04-05T17:38:18Z]
HTTP/1.1 200 OK
Content-Length: 586
Content-Type: application/json;charset=utf-8
Date: Tue, 05 Apr 2016 17:38:18 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 54184ed0-310b-4a2f-5d5f-a1c21a397d49
X-Vcap-Request-Id: 876ca517-01fd-4f73-7a85-955955f3de41::86dcd763-5                                                                                                                             f8e-42b3-b657-7af57ec9ea21

{"name":"","build":"","support":"http://support.cloudfoundry.com","                                                                                                                             version":0,"description":"","authorization_endpoint":"http://uaa.vi                                                                                                                             kramdevtest1.io","token_endpoint":"http://uaa.vikramdevtest1.io","m                                                                                                                             in_cli_version":null,"min_recommended_cli_version":null,"api_versio                                                                                                                             n":"2.51.0","app_ssh_endpoint":"ssh.vikramdevtest1.io:2222","app_ss                                                                                                                             h_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","ro                                                                                                                             uting_endpoint":"https://api.vikramdevtest1.io/routing","logging_en                                                                                                                             dpoint":"wss://loggregator.vikramdevtest1.io:4443","doppler_logging                                                                                                                             _endpoint":"wss://doppler.vikramdevtest1.io:4443"}

REQUEST: [2016-04-05T17:38:18Z]
GET /login HTTP/1.1
Host: uaa.vikramdevtest1.io
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-04-05T17:38:18Z]
HTTP/1.1 200 OK
Content-Length: 447
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Tue, 05 Apr 2016 17:38:18 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: d35da14d-3367-4032-6eef-d2050839147f
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.vikramdevtest                                                                                                                             1.io","passwd":"https://console.vikramdevtest1.io/password_resets/n                                                                                                                             ew","login":"http://login.vikramdevtest1.io","register":"https://co                                                                                                                             nsole.vikramdevtest1.io/register"},"zone_name":"uaa","entityID":"lo                                                                                                                             gin.vikramdevtest1.io","commit_id":"9b5c13d","idpDefinitions":{},"p                                                                                                                             rompts":{"username":["text","Email"],"password":["password","Passwo                                                                                                                             rd"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-04-05T17:38:29Z]
POST /oauth/token HTTP/1.1
Host: uaa.vikramdevtest1.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-04-05T17:38:29Z]
HTTP/1.1 404 Not Found
Content-Length: 65
Content-Type: text/plain; charset=utf-8
Date: Tue, 05 Apr 2016 17:38:29 GMT
X-Cf-Routererror: unknown_route
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: dab37d6c-3fea-428c-516a-ec7906ff6d16

404 Not Found: Requested route ('uaa.cisco.com') does not exist.

Server error, status code: 404, error code: , message:

Password> root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtest1/cf-deploy#

Regards
Nithiyasri

attachment.html

Amit Kumar Gupta

#4456

Sounds like a new issue.  Can you start a new mailing list thread?

Thanks,
Amit

On Tue, Apr 5, 2016 at 10:44 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit

I tried cf login after setting the endpoint. But it fails with the below
msg.  Related property (uaa.require_https= false) Last time when I got the
error, we changed this property.

But this time, instead of this setting, it fails. Cf logs below

root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes
t1/cf-deploy# cf login

API endpoint: https://api.vikramdevtest1.io

Email> admin

Password>

Authenticating...

Server error, status code: 404, error code: , message:

Password> root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vi
                                                                                              t1/cf-deploy#
ls

cf-231-final-V.yml  cf-template-231.yml    service.yml

cf-settings.rb      cf-vikramdevtest1.yml

root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes
t1/cf-deploy# vimdiff cf-template-231.yml cf-231-final-V.yml

2 files to edit

root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes
t1/cf-deploy# CF_TRACE_true

CF_TRACE_true: command not found

root(a)dev-inception-vm1:/opt/cisco/vms-installer/tenant-vikramdevtes
t1/cf-deploy# CF_TRACE=true cf login

API endpoint: https://api.vikramdevtest1.io

REQUEST: [2016-04-05T17:38:18Z]

GET /v2/info HTTP/1.1

Host: api.vikramdevtest1.io

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-04-05T17:38:18Z]

HTTP/1.1 200 OK

Content-Length: 586

Content-Type: application/json;charset=utf-8

Date: Tue, 05 Apr 2016 17:38:18 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 54184ed0-310b-4a2f-5d5f-a1c21a397d49

X-Vcap-Request-Id: 876ca517-01fd-4f73-7a85-955955f3de41::86dcd763-5
                                                                                                                       f8e-42b3-b657-7af57ec9ea21

{"name":"","build":"","support":"http://support.cloudfoundry.com","
                                                                                   version":0,"description":"","authorization_endpoint":"
http://uaa.vi
                   kramdevtest1.io","token_endpoint":"
http://uaa.vikramdevtest1.io","m
in_cli_version":null,"min_recommended_cli_version":null,"api_versio
n":"2.51.0","app_ssh_endpoint":"ssh.vikramdevtest1.io:2222","app_ss
                                                                                   h_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","ro
                   uting_endpoint":"https://api.vikramdevtest1.io/routing","logging_en
dpoint":"wss://loggregator.vikramdevtest1.io:4443","doppler_logging
_endpoint":"wss://doppler.vikramdevtest1.io:4443"}

REQUEST: [2016-04-05T17:38:18Z]

GET /login HTTP/1.1

Host: uaa.vikramdevtest1.io

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux

RESPONSE: [2016-04-05T17:38:18Z]

HTTP/1.1 200 OK

Content-Length: 447

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Tue, 05 Apr 2016 17:38:18 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: d35da14d-3367-4032-6eef-d2050839147f

X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.vikramdevtest
                                                                      1.io
","passwd":"https://console.vikramdevtest1.io/password_resets/n
      ew","login":"http://login.vikramdevtest1.io","register":"https://co
nsole.vikramdevtest1.io/register"},"zone_name":"uaa","entityID":"lo
gin.vikramdevtest1.io","commit_id":"9b5c13d","idpDefinitions":{},"p
                                                                      rompts":{"username":["text","Email"],"password":["password","Passwo
      rd"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>

Authenticating...

REQUEST: [2016-04-05T17:38:29Z]

POST /oauth/token HTTP/1.1

Host: uaa.vikramdevtest1.io

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-04-05T17:38:29Z]

HTTP/1.1 404 Not Found

Content-Length: 65

Content-Type: text/plain; charset=utf-8

Date: Tue, 05 Apr 2016 17:38:29 GMT

X-Cf-Routererror: unknown_route

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: dab37d6c-3fea-428c-516a-ec7906ff6d16

404 Not Found: Requested route ('uaa.cisco.com') does not exist.

Server error, status code: 404, error code: , message:

Password> root(a)dev-inception-vm1
:/opt/cisco/vms-installer/tenant-vikramdevtest1/cf-deploy#

Regards

Nithiyasri

attachment.html

1 - 15 of 15

Previous Topic Next Topic

Home Hashtags Subgroups Terms