[Bug 280781] net/samba419 - winbindd does not start
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 12 Aug 2024 16:54:44 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280781 Bug ID: 280781 Summary: net/samba419 - winbindd does not start Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: mikael@FreeBSD.org Reporter: byrnejb@harte-lyne.ca Assignee: mikael@FreeBSD.org Flags: maintainer-feedback?(mikael@FreeBSD.org) Created attachment 252714 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252714&action=edit samba4 configuration file The winbindd daemon does not start when spawned by samba_server: [2024/08/09 16:03:15.095245, 0] ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) Got sig[15] terminate (is_parent=0) When run interactively the program gives this output: # /usr/local/sbin/winbindd -d 15 -i INFO: Current debug levels: all: 15 tdb: 15 printdrivers: 15 lanman: 15 smb: 15 rpc_parse: 15 rpc_srv: 15 rpc_cli: 15 passdb: 15 sam: 15 locking: 15 msdfs: 15 dmapi: 15 registry: 15 scavenger: 15 dns: 15 ldb: 15 tevent: 15 auth_audit: 15 auth_json_audit: 15 kerberos: 15 drs_repl: 15 smb2: 15 smb2_credits: 15 dsdb_audit: 15 dsdb_json_audit: 15 dsdb_password_audit: 15 dsdb_password_json_audit: 15 dsdb_transaction_audit: 15 dsdb_transaction_json_audit: 15 dsdb_group_audit: 15 dsdb_group_json_audit: 15 lp_load_ex: refreshing parameters Initialising global parameters INFO: Current debug levels: all: 15 tdb: 15 printdrivers: 15 lanman: 15 smb: 15 rpc_parse: 15 rpc_srv: 15 rpc_cli: 15 passdb: 15 sam: 15 auth: 15 winbind: 15 vfs: 15 idmap: 15 quota: 15 acls: 15 locking: 15 msdfs: 15 dmapi: 15 registry: 15 scavenger: 15 dns: 15 ldb: 15 tevent: 15 auth_audit: 15 auth_json_audit: 15 kerberos: 15 drs_repl: 15 smb2: 15 smb2_credits: 15 dsdb_audit: 15 dsdb_json_audit: 15 dsdb_password_audit: 15 dsdb_password_json_audit: 15 dsdb_transaction_audit: 15 dsdb_transaction_json_audit: 15 dsdb_group_audit: 15 dsdb_group_json_audit: 15 Processing section "[global]" doing parameter netbios name = SMB4-2 doing parameter disable netbios = yes doing parameter interfaces = em1, 192.168.216.164/16 doing parameter realm = BROCKLEY.HARTE-LYNE.CA doing parameter server role = active directory domain controller doing parameter workgroup = BROCKLEY doing parameter idmap_ldb:use rfc2307 = yes doing parameter vfs objects = acl_xattr dfs_samba4 zfsacl doing parameter socket options = TCP_NODELAY SO_KEEPALIVE doing parameter bind interfaces only = Yes doing parameter interfaces = localhost em1 doing parameter dns forwarder = 216.185.71.33 216.185.71.34 doing parameter dns update command = /usr/local/sbin/samba_dnsupdate doing parameter nsupdate command = /usr/local/bin/samba-nsupdate## Global parameters doing parameter allow dns updates = nonsecure doing parameter log level = 1 doing parameter log file = /var/log/samba4/smbd.log doing parameter max log size = 10000 doing parameter debug timestamp = yes doing parameter load printers = no doing parameter printing = bsd doing parameter printcap name = /dev/null doing parameter disable spoolss = yes vfs objects specified with all required AD DC modules pm_process() returned Yes lp_servicenumber: 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|--version] As an aside, the error respecting interactive mode is either wrong or misleading. In the first instance the -S option is not supported. In the second instance the -i option is passed on the command line. -- You are receiving this mail because: You are the assignee for the bug.