Jump to content

winbindd, smbd warning notices in syslog


Recommended Posts

Hi, running 6.9.1 here on a Supermicro mITX server board with an SOC D-1518 Xeon/32GB registered EC memory.

 

I am getting some interesting asserts or warnings in the log about "possible deadlock" and I'm trying to understand what exactly it is doing.  It may be inconsequential and I haven't noticed anything bad happening, but I first noticed it after I set my three drives to spin-down after 15 minutes of idle time.  It may be that it was happening before this and I didn't notice since I really did look hard at the syslog after doing the spin-down setting to see if it was working and how much time they were up and down.

 

Here are the most recent syslog entries:

Apr 13 14:38:14 Samwise emhttpd: read SMART /dev/sdb
Apr 13 14:38:14 Samwise emhttpd: read SMART /dev/sdc
Apr 13 14:54:46 Samwise emhttpd: spinning down /dev/sdb
Apr 13 14:54:46 Samwise emhttpd: spinning down /dev/sdc
Apr 13 15:31:46 Samwise emhttpd: read SMART /dev/sdb
Apr 13 15:31:48 Samwise emhttpd: read SMART /dev/sdc
Apr 13 15:48:08 Samwise emhttpd: spinning down /dev/sdb
Apr 13 15:48:08 Samwise emhttpd: spinning down /dev/sdc
Apr 13 16:13:45 Samwise apcupsd[18216]: Power failure.
Apr 13 16:13:47 Samwise apcupsd[18216]: Power is back. UPS running on mains.
Apr 13 16:24:14 Samwise apcupsd[18216]: Power failure.
Apr 13 16:24:16 Samwise apcupsd[18216]: Power is back. UPS running on mains.
Apr 13 16:24:19 Samwise apcupsd[18216]: Power failure.
Apr 13 16:24:22 Samwise apcupsd[18216]: Power is back. UPS running on mains.
Apr 13 17:18:08 Samwise winbindd[5039]: [2021/04/13 17:18:08.663506, 0] ../../source3/winbindd/winbindd_samr.c:683(sam_sid_to_name)
Apr 13 17:18:08 Samwise winbindd[5039]: sam_sid_to_name: possible deadlock - trying to lookup SID S-1-5-80-2375682873-768044350-3534595160-1005545032-2873800392
Apr 13 17:18:08 Samwise smbd[29253]: [2021/04/13 17:18:08.664190, 0] ../../source3/smbd/posix_acls.c:2115(create_canon_ace_lists)
Apr 13 17:18:08 Samwise smbd[29253]: create_canon_ace_lists: unable to map SID S-1-5-80-2375682873-768044350-3534595160-1005545032-2873800392 to uid or gid.
Apr 13 17:18:08 Samwise smbd[29253]: [2021/04/13 17:18:08.850186, 0] ../../source3/smbd/posix_acls.c:2115(create_canon_ace_lists)
Apr 13 17:18:08 Samwise smbd[29253]: create_canon_ace_lists: unable to map SID S-1-5-80-2375682873-768044350-3534595160-1005545032-2873800392 to uid or gid.

 

If you have any idea what's happening, please let me know.

 

Thanks!

Link to comment

Nope.  We had some wind that caused some transients that tripped all the UPS in the house.  The other instances of the messages in the syslog are not near any other UPS events.  These winbindd/smbd events seem to happen periodically but not with any consistency.  I have a Raspberry Pi that had one share mounted.  I unmounted that just a bit ago to see if that is causing it.  Mounting that share is also fairly recent so it may be coincidental with the onset of the messages.  I don't remember seeing them before updating to 6.9.1 either.  The SIDs it is looking up do appear to be Windows SIDs but I'm not sure where they are coming from.  That's what makes me wonder about the Raspberry Pi.  I can look up SIDs on Windows machines, but I don't know where it would come from on a Linux machine using a SAMBA share.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...