On Wed, Jul 03, 2013 at 10:17:19AM -0400, Michael Mercier wrote: > Hello, > > I tried to login (ssh) to one (of three) freeipa systems running on CentOS > yesterday without success. > > Running 'ssh root@service-2', the server would reply with a password prompt > and then hang. I went to the system console to discover many of the > following messages on screen: > > Jun 30 <time> service-2 kernel: INFO: task sssd_be:22447 blocked for more > than 120 seconds. > Jun 30 <time> service-2 kernel: "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > Trying to login on the console, I was able to enter and username, but the > login process would hang after entering the password. After rebooting the > system, I see the following in /var/log/messages > > Jun 30 00:29:29 service-2 kernel: INFO: task sssd_be:22447 blocked for more > than 120 seconds. > Jun 30 00:29:29 service-2 kernel: "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Jun 30 00:29:29 service-2 kernel: sssd_be D 000000000000000e 0 > 22447 3673 0x00000084 > Jun 30 00:29:29 service-2 kernel: ffff880827dffce8 0000000000000086 > 0000000000000000 0000000000000000 > Jun 30 00:29:29 service-2 kernel: 0000000000000000 0000000000000000 > 0000000000000000 0000000000000000 > Jun 30 00:29:29 service-2 kernel: ffff880827255058 ffff880827dfffd8 > 000000000000fb88 ffff880827255058 > Jun 30 00:29:29 service-2 kernel: Call Trace: > Jun 30 00:29:29 service-2 kernel: [<ffffffffa00aabf0>] ? > ext4_file_open+0x0/0x130 [ext4] > Jun 30 00:29:29 service-2 kernel: [<ffffffff8150ea85>] > schedule_timeout+0x215/0x2e0 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8117e574>] ? > nameidata_to_filp+0x54/0x70 > Jun 30 00:29:29 service-2 kernel: [<ffffffff812773c9>] ? > cpumask_next_and+0x29/0x50 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8150e703>] > wait_for_common+0x123/0x180 > Jun 30 00:29:29 service-2 kernel: [<ffffffff81063310>] ? > default_wake_function+0x0/0x20 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8150e81d>] > wait_for_completion+0x1d/0x20 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8106513c>] sched_exec+0xdc/0xe0 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8118a100>] do_execve+0xe0/0x2c0 > Jun 30 00:29:29 service-2 kernel: [<ffffffff810095ea>] sys_execve+0x4a/0x80 > Jun 30 00:29:29 service-2 kernel: [<ffffffff8100b4ca>] stub_execve+0x6a/0xc0 > > This sequence of messages is repeated many times. > > I did not have any problems logging into the other two freeipa systems on the > network. The servers are currently used exclusively for freeipa. > > Any ideas what may have happened?
do you see anything in the sssd logs in /var/log/sssd ? ext4_file_open might indicate that sssd is stuck while trying to open a file. Have you tried to run a filesystem check? bye, Sumit > > > rpm -qa | grep ipa > libipa_hbac-1.9.2-82.7.el6_4.x86_64 > ipa-admintools-3.0.0-26.el6_4.4.x86_64 > python-iniparse-0.3.1-2.1.el6.noarch > ipa-client-3.0.0-26.el6_4.4.x86_64 > ipa-server-selinux-3.0.0-26.el6_4.4.x86_64 > ipa-server-3.0.0-26.el6_4.4.x86_64 > ipa-pki-common-theme-9.0.3-7.el6.noarch > libipa_hbac-python-1.9.2-82.7.el6_4.x86_64 > ipa-python-3.0.0-26.el6_4.4.x86_64 > ipa-pki-ca-theme-9.0.3-7.el6.noarch > > > Thanks, > Mike > > _______________________________________________ > Freeipa-users mailing list > Freeipa-users@redhat.com > https://www.redhat.com/mailman/listinfo/freeipa-users _______________________________________________ Freeipa-users mailing list Freeipa-users@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-users
