[Samba] Confiming Logs are "Normal"

Andrew Bartlett abartlet at samba.org
Wed Jan 26 22:01:44 UTC 2022


On Wed, 2022-01-26 at 16:47 -0500, ralph strebbing via samba wrote:
> Hi All,
> 
> So following an article to enable User Identification on our
> PaloAlto,
> I'm noticing some new logs in syslog, notably:
> Jan 26 16:43:26 dc2 sh[3158324]: lpcfg_do_global_parameter: WARNING:
> The "syslog" option is deprecated
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'gssapi_spnego'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'gssapi_krb5'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'gssapi_krb5_sasl'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'spnego' registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'schannel' registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'naclrpc_as_system'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'sasl-EXTERNAL'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'ntlmssp' registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend
> 'ntlmssp_resume_ccache' registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'http_basic'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'http_ntlm'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'http_negotiate'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'krb5' registered
> Jan 26 16:43:26 dc2 sh[3158324]: GENSEC backend 'fake_gssapi_krb5'
> registered
> Jan 26 16:43:26 dc2 sh[3158324]: Using binding
> ncacn_ip_tcp:dc2[,sign]
> Jan 26 16:43:26 dc2 sh[3158324]: resolve_lmhosts: Attempting lmhosts
> lookup for name dc2<0x20>
> Jan 26 16:43:26 dc2 sh[3158324]: resolve_lmhosts: Attempting lmhosts
> lookup for name dc2<0x20>
> 
> I understand the syslog option on smb.conf is deprecated, in this
> instance, what should I do to still route these to the remote syslog
> server?
> As for the GENSEC entries and the "resolve_lmhosts" entries, are
> those
> normal? Do they indicate any issues?

I think you simply have the log level turned up too high in something,
perhaps a command line tool.  These are very low level debugging
messages, and are harmless.

Andrew Bartlett

-- 
Andrew Bartlett (he/him)       https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba

Samba Development and Support, Catalyst IT - Expert Open Source
Solutions








More information about the samba mailing list