[Samba] Fwd: samba-gpupdate nsswitch error

[Dr. Nicola Mingotti]

Hi all,

Peter, i think i have a problem similar to yours.

I am running on Debian stable, package, bullseye backports
---
$> /usr/sbin/samba --version
Version 4.17.5-Debian
---

I just moved my "dc" from another machine, using the join/demote 
procedure. Everything fine, but I see this ugly message in "journalctl -xe"
-----------
Mar 13 15:31:41 dc1 smbd[448]: [2023/03/13 15:31:41.131439,  0] 
../../source3/smbd/server.c:1741(main)
Mar 13 15:31:41 dc1 smbd[448]:   smbd version 4.17.5-Debian started.
Mar 13 15:31:41 dc1 smbd[448]:   Copyright Andrew Tridgell and the Samba 
Team 1992-2022
Mar 13 15:31:41 dc1 winbindd[482]: [2023/03/13 15:31:41.213830, 0] 
../../source3/winbindd/winbindd.c:1440(main)
Mar 13 15:31:41 dc1 winbindd[482]:   winbindd version 4.17.5-Debian started.
Mar 13 15:31:41 dc1 winbindd[482]:   Copyright Andrew Tridgell and the 
Samba Team 1992-2022
Mar 13 15:31:41 dc1 winbindd[482]: [2023/03/13 15:31:41.548236, 0] 
../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache)
Mar 13 15:31:41 dc1 winbindd[482]:   initialize_winbindd_cache: clearing 
cache and re-creating with version number 2
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.225330, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: 
add_local_groups: SID S-1-5-21-2112549936-2540803609-4198596461-1600 -> 
getpwuid(3000148) failed, is nsswitch configured?
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.225694, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: Traceback 
(most recent call last):
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.225754, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: File 
"/usr/sbin/samba-gpupdate", line 133, in <module>
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.225961, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]: /usr/sbin/samba-gpupdate:     
apply_gp(lp, creds, store, gp_extensions, username,
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.225986, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: File 
"/usr/lib/python3/dist-packages/samba/gp/gpclass.py", line 437, in apply_gp
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.226791, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]: /usr/sbin/samba-gpupdate:     gpos = 
get_gpo_list(dc_hostname, creds, lp, username)
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.226857, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: File 
"/usr/lib/python3/dist-packages/samba/gp/gpclass.py", line 373, in 
get_gpo_list
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.226986, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]: /usr/sbin/samba-gpupdate:     gpos = 
ads.get_gpo_list(username.split('\\')[-1])
Mar 13 15:31:42 dc1 winbindd[482]: [2023/03/13 15:31:42.227029, 0] 
../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler)
Mar 13 15:31:42 dc1 winbindd[482]:   /usr/sbin/samba-gpupdate: 
RuntimeError: Failed to get machine token for 'DC1$'(CN=DC1,OU=Domain 
Controllers,DC=windom,DC=borghi,DC=lan): The specified account does not 
exist.
-----------

I checked, the message was also in the old "dc1". So it was not created 
by the moving.

The experiments i can do are very limited, this is a production machine. 
Any change here is done on Sundays or nighttime.

bye
Nicola









On 2/8/23 19:14, David Mulder via samba wrote:
> On 2/8/23 11:01 AM, Peter Carlson via samba wrote:
>> sorry, I need to resurrect this thread and this project.  I would 
>> really like to get this working on ubuntu server.  Brief is in email 
>> below, more details in the bug report
>>
>> What other troubleshooting steps / logging can I do to try and track 
>> down the issue.  I can set up another server, clean, and the same 
>> issue happens with it
> The strange thing here is that I'm unable to reproduce the issue. I 
> get no failures when setting up a similar environment.
>