Zombie Ryushu
2022-Jun-16 14:36 UTC
[Samba] Samba's winbindd is running but seems non-functional.
I have issues with what seems to be an entitrely non-functional Winbindd. This seems to be the source of my problem. Details below: 02:32:42 AM) Codebase: codebase at olympia:~> wbinfo -D PUKEY failed to call wbcDomainInfo: WBC_ERR_NOT_IMPLEMENTED Could not get domain info codebase at olympia:~> wbinfo -P checking the NETLOGON for domain[-not available-] dc connection to "" failed failed to call wbcPingDc: WBC_ERR_NOT_IMPLEMENTED codebase at olympia:~> wbinfo --all-domains failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED codebase at olympia:~> wbinfo --online-status failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED Could not show online-status codebase at olympia:~> wbinfo --own-domain -not available- codebase at olympia:~> wbinfo --trusted-domains failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED Could not list trusted domains (02:33:05 AM) Codebase: This is acting as if winbind isn't configured. (02:33:23 AM) Codebase: (I.e. It claims not to be a part of a domain.) (02:33:25 AM) masterz at olympia.pukey/Olympia: masterz at kefka:~> wbinfo --all-domains BUILTIN PUKEY-NT (02:33:35 AM) Codebase: codebase at olympia:~> wbinfo --own-domain -not available- (02:33:45 AM) Codebase: codebase at olympia:~> wbinfo --all-domains failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED (02:33:58 AM) masterz at olympia.pukey/Olympia: masterz at kefka:~> wbinfo --own-domain PUKEY-NT (02:34:32 AM) Codebase: That's making me wonder if winbind's components are damaged. (02:34:45 AM) masterz at olympia.pukey/Olympia: masterz at kefka:~> wbinfo --online-status BUILTIN : active connection PUKEY-NT : active connection (02:36:13 AM) Codebase: There was a time when sssd overrode winbind's libraries. Instead of using the plugin mechanism that exists today. Most distros would use their alternatives mechisim (or package manager) to select between them. (02:36:54 AM) Codebase: Could opensuse be doing something similar here? (02:37:18 AM) Codebase: Replacing the winbind library with sssd's version? (02:38:47 AM) Codebase: I ask because sssd's version was barebones. If that was the problem, we'd get unimplemented method errors. (02:39:30 AM) masterz at olympia.pukey/Olympia: olympia:~ # rpm -q --verify samba-winbind-libs olympia:~ # rpm -q --verify samba-winbind (02:42:07 AM) Codebase: Do you have a working avahi server enabled on your network? (02:42:38 AM) Codebase: Because this is in olympia's nsswitch.conf: hosts: files mdns_minimal [NOTFOUND=return] dns (02:42:54 AM) Codebase: It will never query DNS for a hostname. (02:43:04 AM) Codebase: With that config. (02:43:16 AM) masterz at olympia.pukey/Olympia: sudo service avahi-daemon status ***avahi-daemon.service - Avahi mDNS/DNS-SD Stack ????Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset> ????Active: *active (running)*since Thu 2022-06-16 01:54:35 EDT; 48min ago (02:43:50 AM) Codebase: I should also point out that it will not have the SRV records that samba needs for ADDC support. (02:44:12 AM) Codebase: Which means that lookups for the DC and GC will fail. (02:44:18 AM) masterz at olympia.pukey/Olympia: Bind DLZ Provides that. (02:44:22 AM) Codebase: Yes. (02:44:23 AM) masterz at olympia.pukey/Olympia: check. How do I debug Winbindd's behavior?
Jeremy Allison
2022-Jun-17 22:09 UTC
[Samba] Samba's winbindd is running but seems non-functional.
On Thu, Jun 16, 2022 at 10:36:40AM -0400, Zombie Ryushu via samba wrote:>I have issues with what seems to be an entitrely non-functional >Winbindd. This seems to be the source of my problem. Details below: > >02:32:42 AM) Codebase: codebase at olympia:~> wbinfo -D PUKEY >failed to call wbcDomainInfo: WBC_ERR_NOT_IMPLEMENTED >Could not get domain info >codebase at olympia:~> wbinfo -P >checking the NETLOGON for domain[-not available-] dc connection to "" failed >failed to call wbcPingDc: WBC_ERR_NOT_IMPLEMENTED >codebase at olympia:~> wbinfo --all-domains >failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED >codebase at olympia:~> wbinfo --online-status >failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED >Could not show online-status >codebase at olympia:~> wbinfo --own-domain >-not available- >codebase at olympia:~> wbinfo --trusted-domains >failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED >Could not list trusted domains >(02:33:05 AM) Codebase: This is acting as if winbind isn't configured. >(02:33:23 AM) Codebase: (I.e. It claims not to be a part of a domain.) >(02:33:25 AM) masterz at olympia.pukey/Olympia: masterz at kefka:~> wbinfo >--all-domains >BUILTIN >PUKEY-NT > >(02:33:35 AM) Codebase: codebase at olympia:~> wbinfo --own-domain >-not available- >(02:33:45 AM) Codebase: codebase at olympia:~> wbinfo --all-domains >failed to call wbcListTrusts: WBC_ERR_NOT_IMPLEMENTED >(02:33:58 AM) masterz at olympia.pukey/Olympia: masterz at kefka:~> wbinfo >--own-domain >PUKEY-NT > >(02:34:32 AM) Codebase: That's making me wonder if winbind's >components are damaged.Getting this return WBC_ERR_NOT_IMPLEMENTED seems to imply a miss-match between components somehow.