IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

[Ronald Bergmann]

From time to time these error reports pop up:

java.io.IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1919)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1515)
	at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
	at com.google.devtools.cdbg.debuglets.java.GcpHubClient.registerDebuggee(Unknown Source)

We do not use the clouddebugger (yet) and the stack trace isn't ours. Where do these messages come from? We also didn't hit any buttons and didn't upload our code.
And is this the right place to ask this or is there a cloud debugger group? (Couldn't find one.)

[Digil(Google Cloud Platform Support)]

This doesn't sounds like an issue connected with Cloud Debugger. Because, A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request. 

A discussion about the similar topic (Server returned HTTP response code: 503 for URL) can be found here which I would strongly recommend you to refer. In my opinion, it seems like your application/code(don't exactly know what) triggering a call to that URL which ultimately end up in the 503 error. 

You might need to post this concern in Stackoverflow.com to get some additional overview on this. Since this is a general discussion group for Google Cloud Platform and/or its connected resources, troubleshooting situations like this would find a better place with Stackoverflow.com. While posting this concern in stackoverflow.com, try to include all necessary details including proper reproduction steps(if any).

I hope this helps.

[Ronald Bergmann]

Thanks for your quick response.

It's not that we get a 503 for some requests we fire but that the whole stack trace does not belong to us. We do not use the Cloud Debugger anywhere!

I see that the Cloud Debugger API is active and in the metrics section I see

google.devtools.clouddebugger.v2.Controller2.ListActiveBreakpoints     307.719     0     39,97 Sekunden     1 Minute google.devtools.clouddebugger.v2.Controller2.RegisterDebuggee     2.097     0,05 %     0,162 Sekunden     0,454 Sekunden But where does this come from? I don't remember enabling this API.
I'll try to deactivate this API now. We use the standard java11 runtime with a simple spring boot application.

[Ronald Bergmann]

When trying to disable the Cloud Debugger API I receive a warning that "cloudapis.googleapis.com" will be disabled as well. That doesn't sound right. Is the Cloud Debugger enabled by default / required for the GAE? If so, what exactly does it do and why does it throw 503s from time to time? :|

[thomasotway]

Hello Ronald, 

Do you have any deployed apps running? Cloud debugger (formerly known as stackdriver debugger) is indeed enabled by default. 

 

In cloud debugger, is a resource selected? Refer to the documentation to see what I mean. You can share screenshots (*Just redact sensitive information*) and we can take a look. I don’t think the Cloud Debugger API is the issue here, and as Digil mentioned, Cloud debugger is referring to an app resource that is in your project.

[Ronald Bergmann]

Hi Thomas,

here are some screens. The debugger is trying to refer to our internal git repo. The source-context.json (where does this come from?) also refers to our git. There ain't much more to see there, no logpoints or snapshots etc.

Best,

Ronald

[Vivak Patel]

Judging from the error, there seems to be an issue with the debugger agents registering with the Controller to identify the application being debugged, the Debuggee. From the screenshots or error itself, it’s difficult to understand why this must be happening. It could be an issue with the Java11 runtime environment interfering with the Cloud Debugger API but this is only speculation.

The “source-context.json” file gets generated from a Git repository and deployed with your application. For more information you can visit here.

Along with the previous recommendations, I would suggest either creating a Public Issue or creating a Support Case with GCP.

[Ronald Bergmann]

Thanks, opened an issue (hopefully in the correct section): 153412854

[Manpreet Sidhu (Google Cloud Support)]

Hi Ronald,

That is great. Creating the issue will allow you to get in touch with the right people in the right place. I see someone has already replied to your request.

For further reference, Google Groups are best suited for general product discussion, product information or other general queries and questions. For more detailed and reproducible issues Public Issues are ideal. If your issue is regarding anything else, please consider Stack Overflow.