More CD2 errors happening lately...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Got this little ditty today:
2025-01-22 10:05:05,294 - ERROR - malformed HTTP response:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>504 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: JcMid_eNLgZT_7qI2WBseNq4zJlRhXRajHT5Rlm1AUrGwdO6FP9m2A==
Along with the "malformed HTTP response" errors, I'm receiving these on a regular basis:
- ERROR - table not initialized, use `initdb`
- ERROR: The request could not be satisfied
- ERROR - invalid_client
My target DB is a horribly over-resourced PG instance in AWS/RDS and I'm using DAP client ver. 1.3.1 on Python 3.12.5. These errors have only coming fast 'n furious in the last few weeks. Before that it's been smooth sailing. Thoughts?
