Sorry for leaving out specifics.
$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd -version 1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/20/2013 12:50 PM, John Bossert wrote:
Sorry for leaving out specifics.
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd –version
1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
Could you try pulling down the version of SSSD that was released in RHEL 6.2 (it should be SSSD 1.9.2). This may fix your issue.
On 05/20/2013 02:15 PM, Stephen Gallagher wrote:
On 05/20/2013 12:50 PM, John Bossert wrote:
Sorry for leaving out specifics.
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd –version
1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
Could you try pulling down the version of SSSD that was released in RHEL 6.2 (it should be SSSD 1.9.2). This may fix your issue.
Did you mean 6.4?
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/20/2013 02:20 PM, Dmitri Pal wrote:
On 05/20/2013 02:15 PM, Stephen Gallagher wrote:
On 05/20/2013 12:50 PM, John Bossert wrote:
Sorry for leaving out specifics.
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd –version
1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
Could you try pulling down the version of SSSD that was released in RHEL 6.2 (it should be SSSD 1.9.2). This may fix your issue.
Did you mean 6.4?
Yes, I meant 6.4. Sorry for the embarrassing typo.
On Mon, May 20, 2013 at 04:50:28PM +0000, John Bossert wrote:
Sorry for leaving out specifics.
$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd -version 1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
Does SSSD start before or after udev? I think it would be OK to start it before udev even if it was before network because SSSD would pick up networking change on its own and switch to online mode automatically.
/var/log/messages suggests that udev starts before sssd:
May 17 16:54:07 seadv01-db01 kernel: udev: starting version 147 May 17 16:54:09 seadv01-db01 sssd: Starting up
On Mon, May 20, 2013 at 04:50:28PM +0000, John Bossert wrote:
Sorry for leaving out specifics.
$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.3 (Santiago)
$ sssd -version 1.8.0
The problem is that, during boot, udev is not correctly executing a rule to set user/group ownership, where the target user and group are maintained (exclusively) in LDAP. If, after boot, I re-execute start_udev, all works as expected.
Does SSSD start before or after udev? I think it would be OK to start it before udev even if it was before network because SSSD would pick up networking change on its own and switch to online mode automatically.
On Mon, May 20, 2013 at 08:59:28PM +0000, John Bossert wrote:
/var/log/messages suggests that udev starts before sssd:
May 17 16:54:07 seadv01-db01 kernel: udev: starting version 147 May 17 16:54:09 seadv01-db01 sssd: Starting up
I haven't found the bug Stephen was referring to (though I remember there was one as well) but if udev needs a remote user, then it should be starting after the SSSD.
sssd-users@lists.fedorahosted.org
-
Dmitri Pal -
Jakub Hrozek -
John Bossert -
Stephen Gallagher