3dee

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by 3dee

  1. Not sure what solution you mean. It's the "easiest" way of connecting the server to the network. The switch model is not relevant for this, you could also just use an unmanaged switch or your standard home router.
  2. Switchport Mode access means that I'm not using VLAN tagging. I'm only using one ethernet port with a single IP address for the server. Trunk makes my server crash like every week, ipvlan does not work for me neither and I'm not willing to change every docker container from br0 to something else.
  3. Hey guys, do I run into problems going from 6.10.0-rc2 to 6.10.0 Stable? Thanks.
  4. Nope I don't use VLANs anymore with my server. Switch port is now mode access. It's stable since then.
  5. Go into Settings - VM Manager and enable advanced view. You should find Libvirt wake on lan. Other than on / off there are no settings. When running, VMs will wake up on magic packet.
  6. So I just changed it again from everthing working macvlan setting to ipvlan and re-enabled docker. Nothing else changed. The issues are back - to name some of them: binhex-teamspeak - Server not reachable through WAN IP, only LAN binhex-rtorrentvpn - No torrent conntects to its Tracker (Tracker: [Couldn't resolve host name]) swag - None of the proxy sites is reachable via its subdomain (but the containers are local reachable) pi-hole - "Maximum number of concurrent DNS queries reached (max: 150)" the webinterfaces of containers take like 10-20 seconds to connect for the first time (like owncloud or pi-hole) It seems like none of the containers can connect to the internet, but pinging a server from the container shell still works: I will switch back to macvlan for now, but I would love to get ipvlan running since it may not crash my server. Diagnostics are attached. serverpc-diagnostics-20220202-1914.zip
  7. Hey Guys, so I upgraded to version 6.10 and changed the network type to ipvlan. None of my docker containers was able to connect to the internet, only local network was working. So I changed back to macvlan and disabled vlan tagging in the network settings. Macvlan traces still showed up every then and now and last night my server crashed completely (kernel panic I guess). Is there a way I can get ipvlan working with my br0 docker containers? Or can I use macvlan with br0 containers without getting trace errors? I really don't need vlan tagging that much on my server.
  8. Yes, all my dockers are runnning on br0 with a fixed IP address. Are those macvlan call traces "bad"? Should I change all my containers to ipvlan? Edit: I should read the links before asking I will check that. Thanks!
  9. IPMI did not log anything noteworthy, but the "Minimum free space" on my cache drive was 0, so I set it to 10GB now. If it happens again, I will run memtest. Until that I hope Minimum free space was the reason for that issue. Thanks so far!
  10. Yes, the RAM is REG ECC. I will do memtest. How can I prevent the cache going full? It actually was 99% some times. I'm using rTorrent with pre allocation of space but it seems to ignore the 30GB limit of minimum free space I set up for my media share. Files usually aren't larger than 5GB but never larger than 30GB.
  11. Hello everyone, today and last week I checked my array in the morning and Unraid was kind of stuck, today for the second time. In the Webinterface Docker and Dashboard didn't load at all, the Main tab showed all my devices but nothing under "Array Operation" (like reboot or shutdown). None of my docker apps were responding. I had to cold start the system to get it back running. I don't know where I should start searching for issues. Before the shutdown I was able to pull diagnostics via SSH / WinSCP. They are untouched except for the mover logs I removed. My CPU is an Intel Xeon E5-2630L V4 ES (Engineering Sample). All the other hardware information should be in the diagnostics. I hope you can help me find the reason for my Unraid OS "crashes". Thanks! serverpc-diagnostics-20220113-0939.zip serverpc-diagnostics-20220120-0912.zip
  12. Thanks for reply, the reason was a torrent with error "Low disk space". I deleted it and all the docker.img usage disappeared. I guess due to my pre reservation of disk space setting.
  13. Thanks. I asked Supermicro Support and they confirmed there is no way
  14. Ok idk what this is but I think this plugin screwed up my server again. The bottom line says " Array Started•Warning: posix_kill() expects parameter 1 to be int, string given in /usr/local/emhttp/plugins/ca.backup2/scripts/killRsync.php on line 27" and I can't stop Docker, I can't stop the array and I can't shut down the server properly. This happened 5 days ago, this corrupted my docker.img and my cache was read-only after that. I had to clean my cache drives, put the backup back on it and setup docker again due to corrupted docker.img. I really loved the idea of this plugin but it's no option for me to re-setup my cache drives and the docker every couple of days. The diagnostics are attached, hoping this issue can be solved. Until that, the plugin is being uninstalled. serverpc-diagnostics-20210923-1058.zip
  15. Hi everyone, is there now an option to split the FAN1234 and FANA groups up for fan control? I would like to control each fan individually. My Mainboard is a Supermicro X10DRi. Thanks.
  16. @zzgus @Richamc01 I have this issue right now, how did you solve it? I don't want to kill my docker containers if possible. The array doesn't stop, I can't disable docker and "docker stop $(docker ps -a -q)" does not work either.. Edit: I can't even do halt shutdown -h now reboot su -c poweroff
  17. I had the same issue and solved it that way: 1. Uninstall Python2 from the Nerd Pack Plugin 2. cli into your unraid 3. Download Python2 for Slackware: wget https://slackware.uk/slackware/slackware64-14.2/slackware64/d/python-2.7.11-x86_64-2.txz 4. Install Python2: upgradepkg --install-new python-2.7.11-x86_64-2.txz For the last step I went to Settings, VM Manager, Advanced View enabled, Libvirt wake on lan disable, then enable again. Status: Running :)
  18. Okay, so I did root@Tower:~# docker commit 0239d37756ae mcmyadmin2-java16 sha256:6576de23caddfa03f9094079da14bff36234e655bdb0e8db82a57dfb9fd4f13f How do I replace the old one now? Sorry I really am a noob to Docker..
  19. I installed Java 16 via Console in a docker container which is not supported by Linuxserver anymore (no Updates anymore and support thread closed). After restarting the container the Java Installation is gone. How can I save the installation and keep it after a reboot / restart? Thanks!!
  20. I would like to do similar, I went into the console of linuxserver/mcmyadmin2 container to Update Java to Version 16 for Mineacraft 1.17.1. After restart the Java Update is gone. How can I make it save the changes? I tried this command (0239d37756ae is mcmyadmin2): root@Tower:~# docker commit 0239d37756ae mcmyadmin2-java16 sha256:6576de23caddfa03f9094079da14bff36234e655bdb0e8db82a57dfb9fd4f13f The container will not be updated by Linuxserver anymore, the support thread is closed: https://forums.unraid.net/topic/41907-support-linuxserverio-mcmyadmin/ Thank you
  21. Installed it again, most of the settings are back I was ignorant enough not to do that. Minimum free space is set now, I think I won't run into that issue again. Thank you so much @Squid and @trurl !!
  22. I was able to stop and start the array. Downloads are paused now, when I start it, it begins to write to disk 2, which is 500MB left. If I keep downloads running, RAM and CPU will fill up when disk 2 is full again, I'm very sure. Docker run: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-rtorrentvpn' --net='br0' --ip='192.168.1.18' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_5000'='5000' -e 'TCP_PORT_9080'='9080' -e 'TCP_PORT_9443'='9443' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='##############' -e 'VPN_PASS'='##############' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'ENABLE_AUTODL_IRSSI'='no' -e 'ENABLE_RPC2'='yes' -e 'ENABLE_RPC2_AUTH'='yes' -e 'ENABLE_WEBUI_AUTH'='yes' -e 'RPC2_USER'='admin' -e 'RPC2_PASS'='admin' -e 'WEBUI_USER'='admin' -e 'WEBUI_PASS'='admin' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,209.222.18.218' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'PHP_TZ'='UTC' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/media/Torrents/':'/data':'rw' -v '/mnt/user/appdata/binhex-rtorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-rtorrentvpn' ce6c73a7cac6d38b6b16e670ff4053c754f25bf4bd1b91871fa11577224996b2 The command finished successfully!
  23. Before the disk was full it was fine I will try as soon my Docker works again Changes were made via GUI only I set up the data path to /mnt/user/media/Torrent and the downloads are being saved to /data/ The RAM started filling up when the HDD went full. Did I maybe accidentally set it up the write to the RAM? I am not even sure how I could do that.. Whats a good way out of this situation? Stop and start the array? Reboot the Server? Still 100% RAM and CPU. How can I make sure next time the container won't fill the disk to 100% so this wont happen again?
  24. Hi! One of my Docker Container writes data to a share, wich is totally fine! But as soon as a drive reached 100%, all the docker containers stopped working. Also RAM and CPU went both to 100% and something begins to read disks.. See the Screenshots: My top Output is this: Also I cannot open the Docker Tab on the unraid web UI nor open the Docker Settings under Settings Tab → Docker It's like that for around 10 hours now, hoping it will fix itself, but no luck so far. This happened before, I rebooted "clean" then, but since then my Pi-Hole Docker is gone (can I bring it back?) and some latest changes to different docker containers are "rolled back". After that reboot the filled disk was not 100% anymore, it went down to like 99 or 98%. Now I let it fill back to 100% in the hope that this was just a bug, but now it's happening again. I attached diagnostic files. Thank you so much! serverpc-diagnostics-20210404-1042.zip
  25. Hi everyone, I already asked in the support thread for the Wake on Lan for VMs Plugin but received no help, hoping to get some help here. After enabling VLANs on the unraid machine and enabling trunk on the switchport, Wake on LAN for the VMs does not work anymore. The VMs still are on br0 and default / native VLAN ID is 1. WoL package both sent from Guacamole Docker but also sent from a Client in VLAN 1 network (192.168.1.0/24) do not wake any machine up. Usual network works as expected. Any ideas? Switch configuration: unraid Network Settings: VM XML: Diagnostic files are attached. Thanks for any help! serverpc-diagnostics-20210328-1612.zip