AsyncNetInputBuffer_c::AppendData: error 35

Лог завален ошибкой:

[Thu Aug 31 11:59:48.168 2023] [832120] WARNING: conn 192.168.0.3:30537(167), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.185 2023] [832114] WARNING: conn 192.168.0.3:30539(169), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.218 2023] [832113] WARNING: conn 192.168.0.3:30542(172), sock=1461: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.219 2023] [832107] WARNING: conn 192.168.0.3:30543(173), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.235 2023] [832117] WARNING: conn 192.168.0.3:30545(175), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.251 2023] [832126] WARNING: conn 192.168.0.3:30546(176), sock=1461: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.252 2023] [832112] WARNING: conn 192.168.0.3:30547(177), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.268 2023] [832104] WARNING: conn 192.168.0.3:30548(178), sock=1461: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1
[Thu Aug 31 11:59:48.269 2023] [832104] WARNING: conn 192.168.0.3:30549(179), sock=1462: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 35 (Resource temporarily unavailable) return -1

Попытка найти в документации или нагуглить, что это вообще за проблема - успехом не увенчались. Кто в курсе?

этот WARNING исправлен в недавнем релизе 6.2.12

1 Like