Skip to content

Command node stops responding after period of time #411

@Bobo-amg

Description

@Bobo-amg

NR v4.0.5, node-red-contrib-telegrambot v16.3.2

(Perhaps related to #391 and/or #253)

After an (unknown) period of time a Command node stops responding. Has been occurring on previous versions of telegrambot also.

A command node containing a single alpha character is used periodically to initiate a Keyboard (group of nodes providing a Telegram keyboard).
When it fails there is NO keyboard output and no output of any kind to a Debug node. There is an error generated from the Config node - "Error stopping node: Close timed out"
I have an Inject node (for testing) wired to the Keyboard bypassing the above Command node. Injecting works as expected and produces a Keyboard in Telegram.

Performing a Full Deploy of NR fixes the above, until it eventually fails again.

Also, perhaps unrelated I see this in the Linux logs (assume this is just caused by a network glitch somewhere) :-
.....
7 Aug 00:56:34 - [warn] [telegram bot:17a66215.f88b7e] RequestError: Error: connect EHOSTUNREACH 10.0.0.1:443
Aug 07 00:56:34 raspberrypi Node-RED[202134]: at new RequestError (/home/main/.node-red/node_modules/request-promise-core/lib/errors.js:14:15)
Aug 07 00:56:34 raspberrypi Node-RED[202134]: ... 10 lines matching cause stack trace ...
Aug 07 00:56:34 raspberrypi Node-RED[202134]: at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
Aug 07 00:56:34 raspberrypi Node-RED[202134]: code: 'SLIGHTLYBETTEREFATAL',
Aug 07 00:56:34 raspberrypi Node-RED[202134]: cause: RequestError: Error: connect EHOSTUNREACH 10.0.0.1:443
.....

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions