Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

catch/report errors due to api service interruptions #186

Open
smnorris opened this issue Jul 6, 2024 · 7 comments
Open

catch/report errors due to api service interruptions #186

smnorris opened this issue Jul 6, 2024 · 7 comments
Milestone
1.0

Comments

@smnorris
Copy link
Owner

smnorris commented Jul 6, 2024 •
edited
Loading

See error at https://github.com/smnorris/bcfishpass/actions/runs/9815019608/job/27103503942

Same error with bcdata v0.10.2 and v0.10.4, as long as no cached response is present.

Something must have changed with the response?
@smnorris smnorris added the bug label Jul 6, 2024
@smnorris
Copy link
Owner Author

smnorris commented Jul 6, 2024

The error occurs when owslib parses the request, it isn't a bcdata function.
owslib is pinned to 0.29.*, which has been available for some time - it shouldn't be a change to that that is causing the issue?

@smnorris
Copy link
Owner Author

smnorris commented Jul 6, 2024 •
edited
Loading

looks to me like it is an error with the response, closing with hope that service is back up next week.

$ curl http://openmaps.gov.bc.ca/geo/pub/ows?service=WFS&request=Getcapabilities

 <?xml version="1.0" encoding="UTF-8"?><ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0.0" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://openmaps.gov.bc.ca/geo/schemas/ows/1.1.0/owsAll.xsd">
  <ows:Exception exceptionCode="MissingParameterValue" locator="request">
    <ows:ExceptionText>Could not determine geoserver request from http request org.geoserver.monitor.MonitorServletRequest@6cc285b6</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

@smnorris smnorris removed the bug label Jul 6, 2024
@smnorris smnorris closed this as completed Jul 6, 2024
@smnorris
Copy link
Owner Author

smnorris commented Jul 8, 2024 •
edited
Loading

Also noted here: bcgov/bcdata#339. A similar workaround should be fine for users with known datasets - listing won't work.

@smnorris smnorris reopened this Jul 8, 2024
@smnorris
Copy link
Owner Author

smnorris commented Jul 8, 2024 •
edited
Loading

No, bcdata validates against the getcapabilities response, a workaround is not really practical.

@smnorris
Copy link
Owner Author

smnorris commented Jul 8, 2024

Service is back up!

@smnorris smnorris closed this as completed Jul 8, 2024
@smnorris
Copy link
Owner Author

smnorris commented Jul 8, 2024

More informative error messages are the way to go:

  • catch the error when getCapabilities fails, add service interruption message, add test
  • look through the module to see if other api service interruptions can be caught

@smnorris smnorris reopened this Jul 8, 2024
@smnorris smnorris changed the title error parsing WFS getcapabilities request catch/report errors due to api service interruptions Jul 8, 2024
@smnorris smnorris modified the milestones: 0.11.0, 1.0 Jul 8, 2024
@smnorris
Copy link
Owner Author

Service is reported as up on the uptime page but is returning 502s fairly regularly. The retries work for the most part but I suspect depending on WFS during peak fire season is not advisable?

2024-07-22 16:30:15,821:WARNING:bcdata.wfs: HTTP error: 502
2024-07-22 16:30:15,821:WARNING:bcdata.wfs: Response headers: {'Date': 'Mon, 22 Jul 2024 23:29:43 GMT', 'Server': 'Apache', 'Content-Length': '341', 'Keep-Alive': 'timeout=5, max=100', 'Connection': 'Keep-Alive', 'Content-Type': 'text/html; charset=iso-8859-1'}
2024-07-22 16:30:15,821:WARNING:bcdata.wfs: Response text: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request<p>Reason: <strong>Error reading from remote server</strong></p></p>
</body></html>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@smnorris