error: handle abandoned timeout (status=4)

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

Post Reply
ropske
Posts: 483
Joined: Tuesday 12 August 2014 5:37
Target OS: Raspberry Pi / ODroid
Domoticz version: V3_8394
Location: Rumbeke,Belgium
Contact:

error: handle abandoned timeout (status=4)

Post by ropske »

Hi,

anyone knows what this means?
I get this often in my domoticz log file:

2017-12-14 10:20:57.409 ::ffff:192.168.1.199 -> handle abandoned timeout (status=4)
SweetPants

Re: error: handle abandoned timeout (status=4)

Post by SweetPants »

Are you using IPv6?
ropske
Posts: 483
Joined: Tuesday 12 August 2014 5:37
Target OS: Raspberry Pi / ODroid
Domoticz version: V3_8394
Location: Rumbeke,Belgium
Contact:

Re: error: handle abandoned timeout (status=4)

Post by ropske »

hi SweetPants,

no i'm not using that.
SweetPants

Re: error: handle abandoned timeout (status=4)

Post by SweetPants »

ropske wrote: Thursday 14 December 2017 11:01 hi SweetPants,

no i'm not using that.
The error is coming from the webserver (webserver/connection.cpp). The host IP address (::ffff:192.168.1.199) looks a litlle weird to me. It get's a timeout reading the connection (status (4) = READING) as far as i can see, but i'm not an expert on C++
fveeken
Posts: 1
Joined: Sunday 14 July 2019 11:21
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: error: handle abandoned timeout (status=4)

Post by fveeken »

Hi,

I have the exact massage in my log. It appears every time exactly 20 minutes after initiating a backup by a backup script.

Frank.
Last edited by fveeken on Thursday 25 July 2019 13:24, edited 1 time in total.
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: error: handle abandoned timeout (status=4)

Post by waaren »

fveeken wrote: Thursday 25 July 2019 11:27 ..It appears every time exactly 20 minutes after initiating a backup by a backup script.
It looks like your network or a particular network interface is very busy causing the TCP layer to timeout. Could it be caused by a massive data transfer from the backup ?
Read this article for some background and on how to adjust timeout settings.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest