Displaying 2 results from an estimated 2 matches for "ndifv".
Did you mean:
ndiff
2024 Aug 12
1
winbindd fails to start
...couldn't find homes
added interface lo0 ip=127.0.162.1 bcast=127.0.162.1 netmask=255.255.255.255
added interface em1 ip=192.168.216.164 bcast=192.168.216.164
netmask=255.255.255.255
ERROR: Can't log to stdout (-S) unless daemon is in foreground (-F) or
interactive (-i)
Usage: winbindd [-?nDiFV] [-?|--help] [--usage] [-n|--no-caching]
[-d|--debuglevel=DEBUGLEVEL] [--debug-stdout]
[-s|--configfile=CONFIGFILE] [--option=name=value]
[-l|--log-basename=LOGFILEBASE] [--leak-report] [--leak-report-full]
[-D|--daemon] [-i|--interactive] [-F|--foreground] [--no-process-group]
[-V|...
2024 Aug 09
2
winbindd fails to start
I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in the
log.wb-<DOMAIN> file:
../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler)
I suspect that this may caused by an ip4 address assignment clash as I am using
the configuration and data structures copied from our running Samba-4.13 DC.
When I run winbindd interactively I see this:
#