ERROR: Failed to initialize config manager

253 views
Skip to first unread message

Jan Krynauw

unread,
Jul 15, 2022, 5:06:45 AM7/15/22
to Google Cloud Endpoints
Hi, 

We are setting up an ESPv2 proxy using gRPC (using descriptor.pb and api_config.yaml) deployed on Google Cloud Run

For some of our services we are getting the following errors when deploying:
fail to initialize config manager: fail to unmarshal service config ...

Screenshot 2022-07-15 at 11.01.28.png

Both service configurations have been successfully submitted and rolled out to Google Services API and are displaying in the Google Cloud Console - Endpoints UI.

I have attached the following services:
  1. service_failed.yaml - for which we received the above error when deploying to Cloud Run
  2. service_success.yaml - which successfully deployed to Cloud Run and CORS, HTTP-Transcoding etc. works as expected.
Any reason why the first server config would have failed?

service_success.yaml
service_failed.yaml

Teju Nareddy

unread,
Jul 15, 2022, 11:07:09 AM7/15/22
to Jan Krynauw, Google Cloud Endpoints
Hi Jan,


There should be an error reason at the end of the log line. Can you check and post it here?

--
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/42806b16-ea11-4f4c-b583-16c81fbf9e55n%40googlegroups.com.


--

Teju Nareddy

nare...@google.com

Software Engineer

Jan Krynauw

unread,
Jul 15, 2022, 11:39:52 AM7/15/22
to Teju Nareddy, Google Cloud Endpoints
Thanks for the quick response.

I've attached the logs for both the above.

Google Cloud Logging seems to have a limit in the size of the logs entries - so the last part of the log line did not come through in the logs - is there another way to access these logs?
Kind regards,
Jan


logs_success.json
logs_failed.json

Wayne Zhang

unread,
Jul 15, 2022, 12:12:06 PM7/15/22
to Jan Krynauw, Teju Nareddy, Google Cloud Endpoints
Here is the error:

returned error unexpected protobuf.Any with url: type.googleapis.com/google.api
.VisibilityRule,

For now,  you need to remove VisibilityRule in your config file.  We will add it in ESPv2

Thanks

-Wayne

Jan Krynauw

unread,
Jul 15, 2022, 12:34:30 PM7/15/22
to Wayne Zhang, Teju Nareddy, Google Cloud Endpoints
Thank you Wayne! This makes sense now.

You mentioned that "We will add it in ESPv2" - we are already using the ESPv2 container: gcr.io/endpoints-release/endpoints-runtime-serverless:2. Not quite sure what you mean?
Kind regards,
Jan

Wayne Zhang

unread,
Jul 15, 2022, 12:50:31 PM7/15/22
to Jan Krynauw, Teju Nareddy, Google Cloud Endpoints
It will be fixed in next ESPv2 release.   Here is the pr  https://github.com/GoogleCloudPlatform/esp-v2/pull/718

-Wayne

Jan Krynauw

unread,
Jul 15, 2022, 1:37:55 PM7/15/22
to Wayne Zhang, Teju Nareddy, Google Cloud Endpoints
Awesome, thanks! 

Just a side comment: the Service object is a well defined Google proto and it seems strange that the one needs to commit a string version of the YAML when submitting a Config in the ServiceManagement endpoint - I've added a feature request here: https://github.com/googleapis/google-api-go-client/issues/1621
Kind regards,
Jan


Reply all
Reply to author
Forward
0 new messages