Error 4 In Libc-2.12.1.so
have one accepted answer. Are you sure you want to replace the current answer with this one? Yes, I'm sure. Changed your mind? You previously marked this answer as accepted. Are you sure you want to unaccept it? Yes, I'm sure. Sign Up Log In submit Tutorials Questions Projects Meetups Main Site logo-horizontal DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In submit View All Results By: marko.korhonen Subscribe Subscribed Share 0 Yum problem in CentOS 6.5 October 16, 2014 7.1k views Hi, I started to have problems with yum. It does not return anything. When I check /var/log/messages, I can find following error messages: Oct 16 05:14:31 dev kernel: yum[28694]: segfault at 3000000000 ip 00000030130813c0 sp 00007fffc9047f98 error 4 in libc-2.12.so[3013000000+18a000] where the "dev kernel: yum" and "error 4 in libc-2.12.so" are always present. Any clues how to solve? I have tried to disable repos one by one. No luck there. Running yum with -d does not give a clue. I cannot find libc-2.12.so thought I don't know where is should exist. Log In to Comment Leave a Comment Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below. Log In to Comment 1 Answer 0 JonsJava October 29, 2014 Not sure if you updated prior to that and didn't reboot, but if that is the case, this is usually resolved by a reboot. If that doesn't fix it, try this: updatedb; locate libc-2.12.so Reply Log In to Comment 0 marko.korhonen October 30, 2014 Hi and thanks for reply, Reboot did not work, that was among first things I tried. For the command you provided, I just get "command not found". And as suggested in various sources the solution is to install mlocate package which of course I cannot do as yum is not working. My other server having same issue had updatedb command available so I now know where the file is located: /lib64/libc-2.12.so But what to do next? 0 JonsJava Octob
Status Importance Assigned to Milestone rhythmbox (Ubuntu) Edit Invalid Medium Unassigned Edit You need to log in to change this bug's status. Affecting: rhythmbox (Ubuntu) Filed here by: ionash. When: 2011-02-06 Completed: 2014-04-22 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 Invalid Medium Assigned to Nobody Me Comment on this change (optional) Email me about changes to this https://www.digitalocean.com/community/questions/yum-problem-in-centos-6-5 bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: rhythmbox Rhythmbox crash immediately every time I try to run it. Reinstallation doesn't help. janusz@janusz-desktop:~/Pulpit$ rhythmbox (rhythmbox:1968): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** Message: pygobject_register_sinkfunc is deprecated (GstObject) Naruszenie ochrony pamięci (core dumped) /var/log/messages: janusz-desktop kernel: [ 298.192808] rhythmbox[2781]: https://bugs.launchpad.net/bugs/714161 segfault at 0 ip 044e4770 sp b3eff068 error 4 in libc-2.12.1.so[4470000+157000] ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: rhythmbox 0.13.1-0ubuntu6.1 ProcVersionSignature: Ubuntu 2.6.35-26.46-generic 2.6.35.10 Uname: Linux 2.6.35-26-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Sun Feb 6 18:02:29 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100323) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such device ProcCmdline: rhythmbox ProcEnviron: LANG=pl_PL.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x74ba770: pcmpeqb (%esi),%xmm0 PC (0x074ba770) ok source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)! destination "%xmm0" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /lib/libc.so.6 rb_make_valid_utf8 () from /usr/lib/librhythmbox-core.so.1 ?? () from /usr/lib/librhythmbox-core.so.1 ?? () from /usr/lib/librhythmbox-core.so.1 ?? () from /lib/libglib-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in rb_make_valid_utf8() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare Tags: apport-crash i386 maverick Edit Tag help ionash. (janusz-arch) wrote on 2011-02-06: #1 Dependencies.txt Edit (6.8 KiB, text/plain; charset="utf-8") Disassembly.txt Edit (523 bytes, text/plain; charset=
Next This bug is not in your last search results. Bug1113 - glibc / libc-2.12.1.so https://bugs.mageia.org/show_bug.cgi?id=1113 causes sshd and httpd to segfault Summary: glibc / libc-2.12.1.so causes https://github.com/celery/celery/issues/640 sshd and httpd to segfault Status: RESOLVED FIXED Product: Mageia Classification: Unclassified Component: RPM Packages Version: 1 Platform: All Linux Priority: High Severity: critical TargetMilestone: --- Assigned To: Mageia Bug Squad QA Contact: URL: Whiteboard: Keywords: Dependson: Blocks: Show dependency tree /graph Reported: 2011-05-03 error 4 12:22 CEST by DariuszSki Modified: 2011-06-18 15:55 CEST (History) CC List: 3 users (show) cjw mageia misc See Also: Source RPM: glibc CVE: Status comment: Attachments Add an attachment (proposed patch, testcase, etc.) Description DariuszSki 2011-05-03 12:22:25 CEST Description of problem: Running the Beta of Mageia, I can use console to SSH another machine on internal / internet, error 4 in but if I SSH to the Mageia machine I get a "connection refused" message, log file shows a .so segfaults. Likewise, if I use SFTP to another machine internally / internet, there is no problem, but if I try to SFTP to the Mageia machine, the connection is refused, same .so segfaults. From syslog: SSH using console. 03/05/2011 10:39:38 localhost kernel sshd[25991]: segfault at bf711864 ip b73009dc sp bf711854 error 6 in libc-2.12.1.so[b7248000+15f000] 03/05/2011 10:40:02 localhost kernel ===>rt_ioctl_giwscan. 7(7) BSS returned, data->length = 888 03/05/2011 10:40:53 localhost kernel sshd[26576]: segfault at bf576744 ip b73c49dc sp bf576734 error 6 in libc-2.12.1.so[b730c000+15f000] SFTP using Filezilla GUI. 03/05/2011 10:49:27 localhost kernel sshd[30273]: segfault at bf6fcf34 ip b73db9dc sp bf6fcf24 error 6 in libc-2.12.1.so[b7323000+15f000] 03/05/2011 10:49:33 localhost kernel sshd[30278]: segfault at bf6d24c4 ip b74369dc sp bf6d24b4 error 6 in libc-2.12.1.so[b737e000+15f000] 03/05/2011 10:49:38 localhost kernel ===>rt_ioctl_giwscan. 7(7) BSS returned, data->length = 886 Version-Release number of selected component (if applicable): libc-2.12.1.so How reproducible: Attempt to login to a Mageia machine using shell SSH or GUI SFTP. Comment
Sign in Pricing Blog Support Search GitHub This repository Watch 304 Star 5,371 Fork 1,769 celery/celery Code Issues 157 Pull requests 21 Projects 0 Wiki Pulse Graphs New issue celeryd workers dying to segfault with CELERYD_FORCE_EXECV enabled #640 Closed mattdeboard opened this Issue Mar 13, 2012 · 12 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 7 participants mattdeboard commented Mar 13, 2012 I have a problem that seems somewhat similar to issue #627 (and an echo of #614): When I have CELERYD_FORCE_EXECV=True workers are initialized then killed instantly. I tailed my syslog while this was going on, to get screens full of the following: https://gist.github.com/f97546b9157aa0bf6667 Though I normally run the celeryd process using supervisor, this segfault persists even when running directly from command line, only if CELERYD_FORCE_EXECV=True is present in my settings file. mattdeboard closed this Mar 13, 2012 mattdeboard reopened this Mar 13, 2012 vmihailenco commented Mar 14, 2012 I can confirm: Mar 14 11:42:18 kernel: [7479983.436090] [celeryd@host[1707]: segfault at b7255000 ip b7753309 sp bfb58ad0 error 4 in libpthread-2.11.1.so[b7747000+15000] Mar 14 11:42:26 kernel: [7479991.467155] [celeryd@host[1800]: segfault at b7255000 ip b7849312 sp bfa47930 error 7 in libpthread-2.11.1.so[b783d000+15000] dmaniloff commented Mar 16, 2012 Same here: Mar 16 15:55:21 vagrant kernel: [1196670.816848] [celeryd@vagran[7569]: segfault at 7f16febba000 ip 00007fdc01ea2390 sp 00007fffa0dce308 error 4 in libpthread-2.11.3.so[7fdc01e95000+17000] Mar 16 15:55:23 vagrant kernel: [1196673.358936] [celeryd@vagran[7580]: segfault at 7f16febba000 ip 00007f1a4df34390 sp 00007fffb48041b8 error 4 in libpthread-2.11.3.so[7f1a4df27000+17000] Mar 16 15:55:27 vagrant kernel: [1196676.784737] [celeryd@vagran[7598]: segfault at 7f16febba000 ip 00007f8c937bb390 sp 00007fff6ed808d8 error 4 in libpthread-2.11.3.so[7f8c937ae000+17000] aknapp commented Mar 19, 2012 We are seeing the exact same error also, only when using CELERYD_FORCE_EXECV = True in our settings file. aknapp commented Mar 19, 2012 I should also mention: We are running this on Ubuntu 10.04, and Python 2.6.5. It's easily reproducible on our end, so if you need anymore info, feel free to ask. mattdeboard commented Mar 22, 2012 Ditto. One thing that I've just realized is that the clients sending tasks to the broker are us