scubieman Posted November 12, 2019 Share Posted November 12, 2019 wsdd was running 100%. I was backing up to backblaze via the VM through SMB. I shut down all dockers and vm's and it was still running high. Wondering how do i restart the service wsdd? I believe it was at 100% because of the backup happening at that time. Quote Link to comment
Hoopster Posted November 12, 2019 Share Posted November 12, 2019 (edited) @scubieman I have seen this (wsdd at 100% on 1 core or thread) twice as well. In both cases, as expected, a reboot fixed it. It happened when I had an Acronis backup running which backs up a PC/laptop to my unRAID server. The core/thread changes but one remains pegged at 100% even when the backup completes. A reboot is require to clear it. I actually had a bug report ready to go and did not post as I want to gather more info and confirm it only happens during backup. The last time I saw this was three days ago, but another backup is scheduled for tonight. Since it is wsdd, this is only a 6.8.0-RC issue. Edited November 12, 2019 by Hoopster Quote Link to comment
BRiT Posted December 17, 2019 Share Posted December 17, 2019 I wonder what triggers the bug to cause wsdd to peg 1 cpu. I ran across this tonight on 6.8 Stable. About the only thing I have running using Samba from other systems is 1 Win10 system that does media scans using 'media center master'. I looked through the syslog but didn't find anything related to it nor any indications of things going sideways, so I didnt gather diagnostics. Instead I disabled WS-Discovery option. Quote Link to comment
Michael_P Posted December 17, 2019 Share Posted December 17, 2019 This worked for me 2 Quote Link to comment
peter76 Posted December 17, 2019 Share Posted December 17, 2019 I have the same issue since update to 6.8 stable. I discovered 100% usage on 1 core of "wsdd" process after synching a Nextcloud Client to DockerNextcloudServer. Quote Link to comment
MorgothCreator Posted December 27, 2019 Share Posted December 27, 2019 Same here, What happen if I kill him or restart him from time to time? 😀 Quote Link to comment
macmanluke Posted December 28, 2019 Share Posted December 28, 2019 Just noticed i have same issue Tried -i br0 but still pegging 1 core Quote Link to comment
Michael_P Posted December 28, 2019 Share Posted December 28, 2019 You can disable it, but you may not be able to see the server shares show up under 'network' in Windows 10 clients, but you can still browse them manually by server name or IP 1 Quote Link to comment
ptr727 Posted February 7, 2020 Share Posted February 7, 2020 Same happening to me running 6.8.2. 1 Quote Link to comment
User01 Posted February 8, 2020 Share Posted February 8, 2020 (edited) Hi, 6.8.2, no -i br0 and experiencing the same issue. Stopping and starting the array seemed to stop it spiking a CPU for me. Would be good to know the root case. Thanks, Edited February 8, 2020 by User01 forgot to add last sentence. Quote Link to comment
eXtremeSHOK Posted February 12, 2020 Share Posted February 12, 2020 +1 same issue on 6.8.2 Quote Link to comment
sit_rp Posted March 22, 2020 Share Posted March 22, 2020 Just got the same thing. Quote Link to comment
BRiT Posted March 22, 2020 Share Posted March 22, 2020 The only sure way to prevent this is to disable wsdd in your unraid settings. Quote Link to comment
lamer Posted March 31, 2020 Share Posted March 31, 2020 (edited) Same happening to me with 6.8.3. edit: noticed there is already a bug report about this Edited March 31, 2020 by lamer Quote Link to comment
mindedc Posted April 20, 2020 Share Posted April 20, 2020 Any fix that doesn't kill browsing for windows machines? This has been ongoing for months..... kinda sucks that I basically don't have access to one of my CPU cores for VMs/Containers/etc... Is this a more generic SMB problem or something unraid specific? Quote Link to comment
Hoopster Posted April 20, 2020 Share Posted April 20, 2020 10 hours ago, mindedc said: Is this a more generic SMB problem or something unraid specific? I don't think Limetech had anything to do with the development of the wsd daemon. Since the problem only occurs when wsdd is running, the problem lies either with the daemon itself, or an interaction with wsdd and some other driver or kernel module. Quote Link to comment
clinkydoodle Posted April 30, 2020 Share Posted April 30, 2020 I just had this same thing, although killing the VM didn't resolve it. I then disabled each docker container in turn to see what it was, still nothing. Then finally disabled docker, then enabled it again and it quietened down. First time its happened for me though, so could just be a one time thing. I did also have a container that corrupted on me and I had to re-install it not long before this behaviour started. Quote Link to comment
JustOverride Posted April 30, 2020 Share Posted April 30, 2020 1 hour ago, clinkydoodle said: I just had this same thing, although killing the VM didn't resolve it. I then disabled each docker container in turn to see what it was, still nothing. Then finally disabled docker, then enabled it again and it quietened down. First time its happened for me though, so could just be a one time thing. I did also have a container that corrupted on me and I had to re-install it not long before this behaviour started. Try this: Quote Link to comment
clinkydoodle Posted May 1, 2020 Share Posted May 1, 2020 Thanks I haven't done it yet, but if it happens again ill give it a go. Still going strong after just restarting docker. 1 Quote Link to comment
nhm91135 Posted May 3, 2020 Share Posted May 3, 2020 I have this same problem, wsdd process pegging one of the CPU's. Simply changing any one of the parameters on the Shares tab results in the problem going away for a few hours. I am running Version 6.8.3 2020-03-05 I have made some changes recently but I don't see why that would be a cause. I am slowly backing out my changes to see if I can isolate it. Need an effective fix for this. Quote Link to comment
Viper359 Posted May 10, 2020 Share Posted May 10, 2020 I too had this issue for the last few days. Used TOP to get process ID, then killed it, than typed WSDD Windows network locations showed back up after restarting typing just WSDD, or, that did nothing, and it automagically starts back up. Hopefully, it stays normal 1 Quote Link to comment
gareth_iowc Posted May 12, 2020 Share Posted May 12, 2020 have the same problem on 6.9.0-beta1 Quote Link to comment
nhm91135 Posted May 12, 2020 Share Posted May 12, 2020 (edited) NOPE Disabling all SMB Shares does NOT make the problem go away. According to BRIT in the next post, all that need be done is to disable WSD. So I have done that. Crossing fingers. Edited May 13, 2020 by nhm91135 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.