Slarti123

Members
  • Posts

    27
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Slarti123's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. OK, dann wäre der RAM das bottle neck und ich könnte da ein wenig nachrüsten. Wenn ich aber auf ein Cache Share vom Client hochlade, dann ist die Phase 0 MB/s teilweise fast 1min lang, bevor es weitergeht. Das ist bei größeren Mengen schon nervig. Ist es einen Versuch wert, die Cache SSD zu tauschen oder ist das unnötig? Übrigens: Vielen Dank für die schnellen und hilfreichen Antworten!
  2. Ja, das war auch tatsächlich so. Ging dann irgendwann weiter und hat den Vorgang erfolgreich abgeschlossen. Verstehe nicht, was Du meinst. Habe mich vielleicht schlecht ausgedrückt. Habe von einem Share ("Video") eine "nicht gecachte" Datei aus dem Array kopiert auf ein anderes share ("nextdata"), das als "array only" konfiguriert ist. Dabei nur als Oberfläche den Win Explorer/SMB genutzt. Lief aber kein traffic über das Netzwerk.
  3. Noch ein Nachtrag: Habe mal vom Win Client per SMB eine 13GB Datei auf das "Array only" geladen. Die ersten ca 4GB gingen mit ca 100MB/s hoch. Danach konstant bei ca. 45MB/s.
  4. Ja. S. Screenshots. Nur 1 VM für HomeAssistant mit einem Kern und 4-8 GB RAM von 32GB. Das war interessant: Habe ein file von einem share auf das "Array only" share kopiert: 7,8 GB groß. Bis 72% eine Wahnsinnsgeschwindigkeit >1GB/s. Dann auf 0 gedroppt. Das hat keine Veränderung gebracht.
  5. Hallo zusammen, ich bin nicht 100% sicher, habe aber den Eindruck, dass das Phänomen erst seit dem letzten Update auftritt: Wenn ich ein File kopiere, geht zunächst die Geschwindigkeit auf ca. 140Mb/s hoch. Nach kurzer Zeit bricht sie aber völlig ein. Geht auf 0 Mb/s, pausiert dort und schießt wieder kurz auf 140Mb/s hoch, usw. Das passiert auch, wenn ich "lokal" kopiere: Also über einen Win Client auf dem SMB Share von einem Unterordner in den Parentfolder kopiere, ohne das Netzwerk zzu nutzen. RAM/CPU sind nie voll ausgelastet und ich nutze einen SSD Cache Drive (mit Error!). Anbei ein paar Screenshots. Wo kann ich den anfangen, den Fehler einzukreisen? Danke!
  6. Hi, I'm using Gluetun with Surfshark and no territory restrictions. Recently my connection speed decreased significantly. When I restart the container, it connects to other servers. Sometimes they are faster, sometimes not. Is there a better way to receive a new IP/server with an API call or using the command line? Thanks!
  7. Hi all, I'm migrating my Home Assistant setup from a dedicated (but now dead) PC to a VM on Unraid. My Unraid Server has only one physical NIC and runs several Dockers. I have another stand alone server running OPNSense (where I manage "everything network"). My Home Assistant VM has to be on two VLANS: The "General" one, that is not tagged and all devices use (including all dockers) A "Untrusted" one (VLAN "20"), where I have some IOT devices in On my standalone Home Assistant PC I had two physical NICs and my switch took over for tagging. I guess, in my new setup I could create a virtual nic and tag that one? I am really concernced to break things on my Unraid for all other dockers, etc. So: Could someone please give an idiot-safe instruction what to do? Thank you very much!
  8. Reviving this old threat as I experience the same issue. Updated Unraid to 6.10 and now the dockers run in the subnet 172.17.0.X. My actual LAN is in 192.168.178.X I have some docker in bridge or host mode which works, but I do have some as br0 with static IPs in the range of 192.168.178.X. The br0s now cannot find the dockers in host or bridge mode, anymore. Everything worked fine before and I am not very keen to change all settings in some of the clients, etc. Any way to just bring the docker network behaviour back to how it used to be in my environment?
  9. Hi all, I've set up the Nordlynx version succesfully and also tunneling other container's traffic through it works. But I see one odd behaviour and have no clue: I use xteve as a container to provide a m3u file for clients. xteve runs through that VPN via "--net=container:nordlynx". I am able to get acccess to that m3u with every app or desktop client (http://UNRAID-IP:34400/m3u/xteve.m3u). I did add 34400 to the ports in Nordlynx and get access in the browser to the GUI. But: When I use the exact same URL in Jellyfin to get access to the m3u, it gets no access. Same behaviour in Plex, when adding it as a DVR (http://UNRAID-IP:34400)- it won't find xteve. Jellyfin and Plex are running as dockers, too, but do not use the VPN. Do I have to open Upnp or something similar, maybe? Thanks!
  10. Thank you! Solved: TL;DR had to delete everything (image, container) including the "appdata" folder and re-install without error messages.
  11. Thanks, everyone: Solved. For the record (and others): 1) Traccar: The template createa a folder called "traccar.xml". You have to delete that and upload the linked XML file, instead (and of course, do not autostart the docker, before). For some reason, that created a container that was never ever able to start again, even though I manually copied as described. Had to remove the container, delete the image, manually delete all data in "appdata" and then set everything up from scratch as desribed above. 2) TVH: to give you the full picture: still not sure about the initial reasons. Still, similar solution: completely delete container, image and "appdata". New, clean setup. Works now... Thanks a lot!
  12. Thank you! I get that one: docker: Error response from daemon: Conflict. The container name "/tvheadend_neu" is already in use by container "1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2". You have to remove (or rename) that container to be able to reuse that name.
  13. Thanks for the fast reply. My docker run shows no errors and is as follows: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='tvheadend_neu' --net='br0' --ip='192.168.178.15' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'RUN_OPTS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -v '/mnt/user/Media/Video/Aufnahmen/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend':'/config':'rw' --device='/dev/dri' --device='/dev/dvb' 'lscr.io/linuxserver/tvheadend' 1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2 The command finished successfully! What I did just see in the log is that: Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd entered promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered forwarding state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd left promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state
  14. Hi all, I've had a lot of dockers running succesfully. When I installed a new one (Traccar) I experienced an "Execution Error- bad parameter". I tried to install that as custom Br0 with own (free) IP. I did realize that in the overview the port mapping shows 0.0.0.0 instead of 192.XXX. Anyway, I had the same error with every other "Network Type". I decided to put it aside and look at it later. Another Docker was running smoothly. But I wanted a clean restart (TVHeadend). It was set up as custom Br0 with 192(...)15 and worked. I did remove it through the GUI and re-installed it as before (without any error). I did also use the same Network parameters. Now, I see the same: I cannot run the docker ("Server Error" instead of "bad parameter"), but all mappings show 0.0.0.0 instead of the desired 192....15. Any idea where to start? (not even sure, if the two occurences are dependent). Thanks!