Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba:> OK, try this, open a terminal, type 'winbindd -i' > This should directly run winbind in the terminal, hopefully if it fails > it will print an error message, if not try again but add '-d3'main ~ # winbindd -i -d3 Maximum core file size limits now 16777216(soft) -1(hard) winbindd version 4.2.14 started. Copyright Andrew Tridgell and the Samba Team 1992-2014 lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" Maximum core file size limits now 16777216(soft) -1(hard) Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" added interface br0 ip=10.0.0.221 bcast=10.0.0.255 netmask=255.255.255.0 added interface br0 ip=10.0.0.221 bcast=10.0.0.255 netmask=255.255.255.0 initialize_winbindd_cache: clearing cache and re-creating with version number 2 Added domain BUILTIN (null) S-1-5-32 Added domain MAIN (null) S-1-5-21-2777655458-4002997014-749295002 PANIC (pid 3155): Could not find our domain BACKTRACE: 12 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fc11e4ac7aa] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fc11e4ac890] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7fc1211560df] #3 winbindd(+0x36623) [0x55d385353623] #4 winbindd(rescan_trusted_domains+0x1d) [0x55d38535364d] #5 /usr/lib64/libtevent.so.0(tevent_common_loop_timer_delay+0xcd) [0x7fc11b66ab0d] #6 /usr/lib64/libtevent.so.0(+0x9b0a) [0x7fc11b66bb0a] #7 /usr/lib64/libtevent.so.0(+0x8227) [0x7fc11b66a227] #8 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fc11b66646d] #9 winbindd(main+0xb7c) [0x55d3853424cc] #10 /lib64/libc.so.6(__libc_start_main+0xf0) [0x7fc11b09c620] #11 winbindd(_start+0x29) [0x55d385342b59] dumping core in /var/log/samba/cores/winbindd Abgebrochen
got to leave here, can look up in 1-2hrs again from home office
question:
could it be that some old cruft in /var/lib/samba bites here?
how to get rid of that? rm-ing it completely messed up joining (tried
that before), so it seems I have to clean up some files only.
remember: server "main" was nt4-pdc ~~ and we only replaced smb.conf
and
joined etc etc // maybe too bold? ;-)
main samba # tree /var/lib/samba/
/var/lib/samba/
├── account_policy.tdb
├── browse.dat
├── group_mapping.tdb
├── netlogon
│ └── logon.bat
├── perfmon
├── printing
├── private
│ ├── netlogon_creds_cli.tdb
│ ├── passdb.tdb
│ ├── schannel_store.tdb
│ ├── secrets.tdb
│ ├── smbd.tmp
│ │ └── msg
│ │ ├── msg.3250
│ │ ├── msg.3262
│ │ └── names.tdb
│ └── smbpasswd
├── registry.tdb
├── share_info.tdb
├── var
│ └── lib
│ └── samba
├── winbindd_cache.tdb
└── winbindd_privileged
└── pipe
ah, btw. rm-ing winbindd_cache.tdb did not help winbindd either.
bye for now
On Fri, 30 Dec 2016 17:55:58 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:> Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba: > > > OK, try this, open a terminal, type 'winbindd -i' > > This should directly run winbind in the terminal, hopefully if it > > fails it will print an error message, if not try again but add '-d3' > > > main ~ # winbindd -i -d3 > Maximum core file size limits now 16777216(soft) -1(hard) > winbindd version 4.2.14 started. > Copyright Andrew Tridgell and the Samba Team 1992-2014 > lp_load_ex: refreshing parameters > Initialising global parameters > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) Processing section "[global]" > Maximum core file size limits now 16777216(soft) -1(hard) > Registered MSG_REQ_POOL_USAGE > Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED > lp_load_ex: refreshing parameters > Initialising global parameters > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) Processing section "[global]" > added interface br0 ip=10.0.0.221 bcast=10.0.0.255 > netmask=255.255.255.0 added interface br0 ip=10.0.0.221 > bcast=10.0.0.255 netmask=255.255.255.0 initialize_winbindd_cache: > clearing cache and re-creating with version number 2 > Added domain BUILTIN (null) S-1-5-32 > Added domain MAIN (null) S-1-5-21-2777655458-4002997014-749295002 > PANIC (pid 3155): Could not find our domain > BACKTRACE: 12 stack frames: > #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fc11e4ac7aa] > #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fc11e4ac890] > #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7fc1211560df] > #3 winbindd(+0x36623) [0x55d385353623] > #4 winbindd(rescan_trusted_domains+0x1d) [0x55d38535364d] > #5 /usr/lib64/libtevent.so.0(tevent_common_loop_timer_delay+0xcd) > [0x7fc11b66ab0d] > #6 /usr/lib64/libtevent.so.0(+0x9b0a) [0x7fc11b66bb0a] > #7 /usr/lib64/libtevent.so.0(+0x8227) [0x7fc11b66a227] > #8 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) > [0x7fc11b66646d] #9 winbindd(main+0xb7c) [0x55d3853424cc] > #10 /lib64/libc.so.6(__libc_start_main+0xf0) [0x7fc11b09c620] > #11 winbindd(_start+0x29) [0x55d385342b59] > dumping core in /var/log/samba/cores/winbindd > Abgebrochen > >From that I see you are using Samba 4.2.14 , is there a possibility of two smb.conf files or other duplicate Samba binaries ? Have installed all the required dependencies, see here: https://wiki.samba.org/index.php/Samba_Dependencies_Required_to_Build_Samba What is happening is that when winbind is started, it adds the 'BUILTIN' domain, then the local 'MAIN' domain, it then panics when it tries to add the AD domain. All I can suggest is double checking you have all the dependencies installed to build Samba on gentoo. Rowland
On Fri, 30 Dec 2016 18:11:14 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:> > got to leave here, can look up in 1-2hrs again from home office > > question: > could it be that some old cruft in /var/lib/samba bites here? > how to get rid of that? rm-ing it completely messed up joining (tried > that before), so it seems I have to clean up some files only. > > remember: server "main" was nt4-pdc ~~ and we only replaced smb.conf > and joined etc etc // maybe too bold? ;-)Oh definitely, you will probably have to empty /var/lib/samba and then let Samba fill it up again. Rowland
On Fri, Dec 30, 2016 at 05:55:58PM +0100, Stefan G. Weichinger via samba wrote:> Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba: > > >OK, try this, open a terminal, type 'winbindd -i' > >This should directly run winbind in the terminal, hopefully if it fails > >it will print an error message, if not try again but add '-d3' > > > main ~ # winbindd -i -d3-d10 please :-) Volker
On Fri, 30 Dec 2016 18:53:22 +0100 Volker Lendecke via samba <samba at lists.samba.org> wrote:> On Fri, Dec 30, 2016 at 05:55:58PM +0100, Stefan G. Weichinger via > samba wrote: > > Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba: > > > > >OK, try this, open a terminal, type 'winbindd -i' > > >This should directly run winbind in the terminal, hopefully if it > > >fails it will print an error message, if not try again but add > > >'-d3' > > > > > > main ~ # winbindd -i -d3 > > -d10 please :-) > > Volker >I would have worked up to that ;-) But the OP has since posted that he just changed the smb.conf on his old PDC and didn't empty /var/lib/samba Rowland
Will do, currently out of office. Thanks, looking forward. Am 30. Dezember 2016 18:53:22 MEZ schrieb Volker Lendecke <vl at samba.org>:>On Fri, Dec 30, 2016 at 05:55:58PM +0100, Stefan G. Weichinger via >samba wrote: >> Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba: >> >> >OK, try this, open a terminal, type 'winbindd -i' >> >This should directly run winbind in the terminal, hopefully if it >fails >> >it will print an error message, if not try again but add '-d3' >> >> >> main ~ # winbindd -i -d3 > >-d10 please :-) > >Volker-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.