Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1186887
Description of problem: I have no idea how this problem occurred other than I was using the system and the System Security Services daemon was running. Version-Release number of selected component: sssd-common-1.12.3-2.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/sbin/sssd -D -f crash_function: talloc_abort executable: /usr/sbin/sssd kernel: 3.17.8-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 talloc_abort at ../talloc.c:340 #3 talloc_abort_access_after_free at ../talloc.c:359 #4 talloc_chunk_from_ptr at ../talloc.c:380 #5 _talloc_free at ../talloc.c:1559 #6 mt_svc_exit_handler at src/monitor/monitor.c:2759 #7 sss_child_invoke_cb at src/util/child_common.c:174 #8 tevent_common_loop_immediate at ../tevent_immediate.c:135 #9 epoll_event_loop_once at ../tevent_epoll.c:907 #10 std_event_loop_once at ../tevent_standard.c:114 #11 _tevent_loop_once at ../tevent.c:530 Potential duplicate: bug 908759
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 owner: somebody => lslebodn review: True => 0 selected: => testsupdated: => 0
milestone: NEEDS_TRIAGE => SSSD 1.12.4 priority: major => critical
patch: 0 => 1
resolution: => fixed status: new => closed
Metadata Update from @jhrozek: - Issue assigned to lslebodn - Issue set to the milestone: SSSD 1.12.4
Hi!
We are using sssd 1.13.4 but sometimes get a similar error:
in sssd.log
(Wed May 9 08:23:48 2018) [sssd] [talloc_log_fn] (0x0010): talloc: access after free error - first free may be at (null) (Wed May 9 08:23:48 2018) [sssd] [talloc_log_fn] (0x0010): Bad talloc magic value - access after free
In syslog:
May 9 08:24:46 SDTPC302 sssd[pac]: Shutting down May 9 08:24:46 SDTPC302 systemd[1]: sssd.service: Main process exited, code=dumped, status=6/ABRT
May I help to diagnose this? (Users can not login and they need to restart their workstations)
Please see https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html and https://docs.pagure.org/SSSD.sssd/users/reporting_bugs.html
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch adjusted to on (was: 1) - Custom field review reset (from 0) - Custom field testsupdated reset (from 0)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3614
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.