16:40:31 - Group christianw85 cannot be updated again
16:40:24 - Last updated: Cannot detect last update time 16:40:24 - IP address is detected automatically 16:40:24 - Checking interval: 5 minutes 16:40:24 - Connected using: Local Area Network 16:35:16 - Update result: error no update 16:35:16 - christianw85 : notfqdn (A Fully-Qualified Domain Name was not provided) 16:35:09 - Update result: error no update 16:35:09 - christianw85 : notfqdn (A Fully-Qualified Domain Name was not provided) 16:34:45 - Update result: error no update 16:34:44 - christianw85 : notfqdn (A Fully-Qualified Domain Name was not provided) 16:34:36 - Update result: error no update 16:34:36 - christianw85 : notfqdn (A Fully-Qualified Domain Name was not provided) 16:32:45 - Last updated: Cannot detect last update time 16:32:45 - IP address is detected automatically 16:32:45 - Checking interval: Not applicable 16:32:45 - Connected using: Local Area Network Jan 23 10:20:33 .local sssd]: Backend is offlineĮrror is back and at some time even later checking the groups for the user is back to the old hab mir grade mal DynDNS eingerichtet aber beim DynDNS Updater bekomm ich immer denn fehler "error no update" was hab ich da nun wieder falsch gemacht lol.ĭynDNS Updater - Version 3.1.0 (Build 9) log file. Yet even then, after some time, when checking again I see that the Jan 23 10:19:05 .local systemd: Started System Security Services Daemon.Īnd checking the groups for a given user shows the updated groups being correctly associated with the user. Jan 23 10:18:54 .local sssd]: Starting up Jan 23 10:18:54 .local systemd: Starting System Security Services Daemon. └─98656 /usr/libexec/sssd/sssd_pam -uid 0 -gid 0 -logger=files ├─98655 /usr/libexec/sssd/sssd_nss -uid 0 -gid 0 -logger=files
├─98654 /usr/libexec/sssd/sssd_be -domain co.local -uid 0 -gid 0 -logger=files Then after restarting the service, see datalake]# systemctl status sssdĪctive: active (running) since Thu 10:19:05 HST 15s ago
Jan 22 12:56:50 .local sssd]: Backend is offline Jan 22 12:55:22 .local systemd: Started System Security Services Daemon. Jan 22 12:55:17 .local sssd]: Starting up Jan 22 12:55:17 .local systemd: Starting System Security Services Daemon. └─95840 /usr/libexec/sssd/sssd_pam -uid 0 -gid 0 -logger=files ├─95839 /usr/libexec/sssd/sssd_nss -uid 0 -gid 0 -logger=files ├─95838 /usr/libexec/sssd/sssd_be -domain co.local -uid 0 -gid 0 -logger=files Note that we recently changed our primary DNS server and the /etc/nf file does reflect these changes, but I suspect that this is very related.ĭoes anyone with more experience with SSSD have any debugging tips or know what could be going wrong here?Īfter checking a server where the DNS was not updated (rather the server is using the secondary DNS), when initially checking sssd status I see datalake]# systemctl status sssdĪctive: active (running) since Wed 12:55:22 HST 21h ago Realmd_tags = manages-system joined-with-samba Hint: Some lines were ellipsized, use -l to show in full.įor further reference, the server's /etc/sssd/nf file looks like. Jan 21 16:00:40 .local sssd]: Warning: user would have been denie. Jan 21 15:54:15 .local sssd: update failed: REFUSED Jan 21 15:54:15 .local sssd: TSIG error with server: tsig verify failure Jan 21 15:54:14 .local systemd: Started System Security Services Daemon. Jan 21 15:54:14 .local sssd_be: GSSAPI client step 2 Jan 21 15:54:14 .local sssd_be: GSSAPI client step 1 └─87113 /usr/libexec/sssd/sssd_pam -uid 0 -gid 0 -logger=files ├─87112 /usr/libexec/sssd/sssd_nss -uid 0 -gid 0 -logger=files ├─87111 /usr/libexec/sssd/sssd_be -domain co.local -uid 0 -gid 0 -logger=files Loaded: loaded (/usr/lib/systemd/system/rvice enabled vendor preset: disabled)Īctive: active (running) since Tue 15:54:14 HST 9min ago rvice - System Security Services Daemon.After adding a user to a group in Active Directory and looking for that group to appear with the user on a linux server linked to AD via SSSD, noticing that the group is not added to the user (even after restarting the sssd service).Ĭhecking the SSSD daemon status, I see.