CO11: Could not add to delay handler

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
fodome
New user
Posts: 7
Joined: 16 Feb 2022, 00:43

CO11: Could not add to delay handler

#1 Post by fodome » 16 Feb 2022, 00:57

Good day,

I am currently trying to configure ESPEasy to write to InfluxDB via the "Generic HTTP Advanced [Testing]" controller.

I tried this initially using CURL and got it to POST to InfluxDB successfully.
I have copied all the parameters that I used with CURL into the "Generic HTTP Advanced [Testing]" controller and after I click "Submit"...

1. I see no HTTP POSTs over Wireshark
2. The ESPEasy log keeps saying "CO11: Could not add to delay handler"

From what I can tell, ESPEasy is breaking before it even builds the HTTP packet, however, I am not sure why.

Anyone have any ideas? I've tried all kinds of differents settings, such as the following:

-Really dumbed down the HTTP headers to just the default value
-Dumbed down the HTTP body to basically "bleh" (without quotes)
-Increased "Minimum Set Interval" to 5000
-Increased "Client Timeout" to 5000
-etc

It just keeps saying "CO11: Could not add to delay handler". I understand CO11 is my HTTP controller but what is a delay handler? What does this error mean?

Thanks in advance for any help. I am at a dead end.

Fodome

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: CO11: Could not add to delay handler

#2 Post by TD-er » 16 Feb 2022, 07:59

The delay handler is something internal in ESPEasy.
It is essentially the queue manager for messages sent to a controller.

There is just a handful of reasons why this could happen:
- Queue is full and policy is set to "Keep oldest"
- No more free memory.

Which build are you using?
How often do you send data to this controller?
Can you show your controller settings?
See also https://espeasy.readthedocs.io/en/lates ... parameters
For more details on what the settings mean.

If the host you're sending to is not on your local network, set the timeout to something like 1000 msec.
Make sure you're not trying to send to a HTTPS server.

fodome
New user
Posts: 7
Joined: 16 Feb 2022, 00:43

Re: CO11: Could not add to delay handler

#3 Post by fodome » 18 Feb 2022, 05:35

Changing the queue policy to "Delete Oldest" seems to have done the trick as I'm not seeing this error message anymore.

Thanks for your help.

Fodome

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: CO11: Could not add to delay handler

#4 Post by TD-er » 18 Feb 2022, 08:44

You're welcome :)

Post Reply

Who is online

Users browsing this forum: No registered users and 21 guests