FTL.log flooded fs system 100% full / Could not accept() in listener()

Help
1

Not sure what happened but pihole seem running wild, needed to restart complete system to get rid of super fast growing /var/log/pihole/FTL.log, mainly all about:

[2022-07-29 20:45:21.947 1251/T1253] WARN: Could not accept() in listener() (/__w/FTL/FTL/src/api/socket.c:267): Socket operation on non-socket

[2022-07-29 20:45:21.947 1251/T1253] WARN: Could not accept() in listener() (/__w/FTL/FTL/src/api/socket.c:267): Socket operation on non-socket
[2022-07-29 20:45:21.947 1251/T1253] IPv4 telnet error: Success (0)
[2022-07-29 20:45:21.948 1251/T1253] WARN: Could not accept() in listener() (/__w/FTL/FTL/src/api/socket.c:267): Socket operation on non-socket
[2022-07-29 20:45:21.948 1251/T1253] IPv4 telnet error: Success (0)
[2022-07-29 20:45:21.948 1251/T1253] WARN: Could not accept() in listener() (/__w/FTL/FTL/src/api/socket.c:267): Socket operation on non-socket

Any hint/help would be appreciated.
Mike

2

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

3

Behaviour is gone after restart

4

@Bucking_Horn https://tricorder.pi-hole.net/2LWcFV5L/

5

Are you running PADD? There is an unresolved issue with v3.8.0.

To mitigate, you can run PADD v3.7.1
This is the raw file
https://raw.githubusercontent.com/pi-hole/PADD/v3.7.1/padd.sh

Download and replace your PADD.sh

2 Likes
6

Yes, running padd v3.8.0 - occationally from time to time not with the special hardware part but within a pi shell window. Will the error triggered by execution start or only during runtime?

7

Runtime.

8

Ok, thx, will step back to 3.7.1 for mitigation

9

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.