9:04 a.m.
Hi All,
We are having an issue performing RHEL 6.6 to 6.7 upgrade with SSSD. The
systems are already enrolled and working in IPA 3.0.0-50 using 6.6 client.
We yum update and sssd gives this
Non-fatal POSTTRANS scriptlet failure in rpm package
sssd-1.12.4-47.el6_7.8.ppc64
warning: %posttrans(sssd-1.12.4-47.el6_7.8.ppc64) scriptlet
failed, exit status 1
Seems to install however sssd will no longer start. I can run ldap
searches against the IPA server and kinit without issue
I have un-enrolled the client and re-enrolled to no avail... once enroll
gets to starting sssd it says sssd restart failed and continues to enroll.
I have reinstalled sssd, ipa client and c-ares, I have removed the sssd
cache db.
The really strange part is if we wait approx 24 hours sssd starts working
again which we have reproduced on 2 servers we are testing with... are we
missing some sort of lease or cache? Using this to remove the sssd db
rm -rf /var/lib/sss/db/*
Here is a piece of the gdb core dump
Core was generated by `/usr/libexec/sssd/sssd_pac --uid 0 --gid 0 -d 0x37f0
'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000fff83f2bc64 in ._dl_vdso_vsym () from /lib64/libc.so.6
Part of SSSD.log with debug 9
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca0c10
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (sudo,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking sudo as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca4590
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (ssh,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking ssh as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca31b0
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (pam,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking pam as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034c9fc70
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (nss,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking nss as started.
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 1
(Tue Jun 27 21:13:14 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:14 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:14 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:16 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 2
(Tue Jun 27 21:13:16 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:16 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:16 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:16 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:19 2017) [sssd] [services_startup_timeout] (0x0400):
Handling timeout
(Tue Jun 27 21:13:20 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 3
(Tue Jun 27 21:13:20 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:20 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:20 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:20 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_restart_service] (0x0010):
Process [pac], definitely stopped!
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0040): Returned with: 1
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[ssh][14092]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [ssh]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[pam][14091]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [pam]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[sudo][14090]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [sudo]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[nss][14089]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [nss]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[example.local][14088]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child
[example.local] exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [sbus_remove_watch] (0x2000):
0x10034c9b8d0/0x10034c895a0
server.example.local:/var/log/sssd# sssd -d9
(Tue Jun 27 21:46:38:159841 2017) [sssd] [check_file] (0x0400): lstat for
[/var/run/nscd/socket] failed: [2][No such file or directory].
(Tue Jun 27 21:46:38:162382 2017) [sssd] [ldb] (0x0400): server_sort:Unable
to register control with rootdse!
(Tue Jun 27 21:46:38:163358 2017) [sssd] [confdb_get_domain_internal]
(0x0400): No enumeration for [example.local]!
(Tue Jun 27 21:46:38:163410 2017) [sssd] [confdb_get_domain_internal]
(0x1000): pwd_expiration_warning is -1
(Tue Jun 27 21:46:38:163570 2017) [sssd] [become_user] (0x0200): Trying to
become user [0][0].
(Tue Jun 27 21:46:38:163597 2017) [sssd] [become_user] (0x0200): Already
user [0].
(Tue Jun 27 21:46:38:163675 2017) [sssd] [server_setup] (0x0040): Becoming
a daemon.
this pauses for a few seconds and drops me back to command line with sssd
not started.
Client
sssd-client-1.12.4-47.el6_7.8.ppc64
sssd-ldap-1.12.4-47.el6_7.8.ppc64
sssd-krb5-common-1.12.4-47.el6_7.8.ppc64
sssd-common-1.12.4-47.el6_7.8.ppc64
sssd-proxy-1.12.4-47.el6_7.8.ppc64
sssd-common-pac-1.12.4-47.el6_7.8.ppc64
sssd-krb5-1.12.4-47.el6_7.8.ppc64
python-sssdconfig-1.12.4-47.el6_7.8.noarch
sssd-ipa-1.12.4-47.el6_7.8.ppc64
sssd-1.12.4-47.el6_7.8.ppc64
sssd-ad-1.12.4-47.el6_7.8.ppc64
ipa-client-3.0.0-47.el6_7.2.ppc64
IPA Server
ipa-server-3.0.0-50.el6.1.x86_64
Any help is appreciated as I have spent a good 15 hours reading the logs
and bug reports and not any closer to a resolution.
Sean Hogan
9:46 a.m.
On Wed, Jun 28, 2017 at 07:04:58AM -0700, Sean Hogan via FreeIPA-users wrote:
Hi All,
We are having an issue performing RHEL 6.6 to 6.7 upgrade with SSSD. The
systems are already enrolled and working in IPA 3.0.0-50 using 6.6 client.
We yum update and sssd gives this
Non-fatal POSTTRANS scriptlet failure in rpm package
sssd-1.12.4-47.el6_7.8.ppc64
warning: %posttrans(sssd-1.12.4-47.el6_7.8.ppc64) scriptlet
failed, exit status 1
I'm sorry if this comes off as less than helpful, but unless you have a
critical reason to use 6.7, please upgrade to 6.8 or even 6.9. You don't
have to upgrade the whole distro, but at least the sssd stack.
There was a ton of bugfixes between 6.7 and 6.8..
Seems to install however sssd will no longer start. I can run ldap
searches against the IPA server and kinit without issue
I have un-enrolled the client and re-enrolled to no avail... once enroll
gets to starting sssd it says sssd restart failed and continues to enroll.
I have reinstalled sssd, ipa client and c-ares, I have removed the sssd
cache db.
The really strange part is if we wait approx 24 hours sssd starts working
again which we have reproduced on 2 servers we are testing with... are we
missing some sort of lease or cache? Using this to remove the sssd db
rm -rf /var/lib/sss/db/*
Here is a piece of the gdb core dump
Core was generated by `/usr/libexec/sssd/sssd_pac --uid 0 --gid 0 -d 0x37f0
This is a bug in the sssd_pac responder. I couldn't find any related
bug report upstream or in RHBZ, but I would really suggest upgrading
first.
If the sssd_pac service still crashes, then we need to investiage the
problem further. Seeing that you're using ppc, chances are there might be
an endianess issue, but I can't think of any recent one.
9:46 a.m.
On Wed, Jun 28, 2017 at 07:04:58AM -0700, Sean Hogan via FreeIPA-users wrote:
Hi All,
We are having an issue performing RHEL 6.6 to 6.7 upgrade with SSSD. The
systems are already enrolled and working in IPA 3.0.0-50 using 6.6 client.
We yum update and sssd gives this
Non-fatal POSTTRANS scriptlet failure in rpm package
sssd-1.12.4-47.el6_7.8.ppc64
warning: %posttrans(sssd-1.12.4-47.el6_7.8.ppc64) scriptlet
failed, exit status 1
Seems to install however sssd will no longer start. I can run ldap
searches against the IPA server and kinit without issue
I have un-enrolled the client and re-enrolled to no avail... once enroll
gets to starting sssd it says sssd restart failed and continues to enroll.
I have reinstalled sssd, ipa client and c-ares, I have removed the sssd
cache db.
The really strange part is if we wait approx 24 hours sssd starts working
again which we have reproduced on 2 servers we are testing with... are we
missing some sort of lease or cache? Using this to remove the sssd db
rm -rf /var/lib/sss/db/*
Here is a piece of the gdb core dump
Core was generated by `/usr/libexec/sssd/sssd_pac --uid 0 --gid 0 -d 0x37f0
'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000fff83f2bc64 in ._dl_vdso_vsym () from /lib64/libc.so.6
This sounds quite like
https://bugzilla.redhat.com/show_bug.cgi?id=1398716. I'm not sure if you
are allowed to access this ticket. The current state is that it is
assumed to be a glibc issue on ppc64.
I'll add a link to this email to the ticket so that the people who are
working on the ticket are aware.
bye,
Sumit
Part of SSSD.log with debug 9
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca0c10
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (sudo,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking sudo as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca4590
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (ssh,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking ssh as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034ca31b0
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (pam,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking pam as started.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): dbus conn:
0x10034c9fc70
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_dispatch] (0x4000): Dispatching.
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_message_handler] (0x4000): Received
SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_get_sender_id_send] (0x2000): Not a
sysbus message, quit
(Tue Jun 27 21:13:14 2017) [sssd] [sbus_handler_got_caller_id] (0x4000):
Received SBUS method [RegisterService]
(Tue Jun 27 21:13:14 2017) [sssd] [client_registration] (0x0100): Received
ID registration: (nss,1)
(Tue Jun 27 21:13:14 2017) [sssd] [mark_service_as_started] (0x0200):
Marking nss as started.
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 1
(Tue Jun 27 21:13:14 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:14 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:14 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:14 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:16 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 2
(Tue Jun 27 21:13:16 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:16 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:16 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:16 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:19 2017) [sssd] [services_startup_timeout] (0x0400):
Handling timeout
(Tue Jun 27 21:13:20 2017) [sssd] [mt_svc_restart] (0x0400): Scheduling
service pac for restart 3
(Tue Jun 27 21:13:20 2017) [sssd] [get_ping_config] (0x0100): Time between
service pings for [pac]: [10]
(Tue Jun 27 21:13:20 2017) [sssd] [get_ping_config] (0x0100): Time between
SIGTERM and SIGKILL for [pac]: [60]
(Tue Jun 27 21:13:20 2017) [sssd] [start_service] (0x0100): Queueing
service pac for startup
(Tue Jun 27 21:13:20 2017) [sssd] [mt_svc_exit_handler] (0x0040): Child
[pac] terminated with signal [11]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_restart_service] (0x0010):
Process [pac], definitely stopped!
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0040): Returned with: 1
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[ssh][14092]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [ssh]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[pam][14091]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [pam]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[sudo][14090]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [sudo]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[nss][14089]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child [nss]
exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Terminating
[example.local][14088]
(Tue Jun 27 21:13:20 2017) [sssd] [monitor_quit] (0x0020): Child
[example.local] exited gracefully
(Tue Jun 27 21:13:20 2017) [sssd] [sbus_remove_watch] (0x2000):
0x10034c9b8d0/0x10034c895a0
server.example.local:/var/log/sssd# sssd -d9
(Tue Jun 27 21:46:38:159841 2017) [sssd] [check_file] (0x0400): lstat for
[/var/run/nscd/socket] failed: [2][No such file or directory].
(Tue Jun 27 21:46:38:162382 2017) [sssd] [ldb] (0x0400): server_sort:Unable
to register control with rootdse!
(Tue Jun 27 21:46:38:163358 2017) [sssd] [confdb_get_domain_internal]
(0x0400): No enumeration for [example.local]!
(Tue Jun 27 21:46:38:163410 2017) [sssd] [confdb_get_domain_internal]
(0x1000): pwd_expiration_warning is -1
(Tue Jun 27 21:46:38:163570 2017) [sssd] [become_user] (0x0200): Trying to
become user [0][0].
(Tue Jun 27 21:46:38:163597 2017) [sssd] [become_user] (0x0200): Already
user [0].
(Tue Jun 27 21:46:38:163675 2017) [sssd] [server_setup] (0x0040): Becoming
a daemon.
this pauses for a few seconds and drops me back to command line with sssd
not started.
Client
sssd-client-1.12.4-47.el6_7.8.ppc64
sssd-ldap-1.12.4-47.el6_7.8.ppc64
sssd-krb5-common-1.12.4-47.el6_7.8.ppc64
sssd-common-1.12.4-47.el6_7.8.ppc64
sssd-proxy-1.12.4-47.el6_7.8.ppc64
sssd-common-pac-1.12.4-47.el6_7.8.ppc64
sssd-krb5-1.12.4-47.el6_7.8.ppc64
python-sssdconfig-1.12.4-47.el6_7.8.noarch
sssd-ipa-1.12.4-47.el6_7.8.ppc64
sssd-1.12.4-47.el6_7.8.ppc64
sssd-ad-1.12.4-47.el6_7.8.ppc64
ipa-client-3.0.0-47.el6_7.2.ppc64
IPA Server
ipa-server-3.0.0-50.el6.1.x86_64
Any help is appreciated as I have spent a good 15 hours reading the logs
and bug reports and not any closer to a resolution.
Sean Hogan
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
10:04 a.m.
New subject: SSSD not starting
Hi Jakub
Thanks and it does not come off that way at all. I made the same
recommendations. I can only control the IPA servers and they are at 6.9
but the typical reason for not moving up... app not tested on higher level.
Sean Hogan
From: Jakub Hrozek via FreeIPA-users
<freeipa-users(a)lists.fedorahosted.org>
To: freeipa-users(a)lists.fedorahosted.org
Cc: Jakub Hrozek <jhrozek(a)redhat.com>
Date: 06/28/2017 07:47 AM
Subject: [Freeipa-users] Re: (no subject)
On Wed, Jun 28, 2017 at 07:04:58AM -0700, Sean Hogan via FreeIPA-users
wrote:
Hi All,
We are having an issue performing RHEL 6.6 to 6.7 upgrade with SSSD.
The
systems are already enrolled and working in IPA 3.0.0-50 using 6.6
client.
We yum update and sssd gives this
Non-fatal POSTTRANS scriptlet failure in rpm package
sssd-1.12.4-47.el6_7.8.ppc64
warning: %posttrans(sssd-1.12.4-47.el6_7.8.ppc64) scriptlet
failed, exit status 1
I'm sorry if this comes off as less than helpful, but unless you have a
critical reason to use 6.7, please upgrade to 6.8 or even 6.9. You don't
have to upgrade the whole distro, but at least the sssd stack.
There was a ton of bugfixes between 6.7 and 6.8..
Seems to install however sssd will no longer start. I can run ldap
searches against the IPA server and kinit without issue
I have un-enrolled the client and re-enrolled to no avail... once enroll
gets to starting sssd it says sssd restart failed and continues to
enroll.
I have reinstalled sssd, ipa client and c-ares, I have removed the
sssd
cache db.
The really strange part is if we wait approx 24 hours sssd starts working
again which we have reproduced on 2 servers we are testing with... are we
missing some sort of lease or cache? Using this to remove the sssd db
rm -rf /var/lib/sss/db/*
Here is a piece of the gdb core dump
Core was generated by `/usr/libexec/sssd/sssd_pac --uid 0 --gid 0 -d
0x37f0
This is a bug in the sssd_pac responder. I couldn't find any related
bug report upstream or in RHBZ, but I would really suggest upgrading
first.
If the sssd_pac service still crashes, then we need to investiage the
problem further. Seeing that you're using ppc, chances are there might be
an endianess issue, but I can't think of any recent one.
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
2491
days inactive
2491
days old
freeipa-users@lists.fedorahosted.org
3 comments
3 participants
participants (3)
-
Jakub Hrozek -
Sean Hogan -
Sumit Bose