Error 4 In Libpthread-2.12.so
error 4 on gui log in General support questions Post Reply Print view Search Advanced search 8 posts • Page 1 of 1 AlanH Posts: 4 Joined: 2013/02/21 01:51:02 Location: Richardson, TX [SOLVED] seg fault error 4 on gui log in Quote Postby AlanH » 2013/02/21 02:41:31 Hi I am new to the forum and to Centos, so please be patient with me. I apologies in advance as this is a bit long. I am trying to set up a server for my research group and have run into a snag. I bit of history, the server was first built at the beginning of December, by a student who was leaving the group. I inherited the box with a fresh install of Centos 6.3 that had not even been booted for first use. I do not have the full specs of the machine with me as I am at home right now, but off the top of my head it is a new i5 with 32 GB ram using the internal Intel graphics of the i5. The system was installed on a 1.5 TB drive with a secondary 2TB data drive. About 3 weeks ago our building had a power spike that may have affected the machine. The issues started showing up when a user could not mount and NFS share he uses (logging in via ssh in case it matters). I logged in directly and noticed several gnome applets crashing due to signal 11. Disk utility reported that the system drive had 27 bad sectors, but running bad blocks in the terminal did not report any issues. After a bit of searching and trying to repair the disk, I did a fresh install on a new disk and everything ran fine for 4 day ( 2 of them were the weekend while no one was in the office) then started getting the signal 11 errors again. I figured the power spike must have damaged the mobo or cpu, so I do a fresh install on yet another drive in a whole new system. This one is a mac pro with dual xenon 6 core processors and 62 GB of ram (my professor wants me to convert 3 more of these beasts and cluster if we can get them working). This system works for about 2 days before getting the signal 11 errors. For this latest build I took a look in /var/log/messages and found thisFeb 20 14:04:25 modeler kernel: wnck-applet[10443]: segfault at 3c00000000 ip 0000003c25128190 sp 00007fff9c721688 error 4 in libc-2.12.so[3c25000000+18900
related to applications and software problems Post Reply Print view Search Advanced search 4 posts • Page 1 of 1 macdutra Posts: 2 Joined: 2014/12/26 13:21:29 Problem tgtd Quote Postby macdutra » 2014/12/26 13:54:21 Hi http://www.centos.org/forums/viewtopic.php?t=3606 everybody, happy holidays...I have a Centos 6.5 server and I had a segfault in tgtd process two times in a month. I found at RedHat advisories this information https://rhn.redhat.com/errata/RHBA-2014-1599.html.My question is: Must I upgrade my centos http://www.centos.org/forums/viewtopic.php?t=50305 version to 6.6?Bellow dmesg's segfault error and abrt output. Thanks and happy new year!!!tgtd[22128]: segfault at 0 ip (null) sp 00007fffe44bc678 error 14 in tgtd[400000+3e000]@0Directory: /var/spool/abrt/ccpp-2014-12-25-09:33:09-22128abrt_version: 2.0.8analyzer: CCpparchitecture: x86_64cgroup: cmdline: tgtdcomponent: scsi-target-utilscount: 1executable: /usr/sbin/tgtdhostname: myserverkernel: 2.6.32-431.el6.x86_64last_occurrence: 1419507189os_release: CentOS release 6.5 (Final)package: scsi-target-utils-1.0.24-12.el6_5pid: 22128pwd: /reason: Process /usr/sbin/tgtd was killed by signal 11 (SIGSEGV)time: Thu 25 Dec 2014 09:33:09 AM BRSTuid: 0username: rootuuid: 0e1b0358dc8e55bced29bfbf569d63fd6fb988facoredump: Binary file, 34439004160 bytesmaps: Text file, 325294 bytesopen_fds: Text file, 12646 bytessosreport.tar.xz: Binary file, 164401516 bytesvar_log_messages: Text file, 7518 bytesdso_list::/lib64/ld-2.12.so glibc-2.12-1.132.el6_5.4.x86_64 (CentOS) 1410367146:/usr/lib64/librdmacm.so.1.0.0 librdmacm-1.0.17-1.el6.x86_64 (CentOS) 1410367476:/usr/sbin/tgtd scsi-target-utils-1.0.24-12.el6_5.x86_64 (CentOS) 1410367481:/lib64/libaio.so.1.0.1 libaio-0.3.107-10.el6.x86_64 (CentOS) 1410291361:/lib64/libc-2.12.so glibc-2.12-1.132.el6_5.4.x86_64 (CentOS) 1410367146:/lib64/libgcc_s-4.4.7-20120601.so.1 libgcc-4.4.7-4.el6.x86_64 (CentOS) 1410291188:/usr/lib64/libibverbs.so.1.0.0 libibverbs-1.1.7-1.el6.x86_64 (CentOS) 1410367475:/lib64/libdl-2.12.so glibc-2.12-1.132.el6_5.4.x86_64 (CentOS) 1410367146:/lib
Importance Assigned to Milestone Gwibber Edit Invalid Undecided Unassigned Edit You need to log in https://bugs.launchpad.net/bugs/602903 to change this bug's status. Affecting: Gwibber Filed here by: Omer Akram When: 2010-07-28 Completed: 2010-10-08 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu https://fedorahosted.org/sssd/ticket/1061 Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance error 4 Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report gwibber (Ubuntu) Edit Expired Medium Unassigned Edit You need to log in to change this bug's status. Affecting: gwibber (Ubuntu) Filed here by: Robbie Williamson When: 2010-07-07 Completed: error 4 in 2010-12-29 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Expired Medium Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: gwibber Crashed multiple times today with the following line repeated in dmesg output: gwibber-service[PID]: segfault at e8013880 ip 00007f04fff39644 sp 00007f04ee75e780 error 4 in libpthread-2.12.so[7f04fff30000+18000] Attaching portion of dmesg output ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gwibber-service 2.31.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3 Uname: Linux 2.6.35-6-generic x86_64 Architecture: amd64 Date: Wed Jul 7 16:30:21 2010 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gwibber Tags: amd64 apport-bug maverick Edit Tag help Robbie Wil
5 years ago Last modified 5 years ago RHEL6.1/sssd_pam segmentation fault Reported by: sgallagh Owned by: sgallagh Priority: critical Milestone: SSSD 1.5.15 Component: PAM Version: 1.5.1 Keywords: Cc: Blocked By: Blocking: Sensitive: Tests Updated: no Coverity Bug: Patch Submitted: yes Red Hat Bugzilla: 748924 Design link: Feature Milestone: Design review: Fedora test page: Chosen: Candidate to push out: Release Notes: Temp mark: Description (last modified by sgallagh) (diff) https://bugzilla.redhat.com/show_bug.cgi?id=748924 Description of problem: sssd_pam segmentation fault messages --------- Sep 20 09:33:19 jonah kernel: sssd_pam[1971]: segfault at 10 ip 000000000042f453 sp 00007fffbab2d780 error 4 in sssd_pam[400000+3d000] Sep 20 09:33:19 jonah abrt[10948]: saved core dump of pid 1971 (/usr/libexec/sssd/sssd_pam) to /var/spool/abrt/ccpp-1316478799- 1971.new/coredump (1568768 bytes) Sep 20 09:33:19 jonah abrtd: Directory 'ccpp-1316478799-1971' creation detected Sep 20 09:33:20 jonah sssd[pam]: Starting up Sep 20 09:33:20 jonah abrtd: New crash /var/spool/abrt/ccpp-1316478799-1971, processing Version-Release number of selected component (if applicable): RHEL6.1 kernel 2.6.32-131.0.15.el6.x86_64 sssd-1.5.1-34.el6.x86_64 How reproducible: Sometimes, the customer is trying to reproduce it, but still not sure. Nothig but core file. ---- $ tar tvzf sssd_pam_abrtlog.tar.gz -rw-r----- abrt/root 4 2011-09-20 09:33 ./analyzer -rw-r----- abrt/root 6 2011-09-20 09:33 ./architecture -rw-r----- abrt/root 4786 2011-09-20 11:45 ./backtrace -rw-r----- abrt/root 48 2011-09-20 09:33 ./cmdline -rw-r----- abrt/root 4 2011-09-20 09:33 ./component -rw-r--r-- root/root 1568768 2011-09-20 09:33 ./coredump <======= core file -rw-r----- abrt/root 359 2011-09-20 09:33 ./description -rw-r----- abrt/root 26 2011-09-20 09:33 ./executable -rw-r----- abrt/root 40 2011-09-20 11:45 ./global_uuid -rw-r----- abrt/root 5 2011-09-20 09:33 ./hostname -rw-r----- abrt/root 26 2011-09-20 09:33 ./kernel -rw-r----- abrt/root 17 2011-09-20 09:33 ./package -rw-r----- abrt/root 1 2011-09-20 11:45 ./rating -rw-r----- abrt/root 68 2011-09-20 09:33 ./reason -rw-r----- abrt/root 54 2011-09-20 09:33 ./release -rw------- root/root 12357332 2011-09-20 09:33 ./sosreport.tar.xz -rw-r----- abrt/root 10 2011-09-20 09:33 ./time -rw-r----- abrt/root 1 2011-09-20 09:33 ./uid --- Steps to Reproduce: 1. 2. 3. Actual results: Crashed with Segfault with sssd_pam Expected results: No crash. Additional info: [root@dhcp-207-132 sssd_pam_abrtlog]# gdb /usr/libexec/sssd/sssd_pam coredump