> Not sure what would cause that error message, nor have I experienced it. Looks like other people have seen it: > https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+information:+No+credentials+cache+foundI found no way to get rid of this, although everything seems to work fine. Red Hat need to push out an update to samba4 and fix bug 10604. It's highly irritating, and the workaround https://bugzilla.samba.org/show_bug.cgi?id=10604#c30 doesn't. The patch from https://bugzilla.samba.org/show_bug.cgi?id=10604#c17 does.
Am 14.09.2016 um 17:50 schrieb isdtor <isdtor at gmail.com>:> >> Not sure what would cause that error message, nor have I experienced it. Looks like other people have seen it: >> https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+information:+No+credentials+cache+found > > I found no way to get rid of this, although everything seems to work fine. > > Red Hat need to push out an update to samba4 and fix bug 10604. It's highly irritating, and the workaround https://bugzilla.samba.org/show_bug.cgi?id=10604#c30 doesn't. The patch from https://bugzilla.samba.org/show_bug.cgi?id=10604#c17 does.If you have not done so already, I would definitely report this to upstream (bugzilla.redhat.com). -- LF
On Wed, 2016-09-14 at 16:50 +0100, isdtor wrote:> > Not sure what would cause that error message, nor have I > > experienced it. Looks like other people have seen it: > > https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+wi > > th+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+informa > > tion:+No+credentials+cache+found > I found no way to get rid of this, although everything seems to work > fine. > Red Hat need to push out an update to samba4 and fix bug 10604. It's > highly irritating, and the workaround > https://bugzilla.samba.org/show_bug.cgi?id=10604#c30 doesn't. The > patch from https://bugzilla.samba.org/show_bug.cgi?id=10604#c17 does.Six months later, now on CentOS6.9, we still see the same issue - constantly logging this message. ?Server packages are all up-to-date. I find multiple reports on the Internet - but no solutions. -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA
On 05/20/2017 06:10 PM, Adam Tauno Williams wrote:> Six months later, now on CentOS6.9, we still see the same issue - > constantly logging this message. Server packages are all up-to-date. > > I find multiple reports on the Internet - but no solutions.The bug report mentioned in the message you replied to indicates that the problem was fixed in samba's master branch with this commit: https://git.samba.org/?p=samba.git;a=commit;h=4d5680e9ae531c6dc4d0a6687abe6293b5d4f4f2 That change isn't included in samba 4.4, distributed in RHEL 7 (nor 4.2 in RHEL 6), so you'll probably need to patch the software yourself, or wait for a 4.5 or newer package (which won't happen before the next point release, which is probably ~6 months away). If you're a customer, you can also file a bug report and request that specific patch be reviewed as an enhancement for a future release.