March 28, 20215 yr Hello there, Had this problem for the first time ever (looks like it happened after a Nextcloud docker's update). Rebooting the server fixed (at least for now). Cheers.
April 24, 20215 yr @limetechthis issue is open since November 2019, I suffer it from over a year (my report here https://forums.unraid.net/bug-reports/stable-releases/683-wsdd-process-at-100-r1123 I know your saying that no response does not mean the issue is not looked at, but this a year and a half. I have also suggested something which may be related in my post, is it ever going to be looked at? Thanks. btw (-i br0 does not solve it for me, two machines suffer from the same issue)
May 3, 20215 yr On 4/24/2021 at 3:18 PM, thecode said: @limetechthis issue is open since November 2019, I suffer it from over a year (my report here https://forums.unraid.net/bug-reports/stable-releases/683-wsdd-process-at-100-r1123 I know your saying that no response does not mean the issue is not looked at, but this a year and a half. I have also suggested something which may be related in my post, is it ever going to be looked at? Thanks. btw (-i br0 does not solve it for me, two machines suffer from the same issue) Also had this issue on my otherwise fantastic 6.9.2 server. Added workaround. Will report back.
May 27, 20215 yr Same here tonight for the first time as far as i'm aware. Asolutely nothing running, system standing idle for days, disks spun down. just dipped in to have a look, see alls ok and one cpu pegged at 100% by wsdd process. Switched of in settings and it's aok again. No idea what harm that has done, if any? If i mount a local to remote share time to time will this be affected?
July 31, 20214 yr I faced this issue for the first time today, and it was solved by just restarting the Docker from Settings menu I shall try using -i br0 in WSD Options under SMB settings. I am running docker on VLAN br0.150, so not very sure if that will work. I shall report back once I get the issue solved.
July 31, 20214 yr 3 hours ago, samba_69 said: I faced this issue for the first time today, and it was solved by just restarting the Docker from Settings menu Thanks, this resolved it for me as well and is preferred over a reboot. I only had one container running (sabnzb) and now I have none (but docker is active), so I'm curious if it'll happen again under these conditions. Edited July 31, 20214 yr by nate1749
September 1, 20214 yr Quote Other Changes We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core. This will be fixed in Unraid v6.10.
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.