pinion Posted June 5, 2016 Share Posted June 5, 2016 You can add me to the list. Been getting it awhile. 6.1.9.... annoying. WTF is being done? kernel:unregister_netdevice: waiting for lo to become free. Usage count It's a kernel thing and outside of lt control. Aside from the annoyance it is completely harmless Sent from my LG-D852 using Tapatalk 10-4, safe to ignore! Quote Link to comment
jonesy8485 Posted July 7, 2016 Share Posted July 7, 2016 Just had my server stop responding to anything; even just a ping. I changed to a local monitor plugged into the box, and this error was shown but server would not respond to the keyboard. I had to hit the reset button and start a parity check. Any ideas? I had just started a 5-run preclear on a new HDD via the preclear plugin and had 5 PMS streams going with 3 transcodes. Running a Xeon E5-2670 now. Running PMS, plexpy, NZBget, couchpotato, sickbeard, cadviser, mumbleserver, nginx, plexrequests, and transmission docker containers. Did I just have too much going on? Quote Link to comment
CHBMB Posted July 7, 2016 Share Posted July 7, 2016 Just had my server stop responding to anything; even just a ping. I changed to a local monitor plugged into the box, and this error was shown but server would not respond to the keyboard. I had to hit the reset button and start a parity check. Any ideas? I had just started a 5-run preclear on a new HDD via the preclear plugin and had 5 PMS streams going with 3 transcodes. Running a Xeon E5-2670 now. Running PMS, plexpy, NZBget, couchpotato, sickbeard, cadviser, mumbleserver, nginx, plexrequests, and transmission docker containers. Did I just have too much going on? This message is harmless. Start a new thread and post diagnostics. Quote Link to comment
slushieken Posted September 19, 2016 Share Posted September 19, 2016 I have been receiving this error regularly for some time. unregister_netdevice: waiting for lo to become free. Usage count = 1 Much of the time, it is harmless and nothing happens. Sometimes though, everything grinds to very nearly a full stop re: networking. This is full OS affecting and I cannot connect via the GUI at all, and even when connected via SSH/Telnet command completion becomes hard as the connection goes in and out. This situation remains so, until a full reboot can be executed. Can't test restarting docker only, as connectivity becomes so problematic at that point issuing commands becomes difficult. It seems, via research, this is a cross platform kernel related issue, and shows up most commonly when using docker containers with high network activity (for example, torrents). It seems it is also intermittent, and therefore hard to reproduce except in a production environment with lots of connections. Devs indicate it seems to be related to hairpin mode networking, and if this can be disabled it stops. Hairpin mode is used by default on containers. Suggested workarounds found so far are: Disable IPV6 in the containers. hard to do as even if docker is configured to not use IPV6, it seems it still uses it anyway. Additionally, even when disabled in the kernel via boot parameters, many say it did not fix the issue. Set docker networking to promiscuous mode. This disables hairpin mode. Anyone know how to do this on a container? I don't know myself. This worked for users of kubernetes and some others. Final suggestions I would offer are to: Not use docker containers for torrents. Only until fixed anyway. I am probably going this route unless I can get promiscuous mode going, and it works. Quote Link to comment
Outlet6957 Posted March 7, 2017 Share Posted March 7, 2017 Having the same issue kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 Quote Link to comment
Squid Posted March 7, 2017 Author Share Posted March 7, 2017 Having the same issue kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 As previously noted the message is harmless and only annoying because it'll show up on all open ssh terminals to the system. It is cross platform and docker related but containers do not have to be running for it to triggerSent from my LG-D852 using Tapatalk Quote Link to comment
gurulee Posted April 1, 2017 Share Posted April 1, 2017 I have been finding my unraid 6.3.2 become unresponsive in WebUI and all docker apps were also unresponsive. However, I can still SSH in. The only indication of a problem is this related error in screen-shot. If I wait 5min or so, the WebUI and docker app begin responding again. This is a problem and I want to avoid blowing away my docker img if possible if that's the end result. Quote Link to comment
ZataH Posted April 16, 2017 Share Posted April 16, 2017 On 4/1/2017 at 4:05 PM, guruleenyc said: I have been finding my unraid 6.3.2 become unresponsive in WebUI and all docker apps were also unresponsive. However, I can still SSH in. The only indication of a problem is this related error in screen-shot. If I wait 5min or so, the WebUI and docker app begin responding again. This is a problem and I want to avoid blowing away my docker img if possible if that's the end result. Mine has the same message on console. And webui are not responding. Docker and shares seem to work Quote Link to comment
jademonkee Posted June 6, 2017 Share Posted June 6, 2017 Sorry to dig up an aged thread, but I thought I'd just note that I onlly just started getting the error, and it seems to have been caused by me activating the CA backups app - I received the error for the first time as it ran (also for the first time) last night: Jun 6 04:00:01 Percy root: ####################################### Jun 6 04:00:01 Percy root: Community Applications appData Backup Jun 6 04:00:01 Percy root: Applications will be unavailable during Jun 6 04:00:01 Percy root: this process. They will automatically Jun 6 04:00:01 Percy root: be restarted upon completion. Jun 6 04:00:01 Percy root: ####################################### Jun 6 04:00:01 Percy root: Stopping binhex-sabnzbdvpn Jun 6 04:00:02 Percy kernel: docker0: port 1(veth175b19c) entered disabled state Jun 6 04:00:02 Percy kernel: vetha7ec8d4: renamed from eth0 Jun 6 04:00:02 Percy kernel: docker0: port 1(veth175b19c) entered disabled state Jun 6 04:00:02 Percy kernel: device veth175b19c left promiscuous mode Jun 6 04:00:02 Percy kernel: docker0: port 1(veth175b19c) entered disabled state Jun 6 04:00:02 Percy root: docker stop -t 30 binhex-sabnzbdvpn Jun 6 04:00:02 Percy root: Stopping CrashPlan Jun 6 04:00:03 Percy root: docker stop -t 30 CrashPlan Jun 6 04:00:03 Percy root: Stopping LogitechMediaServer Jun 6 04:00:04 Percy root: docker stop -t 30 LogitechMediaServer Jun 6 04:00:04 Percy root: Stopping PlexMediaServer Jun 6 04:00:04 Percy root: docker stop -t 30 PlexMediaServer Jun 6 04:00:04 Percy root: Stopping Sonarr Jun 6 04:00:08 Percy kernel: veth3219885: renamed from eth0 Jun 6 04:00:08 Percy kernel: docker0: port 2(vethd9358f8) entered disabled state Jun 6 04:00:08 Percy kernel: docker0: port 2(vethd9358f8) entered disabled state Jun 6 04:00:08 Percy kernel: device vethd9358f8 left promiscuous mode Jun 6 04:00:08 Percy kernel: docker0: port 2(vethd9358f8) entered disabled state Jun 6 04:00:08 Percy root: docker stop -t 30 Sonarr Jun 6 04:00:08 Percy root: Stopping Subsonic Jun 6 04:00:11 Percy ntpd[1648]: Deleting interface #3 docker0, 172.17.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=442096 secs Jun 6 04:00:12 Percy root: docker stop -t 30 Subsonic Jun 6 04:00:12 Percy root: Deleting Old USB Backup Jun 6 04:00:12 Percy root: Backing up USB Flash drive config folder to /mnt/user/appdata/Community_Applications_USB_Backup Jun 6 04:00:12 Percy root: Using command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log" /boot/ "/mnt/user/appdata/Community_Applications_USB_Backup" > /dev/null 2>&1 Jun 6 04:00:31 Percy root: Backing up VM XML's to /mnt/user/appdata/Community_Applications_VM_XML_Backup Jun 6 04:00:31 Percy root: Backing Up appData from /mnt/user/appdata/ to /mnt/user/Backup/ca_backup_app/[email protected] Jun 6 04:00:31 Percy root: Using command: /usr/bin/rsync -avXHq --delete --exclude "/mnt/cache/docker.img" --log-file="/var/lib/docker/unraid/ca.backup.datastore/appdata_backup.log" "/mnt/user/appdata/" "/mnt/user/Backup/ca_backup_app/[email protected]" > /dev/null 2>&1Jun 6 04:01:58 Percy kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 Jun 6 04:05:31 Percy kernel: mdcmd (92): spindown 5 Jun 6 05:05:33 Percy root: Backup Complete Jun 6 05:05:33 Percy Docker Auto Update: Community Applications Docker Autoupdate running Jun 6 05:05:33 Percy Docker Auto Update: Checking for available updates Jun 6 05:05:41 Percy Docker Auto Update: No updates will be installed Jun 6 05:05:41 Percy root: Restarting binhex-sabnzbdvpn Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered blocking state Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered disabled state Jun 6 05:05:41 Percy kernel: device veth3eb24e2 entered promiscuous mode Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered blocking state Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered forwarding state Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered disabled state Jun 6 05:05:41 Percy kernel: eth0: renamed from vethd19f670 Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered blocking state Jun 6 05:05:41 Percy kernel: docker0: port 1(veth3eb24e2) entered forwarding state Jun 6 05:05:41 Percy root: Restarting CrashPlan Jun 6 05:05:42 Percy root: Restarting LogitechMediaServer Jun 6 05:05:42 Percy root: Restarting PlexMediaServer Jun 6 05:05:42 Percy root: Restarting Sonarr Jun 6 05:05:42 Percy kernel: docker0: port 2(veth2b832af) entered blocking state Jun 6 05:05:42 Percy kernel: docker0: port 2(veth2b832af) entered disabled state Jun 6 05:05:42 Percy kernel: device veth2b832af entered promiscuous mode Jun 6 05:05:42 Percy kernel: docker0: port 2(veth2b832af) entered blocking state Jun 6 05:05:42 Percy kernel: docker0: port 2(veth2b832af) entered forwarding state Jun 6 05:05:42 Percy kernel: docker0: port 2(veth2b832af) entered disabled state Jun 6 05:05:43 Percy kernel: eth0: renamed from veth3fe410a Jun 6 05:05:43 Percy kernel: docker0: port 2(veth2b832af) entered blocking state Jun 6 05:05:43 Percy kernel: docker0: port 2(veth2b832af) entered forwarding state Jun 6 05:05:43 Percy root: Restarting Subsonic Jun 6 05:05:44 Percy root: ####################### Jun 6 05:05:44 Percy root: appData Backup complete Jun 6 05:05:44 Percy root: ####################### Jun 6 05:05:44 Percy root: Rsync log to flash drive disabled Jun 6 05:05:44 Percy ntpd[1648]: Listen normally on 4 docker0 172.17.0.1:123 Jun 6 05:05:44 Percy ntpd[1648]: new interface(s) found: waking up resolver Jun 6 05:05:44 Percy root: Backup / Restore Completed Quote Link to comment
deusxanime Posted September 21, 2017 Share Posted September 21, 2017 (edited) Just started using unRAID and got everything setup and has been working great with basic array and a single CentOS7 VM (migrated my Plex over for now, eventually want to move to container most likely). File copies were usually 50-60 mbps, so not too bad. So now I am trying to start adding docker containers and first one I setup is binhex-rtorrentvpn. Now that I added docker I'm seeing this thread's OP error/message popup when I'm in an SSH session to my unRAID server. Maybe related, maybe not, is that the ruTorrent web GUI in the container seems to have issues connecting to rTorrent. Frequently get timed out in there. Also even more worrying though is that trying to copy from external source to the array and it is agonizingly slow now. Mostly copy speeds are less than 1 mbps. Sometimes jumps up a bit but still crazy slow. Also seems to be killing unRAID web GUI. Barely responsive. Should I skip trying to run torrents in a container and use a VM instead? I'm going to try to reboot unRAID and see if that clears stuff out at least. edit: After reboot it seems to be back to normal. I test copied a ~6.5GB file back and forth from the array and hit speeds I was talking about earlier, or even better! Haven't started VM or container up yet, but will test it by bringing up one at a time. Really wondering if it is as @slushieken said and it can just completely kill networking when this hits. As they said though, maybe better to run torrents in a VM rather than docker container until it can be fixed? Edited September 21, 2017 by deusxanime Quote Link to comment
ZachunRAID Posted January 1, 2021 Share Posted January 1, 2021 I started a new thread because this one is super old, but I am having this issue as well on 6.8.3 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.