No room on device use netcat

Expected Behaviour:

pihole -d will create a debug token and upload the log.

Actual Behaviour:

As the debug is running, I get the following after each line:
tee: /proc/2105/fd/3: No space left on device

Debug Token:

No token, it says "Use netcat."

Do I need to adjust something on Raspbian? Should be the latest version:
pi@raspberrypi:~ $ cat /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="RaspbianForums - Raspbian"
BUG_REPORT_URL="RaspbianBugs - Raspbian"

Thanks for any assistance, sorry that it's (ironically) running the debug token that's messing up, and if this is a FAQ, I looked but didn't see anything. My original issue was with FTL giving URL not found errors on a pihole -up command, but I'll fix this first before I ask for help with that.

Z

I hope this doesn't sound sarcastic but did you check to see if, as the error points out, there is space on your device?

There is plenty of space left on the memory card in the Pi. I think what might be happening is that it's not the main partition that's out, but one of the smaller partitions that handles devices? Kind of skirting the limit of my Linux knowledge here.

Run df -h

pi@raspberrypi:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  4.8G   23G  18% /
devtmpfs        484M     0  484M   0% /dev
tmpfs           489M     0  489M   0% /dev/shm
tmpfs           489M   13M  476M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           489M     0  489M   0% /sys/fs/cgroup
tmpfs           1.0M  1.0M     0 100% /tmp
/dev/mmcblk0p1   41M   21M   21M  51% /boot
tmpfs            98M     0   98M   0% /run/user/1000

Probably the /tmp filesystem being full, isn't it. Didn't notice that before.

Yes, so /tmp is very small and very full.

OK fair enough. You got a crib sheet or link on how to increase that (taking space away from / to do so)?

Not sure, but I'm sure Google does :wink:

You might find some clues in /etc/fstab

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