Hi sudoers,
/tmp on saros (gateway router) has been filling up with files generated by netdata.
e.g.:
$ ls -latr /tmp
[...]
drwx------ 3 root root 64 Oct 7 06:25 netdata-updater-nqKict
drwx------ 3 root root 89 Oct 7 06:26 netdata-libbpf-IMKz3n
drwx------ 3 root root 64 Oct 8 06:25 netdata-updater-aFiv4o
drwx------ 3 root root 89 Oct 8 06:26 netdata-libbpf-wnBwqo
drwx------ 3 root root 64 Oct 9 06:25 netdata-updater-JDovyN
drwx------ 3 root root 89 Oct 9 06:26 netdata-libbpf-Uz8r2x
drwx------ 3 root root 64 Oct 10 06:25 netdata-updater-Ms8q9s
drwx------ 3 root root 89 Oct 10 06:26 netdata-libbpf-zdPMcw
drwx------ 3 root root 64 Oct 11 06:25 netdata-updater-XTAGz0
[...]
When /tmp fills up, it's hard to use the shell, as e.g. bash gives this error when attempting to do a tab completion: "-bash: cannot create temp file for here-document: No space left on device"
I made a script to move away old netdata tmp files:
/home/cel/bin/move-away-tmpbloat.sh
I used that to move some into /var/local/tmp.
Is there a need to keep these old netdata tmp files, or should they just be removed? In my script I select ones that are more than 30 days old. That leaves /tmp at 59% filled (770M/1.3G) currently.
~cel(Charles)
I've been troubleshooting at omni for a while now. The wifi appears to
work for me, as do the main gateway and the door computer, but various
ethernet-connected devices do not work. I don't know why, but I
suspect the problem is one of the switches is either misconfigured or
malfunctioning, or the maze of ethernet got incorrectly rearranged
somehow in yesterday's withdrawal-induced panic.
I didn't set up these switches, or the connections throughout the
building, the cables are not labelled, and I don't know if the
switches are documented. I'm exhausted and frustrated because I
couldn't figure this out in 2 hours, because things weren't labelled,
and because there's so many people in the building who don't seem to
be here for essential work, and/or who aren't wearing masks or wearing
them improperly.
I'm not even enthusiastic about making the public computers or office
computers work again, because I'm not convinced they are essential
enough to encourage people to sit around and put food service workers
at greater risk.
So I'm going home. Sorry all, someone else will have to figure this out.
StatusCake Alert -- statuscake.com
Website Monitoring
Your website https://sudoroom.org has encountered an error.
Reason: Timeout / Connection Refused
To view more details about this error, log into your account now: https://app.statuscake.com/
The gateway has been replaced with a desktop computer sitting on its
side in the rack on top of the multi-hd storage server. Note that this
is super janky since the two PCI network cards can't be mounted
properly in the somewhat-smaller-than-standard case.
We added two network cards and were planning to use the built-in card
as well, but currently the built-in card is not used and the private
network is down. There are two reasons:
* The switch used for the private network had one of its fans die and
I turned it off until we can replace the fan so it won't overheat
* The built-in network card appears to need firmware which I'm not
going to bother with until the fan on the private network switch is
replaced
Also, we might get a new server rather than using this old desktop machine.
The new computer is using the old harddrive. I changed the following
files due to the different names of the network interfaces:
/etc/network/interfaces
/etc/default/isc-dhcp-server
/etc/iptables/rules.v4
/etc/iptables/rules.v6
You can find backups of the files from before my changes at the same
paths with .old added (for the parent dir for /etc/iptables)
--
marc/juul
