MagicLike

Members
  • Posts

    20
  • Joined

  • Last visited

MagicLike's Achievements

Noob

Noob (1/14)

3

Reputation

  1. I am not able to open the Docker page, because I restartet and now the cache is compeltely full and I get this error message: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 710 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 896
  2. I already know, what uses my diskspace: I just want to know, how i can identify, if they are used or not, so I can delete those unused...
  3. Oops, I stripped the diagnostics a bit down... The cache is only used by the appdata & system shares, if that answers your question.
  4. I grabbed the diagnosis now, and from my perspective, nothing changed in my problem: How do I identify old - now unused - Docker btrfs subvolumes, so I can clear some space on my cache drive? By the way, the Docker container aren't starting anymore: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 710 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 896 diagnostics.zip
  5. Yes, this is what I wrote in my initial message: Edit: I already faced the issue with filling up rootfs
  6. Filesystem Size Used Avail Use% Mounted on rootfs 7.8G 1.3G 6.5G 17% / tmpfs 32M 764K 32M 3% /run /dev/sda1 988M 545M 443M 56% /boot overlay 7.8G 1.3G 6.5G 17% /lib/firmware overlay 7.8G 1.3G 6.5G 17% /lib/modules devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 7.9G 168K 7.9G 1% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 82M 47M 64% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1 932G 870G 61G 94% /mnt/disk1 /dev/sdb1 58G 57G 0 100% /mnt/cache shfs 932G 870G 61G 94% /mnt/user0 shfs 932G 870G 61G 94% /mnt/user /dev/loop2 1.0G 4.1M 905M 1% /etc/libvirt tmpfs 1.6G 0 1.6G 0% /run/user/0
  7. I am not able to get the diagnostics. When I try it over the GUI, it freezes and when I try it over ssh or the normal syslog, I get the following error: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 18
  8. @S80_UK I just wanted to inform you, that it works now, got 16 GB of RAM and it just works smoothly. Thank you again!
  9. I just experienced a very annoying issue: My cache drive is filled up, with docker btrfs subvolumes, from earlier Docker containers. I can't even install new Docker containers / reinstall them. Is there a way of knowing which is used and which not, so I can delete and use my cache again?
  10. Defenetely! I read, that my Server can take 24 GB of RAM and I will put as much as I can find in it...
  11. @S80_UK You were right! I t is just not enough RAM / Nerd Pack overloaded it. Runs fine now with ~80 % RAM used. Thanks again!
  12. Just "uninstalled" nerdpack (Just deleted the plugin files manually on the flash drive)... I will try to boot now, so I can at least use my SMB shares.
  13. I am already looking for some. I know someone who might have lots of DDR3 ECC RAM... Thank you for the quick replies. I will report here what happens after I got new RAM.
  14. I tried diagnostics, but the output was only a pile of empty .txt files. So there is the copied syslog: syslog
  15. I just tried to connect via ssh, but the connection gets refused. I'll try manually via keyboard...