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
On Tue, May 21, 2013 at 09:01:53 -0700, Jakub Hrozek wrote:
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.
Does this suggest a different bug - that sssd should be started before udev? If so, how should it be submitted?
On Wed, May 22, 2013 at 08:16:55PM +0000, John Bossert wrote:
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
On Tue, May 21, 2013 at 09:01:53 -0700, Jakub Hrozek wrote:
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.
Does this suggest a different bug - that sssd should be started before udev? If so, how should it be submitted?
I thought we already did that in recent RHEL versions. Lukas (CC), can you spin up a RHEL6.4 VM please and take a look?
On (23/05/13 12:58), Jakub Hrozek wrote:
On Wed, May 22, 2013 at 08:16:55PM +0000, John Bossert wrote:
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
On Tue, May 21, 2013 at 09:01:53 -0700, Jakub Hrozek wrote:
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.
Does this suggest a different bug - that sssd should be started before udev? If so, how should it be submitted?
I thought we already did that in recent RHEL versions. Lukas (CC), can you spin up a RHEL6.4 VM please and take a look?
I have bad info.
--------------------------------------- # #After reboot # [root@vm-079 ~]# service sssd status sssd (pid 1216) is running...
[root@vm-079 ~]# uname -a Linux vm-079.idm.lab.com 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@vm-079 ~]# chkconfig --list sssd sssd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@vm-079 ~]# rpm -q sssd sssd-1.9.2-82.el6.x86_64
[root@vm-079 ~]# cat /etc/issue === Cobbler installed machine ===
Red Hat Enterprise Linux Server release 6.4 (Santiago) Kernel \r on an \m
Cobbler distro: RHEL-6.4-nightly-x86_64 Installed from: 10.16.78.1 Machine is not registered to RHN. Registration script in stored in /root/rhn_register.sh
hostname: vm-079.idm.com eth0 address: 10.34.47.79/24
[root@vm-079 ~]# grep -E "(udev|sssd)" /var/log/messages May 23 14:24:02 vm-079 kernel: udev: starting version 147 May 23 14:24:02 vm-079 kernel: udev: starting version 147 May 23 14:24:03 vm-079 sssd: Starting up May 23 14:24:03 vm-079 sssd[be[idm.lab.eng.brq.redhat.com]]: Starting up May 23 14:24:03 vm-079 sssd[sudo]: Starting up May 23 14:24:03 vm-079 sssd[pam]: Starting up May 23 14:24:03 vm-079 sssd[nss]: Starting up May 23 14:24:03 vm-079 sssd[ssh]: Starting up May 23 14:24:04 vm-079 sssd[pac]: Starting up
LS
This suggests to me that, even in 6.4, udev is being started before sssd. If so, is this a bug? Can one of you submit it to the proper group?
On (23/05/13 12:58), Jakub Hrozek wrote:
On Wed, May 22, 2013 at 08:16:55PM +0000, John Bossert wrote:
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
On Tue, May 21, 2013 at 09:01:53 -0700, Jakub Hrozek wrote:
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.
Does this suggest a different bug - that sssd should be started before udev? If so, how should it be submitted?
I thought we already did that in recent RHEL versions. Lukas (CC), can you spin up a RHEL6.4 VM please and take a look?
I have bad info.
--------------------------------------- # #After reboot # [root@vm-079 ~]# service sssd status sssd (pid 1216) is running...
[root@vm-079 ~]# uname -a Linux vm-079.idm.lab.com 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@vm-079 ~]# chkconfig --list sssd sssd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@vm-079 ~]# rpm -q sssd sssd-1.9.2-82.el6.x86_64
[root@vm-079 ~]# cat /etc/issue === Cobbler installed machine ===
Red Hat Enterprise Linux Server release 6.4 (Santiago) Kernel
Cobbler distro: RHEL-6.4-nightly-x86_64 Installed from: 10.16.78.1 Machine is not registered to RHN. Registration script in stored in /root/rhn_register.sh
hostname: vm-079.idm.com eth0 address: 10.34.47.79/24
[root@vm-079 ~]# grep -E "(udev|sssd)" /var/log/messages
May 23 14:24:02 vm-079 kernel: udev: starting version 147 May 23 14:24:02 vm-079 kernel: udev: starting version 147 May 23 14:24:03 vm-079 sssd: Starting up May 23 14:24:03 vm-079 sssd[be[idm.lab.eng.brq.redhat.com]]: Starting up May 23 14:24:03 vm-079 sssd[sudo]: Starting up May 23 14:24:03 vm-079 sssd[pam]: Starting up May 23 14:24:03 vm-079 sssd[nss]: Starting up May 23 14:24:03 vm-079 sssd[ssh]: Starting up May 23 14:24:04 vm-079 sssd[pac]: Starting up
sssd-users@lists.fedorahosted.org