Recently switched hardware (mb and cpu) and now I am getting my log full within a couple of days. No idea what is causing the problem.

mnemosyne-diagnostics-20201028-1651.zip

 

So I don't have any custom networks right now, just one VLAN. I attached my routing table...

 

 

Server went down again because of this....

 

Not sure what to do... I suspect it is some misconfig when I changed out MB and CPU.

Can you check /var/log? open a terminal and do "ls -hal /var/log" just curious to see what is the largest file(s).

 

Also, seeing a TON of this in your syslog. You need to edit your VM settings from "virtio" to "virtio-net" for network interfaces.
Oct 27 22:53:28 mnemosyne kernel: tun: unexpected GSO type: 0x0, gso_size 1448, hdr_len 1514 <----YUCK FIX VM settings

Arch
    <interface type='bridge'>
      <mac address='52:54:00:9e:3d:49'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

Eaton IPM
	<interface type='bridge'>
      <mac address='52:54:00:e1:ef:a8'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

Pihole #2
    <interface type='bridge'>
      <mac address='52:54:00:0b:99:19'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

Windows Server 2019
    <interface type='bridge'>
      <mac address='52:54:00:69:77:2c'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

loxberry-vm
	<interface type='bridge'>
      <mac address='52:54:00:6f:49:4d'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

 

That should help clear up the TUN stuff.  Lets start there and come back

@Darksurf thanks.  Here is the output:

 

total 85M
drwxr-xr-x  9 root   root  660 Nov  9 04:40 ./
drwxr-xr-x 13 root   root  300 Sep 17 20:43 ../
-rw-r--r--  1 root   root   85 Nov  8 04:40 apcupsd.events
-rw-r--r--  1 root   root  193 Nov  8 04:40 apcupsd.events.1
-rw-------  1 root   root    0 Oct  5 11:42 btmp
-rw-r--r--  1 root   root    0 Apr  9  2020 cron
-rw-r--r--  1 root   root    0 Apr  9  2020 debug
-rw-rw-rw-  1 root   root  66K Nov  6 13:32 dmesg
-rw-rw-rw-  1 root   root  273 Nov  8 12:03 docker.log
-rw-r--r--  1 root   root    0 Jun 16 12:22 faillog
-rw-rw-rw-  1 root   root 1.3K Nov  9 13:58 ipmifan
-rw-r--r--  1 root   root    0 Apr  7  2000 lastlog
drwxr-xr-x  3 root   root  120 Nov  6 13:34 libvirt/
-rw-r--r--  1 root   root    0 Apr  9  2020 maillog
-rw-r--r--  1 root   root    0 Apr  9  2020 messages
drwxr-xr-x  2 root   root   40 May 15  2001 nfsd/
drwxr-x---  2 nobody root   60 Nov  6 13:40 nginx/
lrwxrwxrwx  1 root   root   24 Oct  5 11:41 packages -> ../lib/pkgtools/packages/
drwxr-xr-x  4 root   root   80 May 14 22:49 pkgtools/
drwxr-xr-x  2 root   root  440 Nov  6 13:34 plugins/
lrwxrwxrwx  1 root   root   25 Oct  5 11:42 removed_packages -> pkgtools/removed_packages/
lrwxrwxrwx  1 root   root   24 Oct  5 11:42 removed_scripts -> pkgtools/removed_scripts/
drwxr-xr-x  3 root   root  180 Nov  6 13:58 samba/
lrwxrwxrwx  1 root   root   23 Oct  5 11:41 scripts -> ../lib/pkgtools/scripts/
-rw-r--r--  1 root   root    0 Apr  9  2020 secure
lrwxrwxrwx  1 root   root   21 Oct  5 11:41 setup -> ../lib/pkgtools/setup/
-rw-r--r--  1 root   root    0 Apr  9  2020 spooler
drwxr-xr-x  3 root   root   60 Jul 16 09:52 swtpm/
-rw-r--r--  1 root   root 473K Nov 10 20:25 syslog
-rw-r--r--  1 root   root  11M Nov  9 04:40 syslog.1
-rw-r--r--  1 root   root  74M Nov  7 04:40 syslog.2
-rw-rw-rw-  1 root   root    0 Nov  6 13:32 vfio-pci
-rw-rw-r--  1 root   utmp 6.8K Nov  6 13:34 wtmp

 

And I changed all the virtio to virtio-net for my VMs. I have no idea what the difference is.

virtio is the old version of what was renamed to virtio-net. It looks like your syslog is what is exploding and that is most likely because of the errors from the VMs having incorrect network config types (virtio vs virtio-net) blasting that syslog file.

OK, well I switched it and will keep an eye on it. Thanks.