Cannot access resource Logs. Cloud Logging is returning "Internal Error"

[RAMIII]

As of today, 04/30/2025 at 7:17pm, I am unable to load any logs for my Cloud Run project. Now, at 11:50pm, the problem remains, and no outages are reported for region us-east1.

When trying to access logs for a Cloud Run Function from the Cloud Console, I first get a long attempt to load the logs with a message like: "Loading... Scanned up to  5/1/2025,3:59PM", followed by, "Error: Internal error encountered".

Logs Explorer is perpetually stuck loading the logs with this message displayed, "Loading... Scanned up to 4/30/25, 10:26 PM."

Running, 'gcloud logging read' from my local device returns:

ERROR: (gcloud.logging.read) HttpError accessing <https://logging.googleapis.com/v2/entries:list?alt=json>: response: <{'vary': 'Origin, X-Origin, Referer', 'content-type': 'application/json; charset=UTF-8', 'content-encoding': 'gzip', 'date': 'Thu, 01 May 2025 02:13:40 GMT', 'server': 'ESF', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'x-content-type-options': 'nosniff', 'server-timing': 'gfet4t7; dur=9023', 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'transfer-encoding': 'chunked', 'status': 500}>, content <{
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL"
}
}
>
This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach.

Finally, the mobile app says "Something went wrong".

This is NOT a network connectivity issue. The last thing I did before noticing this issue was update and run the source code of an existing Cloud Run Function. Could I have creating a devastating bug?? Is anyone else experiencing issues with Cloud Logging?

Update: Logs Explorer is now a completely blank page.

[reinc]

Hi @RAMIII,

Welcome to Google Cloud Community! 

The error ERROR: (gcloud.logging.read) HttpError accessing https://logging.googleapis.com/v2/entries:list?alt=json indicates that the gcloud logging read command failed because it received an HTTP error while trying to access the Google Cloud Logging API endpoint. The URL the command is trying to access to retrieve the logs in JSON format.

Here are the workarounds you may try:

• Service Account - Is somehow disabled or has other IAM issues preventing it from accessing Cloud Logging. Ensure that the service account used has both the roles/logging.logWriter and roles/logging.viewer roles.
  
  
• Memory Exhaustion - Check your Cloud Run Codes for potential issues like excessive logging. Possibly the function is consuming all available memory, CPU, or network bandwidth, causing the Google Cloud Logging agent to fail. The 500 error occurs due to Container instances exceeded memory limits.

Based on your function logs it shows internal error which are:

• "code": 500 - Confirms the HTTP status code.
• "message": "Internal error encountered." - Google Cloud often returns this message even when more specific information is available internally.
• "status": "INTERNAL" - Indicates that the error occurred within the Google Cloud Logging service itself.

It is recommended to reach out to our Google Cloud Support team for help to examine logs and investigate the internal error furthermore.


Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.