rainrain
Members
-
Joined
-
Last visited
-
> What problem exactly? Popup saying failed to communicate? Or download failure? Failure to communicate. I just repeated the experiment. VPN from US to EU == no communication. Direct connection in the US == works as expected.
-
Same problem on 6.12.14, but disabling my VPN connection solves it for me. Was there filtering added to the community apps server?
-
Just upgraded from 6.11.5 to 6.12.3 and am experiencing near daily crashes. The machine does not respond to web ui or even pings after this crash occurs. I run about 12 dockers and a VM running hasos/homeassistant. Log from a remote syslog is attached. unraid.crash.log
-
I'm slightly creeping up after 2 weeks. root@Tower:~# !45 cat /proc/sys/kernel/pty/nr 3714 root@Tower:~# uptime 21:28:59 up 17 days, 10:55, 0 users, load average: 0.35, 0.29, 0.27 root@Tower:~#
-
After 3 days after a reboot my open ptys are holding steady at 3524 (give-or-take). After hitting this point I dont see ptys not being closed anymore.
-
Same thing on my box: cat /proc/sys/kernel/pty/max == 4096 cat /proc/sys/kernel/pty/nr == 3518 cat /proc/sys/kernel/pty/reserve == 1024 I'm not creating my own containers.
-
I'm seeing the same thing when opening the console window to any running docker container. A reboot fixes it a few hours, but at some point this happens again. Same symptoms as you - stopping/restarting doesn't help. My docker.img is not full.