Skip to content

Time out error when polling. #10

New issue
New issue
Open
Open
Time out error when polling.#10
@maverick-zhn

Description

@maverick-zhn
maverick-zhn
opened on Sep 8, 2021

This happens after some time in the service:

fl-sync:info Not already polling. Starting now... +1ms
  fl-sync:info handleIncomplete: CURRENTLY_POLLING: [true] +3ms
  fl-sync:info Checking OADA to determine whether to poll. +30m
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +1ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +1ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info Checking OADA to determine whether to poll. +28m
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:info handleIncomplete: CURRENTLY_POLLING: [true] +1ms
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Currently polling already. Skipping this poll loop +0ms
  fl-sync:error An error occurred while fetching lastPoll date +0ms
(node:23775) UnhandledPromiseRejectionWarning: Error: read ETIMEDOUT
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:208:20)
(node:23775) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
(node:23775) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Not already polling. Starting now... +0ms
  fl-sync:error An error occurred while fetching lastPoll date +14s
(node:23775) UnhandledPromiseRejectionWarning: Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
    at ClientHttp2Session.request (internal/http2/core.js:1600:13)
    at doFetch (/Users/maverickzhn/repos/smithfield/qlever/fl-sync/.yarn/cache/fetch-h2-npm-3.0.0-1c8fb1c120-9d3e173b9b.zip/node_modules/fetch-h2/dist/lib/fetch-http2.js:51:32)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:23775) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Not already polling. Starting now... +0ms
  fl-sync:error An error occurred while fetching lastPoll date +15s
(node:23775) UnhandledPromiseRejectionWarning: Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
    at ClientHttp2Session.request (internal/http2/core.js:1600:13)
    at doFetch (/Users/maverickzhn/repos/smithfield/qlever/fl-sync/.yarn/cache/fetch-h2-npm-3.0.0-1c8fb1c120-9d3e173b9b.zip/node_modules/fetch-h2/dist/lib/fetch-http2.js:51:32)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:23775) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Not already polling. Starting now... +0ms
  fl-sync:error An error occurred while fetching lastPoll date +15s
(node:23775) UnhandledPromiseRejectionWarning: Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
    at ClientHttp2Session.request (internal/http2/core.js:1600:13)
    at doFetch (/Users/maverickzhn/repos/smithfield/qlever/fl-sync/.yarn/cache/fetch-h2-npm-3.0.0-1c8fb1c120-9d3e173b9b.zip/node_modules/fetch-h2/dist/lib/fetch-http2.js:51:32)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:23775) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Not already polling. Starting now... +0ms
  fl-sync:error An error occurred while fetching lastPoll date +15s
(node:23775) UnhandledPromiseRejectionWarning: Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
    at ClientHttp2Session.request (internal/http2/core.js:1600:13)
    at doFetch (/Users/maverickzhn/repos/smithfield/qlever/fl-sync/.yarn/cache/fetch-h2-npm-3.0.0-1c8fb1c120-9d3e173b9b.zip/node_modules/fetch-h2/dist/lib/fetch-http2.js:51:32)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:23775) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20)
  fl-sync:info Checking OADA to determine whether to poll. +15s
  fl-sync:info Not already polling. Starting now... +0ms
  fl-sync:error An error occurred while fetching lastPoll date +15s
(node:23775) UnhandledPromiseRejectionWarning: Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed
    at ClientHttp2Session.request (internal/http2/core.js:1600:13)
    at doFetch (/Users/maverickzhn/repos/smithfield/qlever/fl-sync/.yarn/cache/fetch-h2-npm-3.0.0-1c8fb1c120-9d3e173b9b.zip/node_modules/fetch-h2/dist/lib/fetch-http2.js:51:32)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions