Ondrej,
If your switch port is an end-port, just have the Cisco network admin
configure "portfast" for the port you are on. This should fix your issue.
Best,
Frank Pikelner
On Thu, Sep 15, 2016 at 5:21 AM, Ondrej Valousek <
ondrej.valou...@s3group.com> wrote:
> Hi List,
>
>
>
> Just
On Thu, Sep 15, 2016 at 09:53:05AM +0200, Lukas Slebodnik wrote:
> https://fedorahosted.org/sssd/ticket/3017
>
> Workaround is to install the adcli package.
> http://packages.ubuntu.com/xenial/adcli
This wouldn't fix #3017 alone, it's best to also set the machine renewal
task to a very long
On Thu, Sep 15, 2016 at 03:07:07AM +, Joakim Tjernlund wrote:
> On Wed, 2016-09-14 at 10:39 +0200, Sumit Bose wrote:
> > On Tue, Sep 13, 2016 at 01:43:06PM +, Joakim Tjernlund wrote:
> > >
...
> > > >
> > >
> > > I swapped the computer to our new domain and now windbind could not find
On Thu, Sep 15, 2016 at 07:09:07AM +0200, Andreas Roth wrote:
> Hi,
>
> i've a ubuntu xenial machine here which experiences the same issue:
>
> uname -a:
> Linux fast-srv03 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC
> 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> sssd version:
On (15/09/16 07:09), Andreas Roth wrote:
>Hi,
>
>i've a ubuntu xenial machine here which experiences the same issue:
>
>uname -a:
>Linux fast-srv03 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC
>2016 x86_64 x86_64 x86_64 GNU/Linux
>
>sssd version: 1.13.4-1ubuntu1
>
>here is the output of
Hi,
i've a ubuntu xenial machine here which experiences the same issue:
uname -a:
Linux fast-srv03 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
sssd version: 1.13.4-1ubuntu1
here is the output of ls -l /proc/`pgrep sssd_be`/fd/
lrwx-- 1 root
My recollection is that finger used a terribly inefficient way of getting
information, at least one time, and asked for information on every user despite
the fact that it was only going to need one. I recall installing something
called finger-ldap, because in the pre-SSSD days, finger could
Ryan Novosielski wrote:
> My recollection is that finger used a terribly inefficient way of getting
> information, at least one time, and asked for information on every user
> despite the fact that it was only going to need one. I recall installing
> something called finger-ldap, because in the
Not likely as this is RHEL-6 machine where network service is starting before
SSSD
Looks like a bug in the network init scripts.
-Original Message-
From: Jakub Hrozek [mailto:jhro...@redhat.com]
Sent: Thursday, September 15, 2016 1:43 PM
To: sssd-users@lists.fedorahosted.org
Subject:
Hi List,
Just experiencing troubles when starting machine.
The thing is that by the time sssd starts, network is not quite ready -
sometimes Cisco switches take up to few seconds to negotiate speed, etc ->
network sysinit script already finishes (could happen if you have static IP,
right?),
True, if at least SSSD would return the cached maps, the situation would be
much better, I agree.
But still, I believe the network init script should not return until the
network is up and functional.
Ondrej
-Original Message-
From: Jakub Hrozek [mailto:jhro...@redhat.com]
Sent:
Update:
The server is connected via bonding interface.
I guess that could be the problem.
Ondrej
From: Ondrej Valousek
Sent: Thursday, September 15, 2016 11:22 AM
To: sssd-users@lists.fedorahosted.org
Subject: Network coming up slowly causing sssd to fail on startup
Hi List,
Just experiencing
If you are in trusty cross realm, you ask for TGT your domain's DC ;
This TGT should be enough to get rights for all other domains (DC controllers
"talk" to each other and do that automagically for you)
Best,
Longina
> -Oprindelig meddelelse-
> Fra: Sumit Bose [mailto:sb...@redhat.com]
On Thu, Sep 15, 2016 at 09:28:54AM +, Ondrej Valousek wrote:
> Update:
> The server is connected via bonding interface.
> I guess that could be the problem.
> Ondrej
>
Sounds like a fix for https://fedorahosted.org/sssd/ticket/3080 might
help at least to return the autofs maps from cache.
14 matches
Mail list logo
