Hello,
Using async http, sometimes I get a timeout error. statusCode reports code 28 whilst statusText reports "Timeout was reached" (which is what is expected). I would expect code 408 instead of 28. Am I wrong?
item.statusCode = 28? [Solved]
Moderator: leecollings
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
item.statusCode = 28?
Debian buster on NUC and three RPi with buster.
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: item.statusCode = 28?
From the sendsync() 6 docs: “If the statuscode is 100 or higher, it is a real HTTP status code returned from the server; if it is between 0 and 99, there was an error sending the request.”Number8 wrote: Tuesday 10 November 2020 13:58 Using async http, sometimes I get a timeout error. statusCode reports code 28 whilst statusText reports "Timeout was reached" (which is what is expected). I would expect code 408 instead of 28. Am I wrong?
Errors 0-99 match curl errors: 28 is “Operation timeout. The specified time-out period was reached according to the conditions.”
So error 28 notify you that something is wrong on the senders side.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
Re: item.statusCode = 28?
Thanks waaren, this is very valuable information
Debian buster on NUC and three RPi with buster.
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
Re: item.statusCode = 28?
Let me get back on this cURL error 28. I understand the error is triggered by the sender, that is dzVEnts itself, in other words, by Domoticz itself. I'm wondering what can I do about that. How can it be tackled? The code is pretty straightforward
ipxURL is a private IP (LAN)
It is trigerred by the timer every minute. It fails a few times a day. What could be the root cause of the failure?
Current dz version is 2020.2 12485
Thank you
Code: Select all
dz.openURL({
url = ipxURL,
callback = 'IPX800v3'
})
It is trigerred by the timer every minute. It fails a few times a day. What could be the root cause of the failure?
Current dz version is 2020.2 12485
Thank you
Debian buster on NUC and three RPi with buster.
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: item.statusCode = 28?
Just guessing but it could be a hickup in your LAN or router or a very busy system.Number8 wrote: Tuesday 10 November 2020 16:01 It is trigerred by the timer every minute. It fails a few times a day. What could be the root cause of the failure?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
Re: item.statusCode = 28?
You mean the gear on which Domoticz is installed?very busy system
Everything is wired 1Gb/s, so taking account what is expected on the LAN, I can't expect any bottleneck. Hardware is NUC Intel, i5 6260 with 8GB of memory
Does this error mean that the TCP/IP can't even leave the interface?
Debian buster on NUC and three RPi with buster.
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: item.statusCode = 28?
The messages tells you that curl (program or library) did not receive anything back within the default time. So no response from the target nor any error message.Number8 wrote: Tuesday 10 November 2020 19:59 Does this error mean that the TCP/IP can't even leave the interface?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
Number8
- Posts: 374
- Joined: Friday 23 May 2014 7:55
- Target OS: Linux
- Domoticz version: 2022.1
- Location: Saint Pierre de Jards
- Contact:
Re: item.statusCode = 28? [Solved]
All right, this is very clear, thanks again
Debian buster on NUC and three RPi with buster.
Who is online
Users browsing this forum: No registered users and 1 guest