Databricks Community

brickster_2018 · ‎06-25-2021

My jobs that are running for more than 48 hours are failing with HTTP 403 error

brickster_2018 · ‎06-25-2021

obs service does not support runs above 48 hours. The failure is caused by API token timing out. The token is used by the jobs service to communicate with external services. Based on the type of your workspace it might be possible to configure the timeout value.

Sample error message for this error is as below:

20/01/19 22:33:42 ERROR RawDBHttpClient: Failed to deserialize exception
shaded.v245.com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 403 Invalid access token.</title>
</head>
<body><h2>HTTP ERROR 403</h2>
<p>Problem accessing /api/2.0/jobs/create. Reason:
<pre>    Invalid access token.</pre></p>
</body>
</html>
; line: 1, column: 2]
at shaded.v245.com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1419)
at shaded.v245.com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:508)
at shaded.v245.com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:437)
at shaded.v245.com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1462)
at shaded.v245.com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:683)
...

View solution in original post

brickster_2018 · ‎06-25-2021

obs service does not support runs above 48 hours. The failure is caused by API token timing out. The token is used by the jobs service to communicate with external services. Based on the type of your workspace it might be possible to configure the timeout value.

Sample error message for this error is as below:

20/01/19 22:33:42 ERROR RawDBHttpClient: Failed to deserialize exception
shaded.v245.com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 403 Invalid access token.</title>
</head>
<body><h2>HTTP ERROR 403</h2>
<p>Problem accessing /api/2.0/jobs/create. Reason:
<pre>    Invalid access token.</pre></p>
</body>
</html>
; line: 1, column: 2]
at shaded.v245.com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1419)
at shaded.v245.com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:508)
at shaded.v245.com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:437)
at shaded.v245.com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1462)
at shaded.v245.com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:683)
...

willjoe · ‎07-12-2022

Check for URL errors and make sure you're specifying an actual web page file name and extension, not just a directory. Most websites are configured to disallow directory browsing, so a 403 Forbidden message when trying to display a folder instead of a specific page, is normal and expected.

If you operate the website in question, and you want to prevent 403 errors in these cases, enable directory browsing in your web server software.

Clear your browser's cache. Issues with a cached version of the page you're viewing could be causing 403 Forbidden issues.

Log in to the website, assuming it's possible and appropriate to do so. The error message could mean that you need additional access before you can view the page.

Typically, a website produces a 401 Unauthorized error when special permission is required, but sometimes a 403 Forbidden is used instead.

Regards,

Will