On Tue, Sep 12, 2017 at 06:06:19PM +0100, John Beranek wrote:
> On 12 September 2017 at 18:03, John Beranek wrote:
> > On 12 September 2017 at 17:59, John Beranek wrote:
> >> On 11 September 2017 at 14:28, Jakub Hrozek wrote:
> >>> On Mon, Sep 11, 2017 at 12:23:26PM +0100, John Beranek wrote:
> >>>
On 12 September 2017 at 18:03, John Beranek wrote:
> On 12 September 2017 at 17:59, John Beranek wrote:
>> On 11 September 2017 at 14:28, Jakub Hrozek wrote:
>>> On Mon, Sep 11, 2017 at 12:23:26PM +0100, John Beranek wrote:
>>> The issue is here:
>> [snip]
>>>
>>> So this is a known bug where locat
On 12 September 2017 at 17:59, John Beranek wrote:
> On 11 September 2017 at 14:28, Jakub Hrozek wrote:
>> On Mon, Sep 11, 2017 at 12:23:26PM +0100, John Beranek wrote:
>>> On 1 September 2017 at 15:54, Lukas Slebodnik wrote:
>>> >
>>> > On (01/09/17 09:33), William Edsall wrote:
>>> > >Had a few c
On 11 September 2017 at 14:28, Jakub Hrozek wrote:
> On Mon, Sep 11, 2017 at 12:23:26PM +0100, John Beranek wrote:
>> On 1 September 2017 at 15:54, Lukas Slebodnik wrote:
>> >
>> > On (01/09/17 09:33), William Edsall wrote:
>> > >Had a few communications with Michal but we're still stuck.
>> > >
>>
On Mon, Sep 11, 2017 at 12:23:26PM +0100, John Beranek wrote:
> On 1 September 2017 at 15:54, Lukas Slebodnik wrote:
> >
> > On (01/09/17 09:33), William Edsall wrote:
> > >Had a few communications with Michal but we're still stuck.
> > >
> > >One issue is that we have dozens of domain controllers
On 11 September 2017 at 12:23, John Beranek wrote:
> On 1 September 2017 at 15:54, Lukas Slebodnik wrote:
>>
>> On (01/09/17 09:33), William Edsall wrote:
>> >Had a few communications with Michal but we're still stuck.
>> >
>> >One issue is that we have dozens of domain controllers globally. A st
On 1 September 2017 at 15:54, Lukas Slebodnik wrote:
>
> On (01/09/17 09:33), William Edsall wrote:
> >Had a few communications with Michal but we're still stuck.
> >
> >One issue is that we have dozens of domain controllers globally. A standard
> >dns lookup could give me a domain controller over
On (01/09/17 09:33), William Edsall wrote:
>Had a few communications with Michal but we're still stuck.
>
>One issue is that we have dozens of domain controllers globally. A standard
>dns lookup could give me a domain controller overseas which will be slow,
>or maybe even a domain controller that i
Sorry, I accidentally did not reply to the list, so, for others,
see the message below.
Michal
On 09/01/2017 04:15 PM, Michal Židek wrote:
Hi again!
See comments inline...
On 09/01/2017 03:33 PM, William Edsall wrote:
Had a few communications with Michal but we're still stuck.
One issue is
Had a few communications with Michal but we're still stuck.
One issue is that we have dozens of domain controllers globally. A standard
dns lookup could give me a domain controller overseas which will be slow,
or maybe even a domain controller that isn't responding. As such, I have
been inserting
Replied directly with updated logs. There was a DNS issue caused by myself
during a frenzy of testing.
On Thu, Aug 31, 2017 at 10:47 AM, Michal Židek wrote:
> I have the important part of logs now :)
>
> Looking at the domain logs, this looks like a DNS or networking issue.
> Are you sure you ca
I have the important part of logs now :)
Looking at the domain logs, this looks like a DNS or networking issue.
Are you sure you can resolve the EXAMPLE.EXAMPLE.COM from the machine
with SSSD?
(Thu Aug 31 09:16:17 2017) [sssd[be[example.com]]]
[fo_resolve_service_done] (0x0020): Failed to resol
I forgot to say one think. You can sanitize the logs, but please
sent the whole logs (not just parts) for the sssd_domain and
sssd_nss logs (maybe you actually did this, but as I said,
I do not see the mail with the attachment).
Michal
On 08/31/2017 04:31 PM, Michal Židek wrote:
Hi,
I do not s
Hi,
I do not see the email where you sent the logs as attachment.
Maybe it is stuck in moderation (maybe the attachment was too big
or something). I only noticed you sent something thanks to your
last message. Can you please sent the logs directly to me?
If the logs are too big, It will help if
Further testing I think user1 may have been cached all along. I was not
clearing cache while sssd was stopped.
After stopping, clearing, starting - id user1 hangs. I then add ad_server
and debug_level to sssd.conf and restart it. I can now id user1 but I
believe it's coming from cache.
On Thu, Au
On 08/30/2017 09:49 PM, William Edsall wrote:
Hello list,
I've configured sssd on Centos 7 with the very basics. I'm able to id
my own user account, which was used to join the domain (via realm), but
unable to id any other account.
Does anything make sense about this? I should mention this
16 matches
Mail list logo
