Re: Error: BAD_REQUEST: server response status code: 400

159 views
Skip to first unread message

D. T.

unread,
Apr 3, 2018, 2:18:31 PM4/3/18
to artjom...@gmail.com, Google Cloud Endpoints
Apologies for the slow response. Are you still experiencing an issue?

Daniel Tang | Software Engineer | ta...@google.com | Google Inc



On Tue, Mar 27, 2018 at 12:18 PM Artjom Zabelin <artjom...@gmail.com> wrote:
Hey guys,

I successfully deployed a service on my cluster:

Service:

# [service start]
apiVersion
: v1
kind
: Service
metadata
:
  name
: qrcode-generator
spec
:
  ports
:
 
- port: 80
    targetPort
: 8080
    protocol
: TCP
    name
: http
 
- port: 443
    protocol
: TCP
    name
: https
  selector
:
    app
: qrcode-generator
  type
: LoadBalancer
# [service end]

Deployment:

# [deployment start]
apiVersion
: extensions/v1beta1
kind
: Deployment
metadata
:
  name
: qrcode-generator
spec
:
  replicas
: 1
 
template:
    metadata
:
      labels
:
        app
: qrcode-generator
    spec
:
      volumes
:
       
- name: service-account-creds
          secret
:
            secretName
: service-account-creds
       
- name: nginx-ssl
          secret
:
            secretName
: nginx-ssl
      containers
:
       
# [endpoint start]
       
- name: qrcode-generator-endpoint
          image
: gcr.io/endpoints-release/endpoints-runtime:1
          args
: [
           
"--http_port", "8080",
           
"--ssl_port", "443",
           
"--backend", "127.0.0.1:8081",
           
"--service", "qrcode-generator.services.my-domain.de",
           
"--version", "2018-03-27r3",
           
"--service_account_key", "/etc/nginx/creds/service-account-creds.json",
         
]
          resources
:
            requests
:
              cpu
: "25m"
          ports
:
           
- containerPort: 8080
           
- containerPort: 443
          volumeMounts
:
           
- mountPath: /etc/nginx/creds
              name
: service-account-creds
              readOnly
: true
           
- mountPath: /etc/nginx/ssl
              name
: nginx-ssl
              readOnly
: true
       
# [endpoint start]
       
# [qrcode-generator microservice start]
       
- name: qrcode-generator
          image
: gcr.io/my-network/qrcode-generator:0.9.7
          env
:
           
- name: PORT
              value
: "8081"
          ports
:
         
- containerPort: 8081
       
# [qrcode-generator microservice end]
# [deployment end]

However after switching from qrcode-generator.endpoints.my-network.cloud.goog to a custom domain, I keep getting following error when I make a request:

{
   
"code": 13,
   
"message": "Request blocked due to unsupported error code: 122",
   
"details": [
       
{
           
"@type": "type.googleapis.com/google.rpc.DebugInfo",
           
"stackEntries": [],
           
"detail": "service_control"
       
}
   
]
}

The requests never reach the qrcode-generator container. And the endpoint container log shows the following:

INFO:Constructing an access token with scope https://www.googleapis.com/auth/service.management.readonly
INFO:Service account email: endp...@my-network.iam.gserviceaccount.com
INFO:Refreshing access_token
INFO:Fetching the service configuration from the service management service
nginx: [warn] Using trusted CA certificates file: /etc/nginx/trusted-ca-certificates.crt
2018/03/27 19:02:00[warn]9#9: Received non-matching report response service config ID: '', requested: '2018-03-27r3'
10.56.1.1 - - [27/Mar/2018:19:02:00 +0000] "GET /v0/qrcode HTTP/1.1" 404 200 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36"
10.56.1.1 - - [27/Mar/2018:19:02:00 +0000] "GET /favicon.ico HTTP/1.1" 404 200 "http://qrcode-generator.services.my-domain.de/v0/qrcode" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36"
2018/03/27 19:02:01[error]9#9: Failed to call https://servicecontrol.googleapis.com/v1/services/qrcode-generator.services.my-domain.de:report, Error: BAD_REQUEST: server response status code: 400, Response body:%Request contains an invalid argument.
[libprotobuf ERROR external/servicecontrol_client_git/src/service_control_client_impl.cc:182] Failed in Report call: Service control request failed with HTTP response code 400
10.56.1.1 - - [27/Mar/2018:19:02:11 +0000] "POST /v0/qrcode HTTP/1.1" 500 229 "-" "PostmanRuntime/6.4.1"
$ kubectl logs qrcode-generator-557498f4cd-kdmx4 qrcode-generator

 I spend literally the entire day to solve this.

Failed to call https://servicecontrol.googleapis.com/v1/services/qrcode-generator.services.my-domain.de:report, Error: BAD_REQUEST: server response status code: 400, Response body:%Request contains an invalid argument.

However no luck so far. Any idea what this error means?

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/e3798c05-ee8d-4d50-9583-c5a50e387999%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages