[SSSD] testing dyndns_update

Jakub Hrozek jhrozek at redhat.com
Thu May 9 11:37:37 UTC 2013


On Thu, May 09, 2013 at 12:00:46PM +0200, steve wrote:
> On 09/05/13 11:26, Jakub Hrozek wrote:
> >On Thu, May 09, 2013 at 08:34:50AM +0200, steve wrote:
> >>On 08/05/13 23:53, Lukas Slebodnik wrote:
> >>>On (08/05/13 22:46), steve wrote:
> >>>>Hi
> >>>>We have 1.10.0beta1 on lubuntu 13.04
> >>>>
> >>>>We have added
> >>>>dyndns_update=true
> >>>>dyndns_refresh=1
> >>>>to sssd.conf
> >>>>
> >>>>We expect to see an update request after 1 minute, but nothing
> >>>>happens. Are we correct to expect this behaviour?
> >>>>
> >>>>Cheers,
> >>>>Steve
> >>>
> >>> From manual page "sssd-ad"
> >>>
> >>>        dyndns_refresh_interval (integer)
> >>>            How often should the back end perform periodic DNS update in
> >>>            addition to the automatic update performed when the back end
> >>>            goes online. This option is optional and applicable only
> >>>            when dyndns_update is true.
> >>>
> >>>            Default: 86400 (24 hours)
> >>>
> >>>It is not explicitelly written, but you could noticed,
> >>>that default value is in seconds. (86400 seconds == 24 hours)
> >>>
> >>Hi. Thanks. I changed it to:
> >>dyndns_update=true
> >>dyndns_refresh=60
> >>
> >>No DNS request is made. We have a Samba4 dc which accepts dns
> >>requests from the windows clients so it seems to be working. I have
> >>set the log level to 6 but nothing gets logged. I'm looking in:
> >>/usr/local/var/log/sssd, /var/log/sssd
> >>
> >>It's starting OK and getent and user logins work fine, just not the
> >>dns update requests.
> >>sudo sssd -i -d3
> >>(Thu May  9 08:25:32 2013) [sssd[be[default]]]
> >>[sssm_simple_access_init] (0x0040): No rules supplied for simple
> >>access provider. Access will be granted for all users.
> >>(Thu May  9 08:25:32 2013) [sssd[be[default]]] [be_process_init]
> >>(0x0080): No SUDO module provided for [default] !!
> >>(Thu May  9 08:25:32 2013) [sssd[be[default]]] [be_process_init]
> >>(0x0020): No selinux module provided for [default] !!
> >>(Thu May  9 08:25:32 2013) [sssd[be[default]]] [be_process_init]
> >>(0x0020): No host info module provided for [default] !!
> >>(Thu May  9 08:25:32 2013) [sssd[be[default]]] [be_process_init]
> >>(0x0020): Subdomains are not supported for [default] !!
> >>
> >>Here is our sssd.conf. What are we missing to be able to trigger the
> >>dns update requests?
> >>[sssd]
> >>debug_level = 6
> >>services = nss, pam
> >>config_file_version = 2
> >>domains = default
> >>
> >>[nss]
> >>
> >>[pam]
> >>
> >>[domain/default]
> >>debug_level=6
> >>dyndns_update=true
> >>dyndns_refresh_interval=60
> >>ldap_schema = rfc2307bis
> >>access_provider = simple
> >>enumerate = FALSE
> >>cache_credentials = true
> >>#entry_cache_timeout = 60
> >>id_provider = ldap
> >
> >^^^^
> >
> >Currently the dyndns updates are only supported with id_provider=ad or
> >id_provider=ipa
> >
> >Since you're using the POSIX attributes, you'd want to configure a
> >domain similar to:
> >
> >id_provider = ad
> >ad_server = hh16.hh3.site
> >ad_domain = HH3.SITE
> >ldap_id_mapping = False
> >
> 
> Hi
> OK. Changed that but then sssd crashes after the first DNS update
> and no update is performed:
>  sudo sssd -i -d3
> (Thu May  9 11:55:25 2013) [sssd[be[default]]]
> [sssm_simple_access_init] (0x0040): No rules supplied for simple
> access provider. Access will be granted for all users.
> (Thu May  9 11:55:25 2013) [sssd[be[default]]] [be_process_init]
> (0x0080): No SUDO module provided for [default] !!
> (Thu May  9 11:55:25 2013) [sssd[be[default]]] [be_process_init]
> (0x0080): No autofs module provided for [default] !!
> (Thu May  9 11:55:25 2013) [sssd[be[default]]] [be_process_init]
> (0x0020): No selinux module provided for [default] !!
> (Thu May  9 11:55:25 2013) [sssd[be[default]]] [be_process_init]
> (0x0020): No host info module provided for [default] !!
> (Thu May  9 11:55:25 2013) [sssd[be[default]]] [be_process_init]
> (0x0020): Subdomains are not supported for [default] !!
> (Thu May  9 11:55:41 2013) [sssd[be[default]]] [be_run_online_cb]
> (0x0080): Going online. Running callbacks.
> (Thu May  9 11:55:41 2013) [sssd[be[default]]]
> [ad_dyndns_nsupdate_done] (0x0040): DNS update finished
> (Thu May  9 11:55:43 2013) [sssd[be[default]]]
> [resolv_gethostbyname_done] (0x0040): querying hosts database failed
> [5]: Error de entrada/salida
> (Thu May  9 11:55:43 2013) [sssd[be[default]]]
> [nsupdate_get_addrs_done] (0x0040): Could not resolve address for
> this machine, error [5]: Error de entrada/salida, resolver returned:
> [11]: Could not contact DNS servers
> (Thu May  9 11:55:43 2013) [sssd[be[default]]]
> [nsupdate_get_addrs_done] (0x0040): (Thu May  9 11:55:44 2013)
> [sssd] [sbus_dispatch] (0x0080): Connection is not open for
> dispatching.
> (Thu May  9 11:55:44 2013) [sssd[nss]] [sbus_dispatch] (0x0020):
> Performing auto-reconnect
> (Thu May  9 11:55:44 2013) [sssd[pam]] [sbus_dispatch] (0x0020):
> Performing auto-reconnect
> (Thu May  9 11:55:44 2013) [sssd] [mt_svc_exit_handler] (0x0040):
> Child [default] terminated with signal [11]

Oof, I suspect we don't handle the situation where we can't get the
machine host name well:
https://fedorahosted.org/sssd/ticket/1913

Can you get us a backtrace, please?



More information about the sssd-devel mailing list