What's new

Samba error msg: smbd[9692] after upgrade to 380.68_4 (RT-AC68U)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

rac_ja

New Around Here
Hi all,
I noticed some wired error messages which never appeared before. It just started after upgrade to Merlin 380.68_4 firmware. Is it some kind of bug? Here's my log:
Code:
Oct  9 14:56:02 smbd[9692]: [2017/10/09 14:56:02.329576,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:56:02 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:45 smbd[9692]: [2017/10/09 14:57:45.455642,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:45 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:46 smbd[9692]: [2017/10/09 14:57:46.968745,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:46 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:48 smbd[9692]: [2017/10/09 14:57:48.389414,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:48 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:49 smbd[9692]: [2017/10/09 14:57:49.868209,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:49 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:51 smbd[9692]: [2017/10/09 14:57:51.163115,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:51 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:52 smbd[9692]: [2017/10/09 14:57:52.722686,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:52 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:54 smbd[9692]: [2017/10/09 14:57:54.585529,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:54 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:55 smbd[9692]: [2017/10/09 14:57:55.769402,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:55 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 14:57:58 smbd[9692]: [2017/10/09 14:57:58.026511,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 14:57:58 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:33 smbd[9692]: [2017/10/09 15:08:33.226917,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:33 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:35 smbd[9692]: [2017/10/09 15:08:35.028304,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:35 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:36 smbd[9692]: [2017/10/09 15:08:36.807306,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:36 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:38 smbd[9692]: [2017/10/09 15:08:38.087656,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:38 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:40 smbd[9692]: [2017/10/09 15:08:40.669254,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:40 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:42 smbd[9692]: [2017/10/09 15:08:42.056392,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:42 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:43 smbd[9692]: [2017/10/09 15:08:43.660630,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:43 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:45 smbd[9692]: [2017/10/09 15:08:45.788117,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:45 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:46 smbd[9692]: [2017/10/09 15:08:46.848586,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:46 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:48 smbd[9692]: [2017/10/09 15:08:48.599015,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:48 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:49 smbd[9692]: [2017/10/09 15:08:49.433949,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:49 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.
Oct  9 15:08:52 smbd[9692]: [2017/10/09 15:08:52.190704,  0] smbd/posix_acls.c:1762(create_canon_ace_lists)
Oct  9 15:08:52 smbd[9692]:   create_canon_ace_lists: unable to map SID S-1-5-21-99998652-783196105-2974951731-1000 to uid or gid.

If there's anything more you need for further investigation (some data, details), please don't hesitate to ask. I'll be thankful :)

Regards.
 
My first guess would be that a) the disk is formatted as NTFS, b) the files/folders on that disk were created by a Windows PC, and c) there is no user name on the Asus/Samba screen that matches the Windows user account that created the file/folders.
 
My first guess would be that a) the disk is formatted as NTFS, b) the files/folders on that disk were created by a Windows PC, and c) there is no user name on the Asus/Samba screen that matches the Windows user account that created the file/folders.

a) Yes, the disk was formatted as NTFS. It was done two years ago. Since then nothing was changed. It is connected the same as it was connected before the upgrade to 380.64_4.
b) Correct again, but it was like that since the very beginning. Some new folders might appear recently, but if they did, they were created the same way as always.
c) This is Windows 10 which connects to the Samba server on RT-AC68U, so the Asus login credentials are being used in Windows 10. The log comes from Asus.
 
It might be useful just to run this command from the Windows command prompt and verify the Windows account name associated with the SID:

wmic useraccount get name,sid

When I asked whether the files were created by Windows I meant, were they created whilst the drive was plugged directly into the Windows PC?

Does it only happen when trying to access certain files?
 
It might be useful just to run this command from the Windows command prompt and verify the Windows account name associated with the SID:
wmic useraccount get name,sid
Done, results:
Code:
Name            SID
Administrator   S-1-5-21-2533733429-3411659595-3940424942-500
DefaultAccount  S-1-5-21-2533733429-3411659595-3940424942-503
defaultuser0    S-1-5-21-2533733429-3411659595-3940424942-1000
Guest           S-1-5-21-2533733429-3411659595-3940424942-501
Login          S-1-5-21-2533733429-3411659595-3940424942-1001


When I asked whether the files were created by Windows I meant, were they created whilst the drive was plugged directly into the Windows PC?
Some of them - yes.


Does it only happen when trying to access certain files?
Not sure, I'll be monitoring it.
 
The error messages have not appear again. They were probably justifiable, but I still don't know the reason. That was probably some coincidence, that they appeared shortly after update. Thread can be closed I guess.

PS Thank you ColinTaylor for your assistance.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top