I'm having a slight issue with apache segfaulting reasonably regularly. I've followed through the apache http debugging guide here:[URL] and receive this when running gdb:
Code:
[root@ukserv1 apache2-dump]# gdb /usr/sbin/httpd core.1085
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5_5.2)
[code]....
The nagios admin interface apparently needs php (although, of course, the howto mentions nothing of the sort). So then, I copied the php.conf that had at some time been installed on the system, and then moved by me out of /etc/httpd/conf.d, back into conf.d. It's a fairly simple one:
#
# PHP is an HTML-embedded scripting language which attempts to make it
# easy for developers to write dynamically generated webpages.
#
LoadModule php5_module modules/libphp5.so
[Code]....
I'm having some strange issues with apache. Time by time it segfaults, eats all available memory (including swap) and makes server non responding.Ubuntu Server 10.04.2 LTS
Some strange logs:
Jun 12 12:00:18 *** kernel: [40767.969443] apache2[7635]: segfault at 726f7272 ip 00007f13a31f3f16 sp 00007fff6f740ea0 error 4 in libapr-1.so.0.3.8[7f13a31d7000+35000]
[code]....
OS: Ubuntu Server x64 10.04 Apache: 2.2.14-5ubuntu8.4 I have a virtual server which has been running for months with no problems then one day I saw that it crashed and I had to power cycle it. Since then I have been unable to start Apache as it segfaults no matter options I give it. Before I try to reinstall Apache, why is this segfaulting?
Code:
execve("/usr/sbin/apache2", ["/usr/sbin/apache2"], [/* 21 vars */]) = 0
brk(0) = 0x7f9f48f8d000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9f47e0d000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
[Code]...
So MPD keeps segfaulting everytime it tries to play anything.I tried compiling a version from the MPD site, but that couldn't even see my music for some reason. Same user running MPD, same permissions on the files... I'd really like to get MPD working again, but it keeps segfaulting with this:
Code: nas kernel: [161048.253573] mpd[22957] general protection ip:b6efc1b5 sp:b53e1850 error:0 in libavcodec.so.52.20.1[b6ab4000+52b000]
I wiped my server recently because of all the custom stuff I had installed, and now MPD won't play music .
This just started today, after I installed a round of updates yesterday: I would attempt to login to my GNOME session. One of three things happens: it hangs, looking like it's authenticating, it lets me into my session but then abruptly logs me out and wrecks anything I was doing, or GDM just crashes altogether.
On tty6, I found this error in dmesg:
Code:
gdm-session-wor[1392]: segfault at 1 ip 0000000000000001 sp 00007fff57babe18 error 14 in gdm-session-worker[400000 + 17000]
The numbers may be slightly off, I had no way to copy and paste the error. I have no modifications to GDM except libpam-usb, which doesn't even work. Is it possible to roll back GDM to before the update?
I have some curious errors and crashes since yesterday. Firefox crashes without saying anything or just freezes. Thunderbird also crashed once without any reason, as far as I could discern.
Compiz is another candidate. Either it segfaults and sends me back to the GDM login screen or it crashes in another way, resulting in a flickering window with an unreadable error message (just an empty window with the nautilus icon in the menu bar, background image stays the same, Unity or any other compiz things are gone). I even had some real X segfaults mixed in.
Would upgrading your cpu ( athlon xp 1700+ to 2600 or 3200 ) be something that causes segfaults ?
View 2 Replies View RelatedI have a new IBM x3650 that I am trying to get installed and running. However, it seems to experience random segfaulting. The system has ECC RAM and I have taken a look at the EDAC reports from the kernel, but as far as I can tell there is no error.This is a critical system I need to bring up, so I can't have it act flaky like this. Software is up to date. [URL]
Example output:
Code:
__ratelimit: 1 callbacks suppressed
ld-linux-x86-64[7676]: segfault at b33000 ip 00000000003b557b sp 00007fff13789c18 error 6 in ld-2.9.so[39d000+20000]
ld-linux-x86-64[7699]: segfault at 62ddbb ip 000000000062ddbb sp 00007ffffa0ab520 error 15 in toc2cddb[62c000+9000]
ld-linux-x86-64[7939]: segfault at 161004011d5 ip 00000000001ea1f0 sp 00007fff1eeb14f0 error 4 in ld-2.9.so[1e2000+20000]
[code]....
In LMMS, pretty much any time where pressing a key or button is supposed to do something, it can crash. Regardless of what made it crash, it always dies in the exact same way: The window just disappears, and I get the line "Segmentation fault" in the console. Usually it crashes within 15 minutes of normal use. Not even 6 hours after I downloaded the program, I had given up trying to use it. Over the next week, a couple other programs crashed with segfaults.
Most of them only crashed once (among those was Firefox). So, of course, I'm now beginning to think that maybe the problem is not with LMMS, but rather with Ubuntu. I've had very little luck getting most of these programs to crash a second time, but I did find reliable ways to reproduce the crash in LMMS and Golly, so I got debug logs of those (with backtraces and steps I took to reproduce):
Code:
What I did to make LMMS Crash:
1. After starting LMMS, created an instrument track using the Oh Synth preset (under LB302)
2. Opened the tool window for the track.
3. Dragged my cursor back and forth across the keys on the virtual piano at the bottom of said window to play them.
4. Within 3 seconds, it crashed.
Starting program: /usr/bin/lmms
[Thread debugging using libthread_db enabled]
[New Thread 0xb7d62b70 (LWP 4674)]
[New Thread 0xb2c18b70 (LWP 4677)]
[New Thread 0xb2417b70 (LWP 4678)]
[New Thread 0xb195ab70 (LWP 4680)]
[New Thread 0xb1159b70 (LWP 4681)] .....
Code:
What I Did to make Golly Crash:
1. After starting Golly, loaded the example file "Still-Lifes/eaters.rle".
2. Alternated between Space (Next Generation) and Ctrl+Z (Undo), holding each for about 1 second.
3. Within 15 seconds, it crashed.
Starting program: /usr/games/golly
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x080fd47c in UndoRedo::RememberGenFinish() ()
#0 0x080fd47c in UndoRedo::RememberGenFinish() ()
#1 0x080f855c in MainFrame::NextGeneration(bool) ()
#2 0x081124f5 in MainFrame::OnMenu(wxCommandEvent&) ()
#3 0x00621a9f in wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const () from /usr/lib/libwx_baseu-2.8.so.0
#4 0x006c0379 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /usr/lib/libwx_baseu-2.8.so.0 .....
I've tried using different governors for CPU (Conservative, Ondemand, etc.), and these crashes continued to occur. I also tried using a different kernel to no avail; the crashes occur both on 2.6.32-21-generic and 2.6.31-17-generic. How to fix whatever's causing these segfaults.
Running Maverick Meerkat fairly close to original specs. When launching Rhythmbox from either the command line or the applications menu, the window appears briefly and closes whether or not I interact with it. During its time open (~3sec), it gives no indication that it recognizes input, i.e. menus do not open and buttons do not depress when clicked.
While running from the terminal, the following output is displayed.
Code:
(rhythmbox:2068): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
** (rhythmbox:2068): DEBUG: SyncDaemon already running, initializing SyncdaemonDaemon object
[code]....
I upgraded my processor two days ago(p4 -> C2D), and ever since then I have been getting segfaults, which are causing my programs to crash randomly. At first I thought it was isolated to one program(deluge), but after searching around I was looking at the /var/log/messages and found a bunch of segfault messages after I installaed the processor. Here is the grep from the messages file:
Code:
Nov 29 12:35:03 Thor kernel: [66065.114231] npviewer.bin[14952]: segfault at 0 ip 00000000f6232ed1 sp 00000000ffe9e6d0 error 4 in libflashplayer.so[f5e93000+b2e000]
Nov 29 12:41:23 Thor kernel: [66445.260799] npviewer.bin[15324]: segfault at 418 ip 00000000f60ddc86 sp 00000000ffb4b928 error 6 in libflashplayer.so[f5e8e000+b2e000]
[Code]...
I'm using Red Hat Enterprise Linux Server release 5. In this whenever a user process crashes due to segmentaion faults , it was not logged in /var/log/messages. Even dmesg is also not showing any messages related to this.
Where as in another distributions(Cent OS 5) I've seen segfaults messages in /var/log/messages whenever my user process crashed.dmesg also showing the segfaults.
Is there any settings that to enabled so that it logs segfaults into /var/log/messages.
I cross checked /etc/syslog.conf of both the systems. Both are same and even /etc/sysconfig/syslog files.
I googled around but most of what I could find said that segfaults are generally a memory issue. I've noticed lately that I'll occasionally get a segfault while compiling on my computer. There's no noticeable pattern, just that every now and then a bit of software that I'm trying to compile will segfault on me, even software that I've compiled in the past.
I ran memtest86+, but it showed no issues at all. I run a stock kernel on Slackware, with no modifications to the system other than installing multilib support (which I'm 100% sure is done correctly).
I've found what seems to be a reproducible problem with 'ash' on slackware64-current (updates to and including Jan 31st)
Open a console
ash <enter>
type 2 or more characters, doesn't matter what.
press backspace
press backspace
**seg fault**
occurs under xterm, konsole, gnome-terminal in both kde4 and xfce and on a virtual console.
New install slackware64 13.0. Sites that cause it to segfault are simple ones - gmail (2 seconds after I get past the sign in stage, and before I even open any email. This one also
www.channel4.com/programmes/4od.
I have done the obvious stuff - checking for missing libs with ldd, finding them, etc. Disks are 1-2 years old (ext3) and well checked, but this install has not been lived in yet. Plugins installed are: java 1.6.0_16; Flash 10.0 r45; SVG-2.26. Kernel is 2.6.33.2, made with 'make oldconfig from a very satisfactory 2.6.30.5 kernel which was faultless for some time.
The box is all-amd/ati HP6715S, with RS690 video and northbridge, sb600 southbridge. and a twin turion 2 Ghz. It is using the recent OSS xf86-video-ati drivers. The only strange Mozilla error was between 4th and 5th crash this session when it said "Input/Output Error". Otherwise the error shows as line 131 of run-mozilla.sh - the 'finally start the binary' routine.
When I am closing yast, from time to time I get this error. Although something segfaults the system seems to behave normally and I do not experience other issues it seams. The error comes up in a small separate window. Yast stays operative. Should I be worried about something? What is the system complaining about actually? Although this happens quite often, it does not happen always.
System is: 11.1 with Linux linux-xu0v 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux and KDE 3.5.10 (r87) Yast: 2.17.69-0.1.1-x86_64
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running.
[Code]...
I've started to get segfaults in sshd when trying to connect. There has been no reboot and (until I restarted the sshd to try to fix the problem) there was still another ssh session connected.
The log messages:
Code:
==> kern.log <==
Jan 6 21:33:38 shuttle kernel: [ 1928.611128] sshd[9548]: segfault at bf30e534 eip b7f51b4c esp bf30e510 error 6
==> auth.log <==
[Code]....
I installed the Adobe Font Forge fonts. They're all OpenType fonts and reside in ~/.fonts. Since around the time when I was fiddling with them, XeTeX started segfaulting whenever I used one of them. Any other font works fine. The strange thing is that I had one font already in ~/.fonts before I installed all of the new ones, which did work fine, but which now causes a segfault. The LaTeX file looks like this:
[Code]...
end{document} When I run xelatex test.tex, it segfaults and produces the log file I've attached to this post (renamed to test.txt from test.log). But, when I run xelatex with the -no-pdf switch, it produces a file test.xdv without complaining. When I then run xdvipdfmx -vv test.xdv, it segfaults and outputs to stdout what I've attached as a file error.txt. I suspect it might have something to do with system font settings that may have been changed by Fontmatrix while I was browsing my fonts, perhaps doing something that I didn't understand and messed things up. But I don't know which settings/config files/etc that may have been affected.
My friend's PC recently started acting up. He had me install Sabayon on it and everything was fine until a few days ago. Every app I try to run after the PC boots results in a segmentation fault. I figured maybe something was wrong with the HDD, so I tried to boot from a DSL liveCD to run fsck, but it wouldn't boot; it freezes right away. I then tried the Sabayon LiveDVD and got a kernel panic.Does anyone have any idea what the problem could be? I am completely clueless; I've never had anything like this happen before.
View 3 Replies View RelatedI'm testing upgrading from 11.1 to 11.3 and running into a major roadblock. When I try to ssh to the server after upgrading, I am unable to use password or pubkey auth to connect via ssh with my ldap user due to sshd segfault. I can however connect via pubkey to a local account on the system. Both auth methods work (for local users) when I disable UsePAM in sshd_config, but auth via ldap is required. My configuration works fine on fully patched installs of both 11.1 and 11.3, but not a fully patched 11.1 upgraded to 11.3. I've been at this for a while now trying various things but don't seem to be making much progress..
/var/log/messages:
Code:
Oct 6 20:33:15 susetest kernel: [ 1829.251921] sshd[3602]: segfault at 7f4bb0521240 ip 00007f4bb0509354 sp 00007fffdf212850 error 7 in libcrypto.so.1.0.0[7f4bb0449000+188000]/usr/sbin/sshd -ddd:
Code:
debug2: load_server_config: filename /etc/ssh/sshd_config
debug2: load_server_config: done config len = 431
debug2: parse_server_config: config /etc/ssh/sshd_config len 431
[code]....
Running slackware-current 32bit. I use digikam-1.7.0, kipi-plugins-1.7.0, and ufraw-0.17 which are all built using the sbo scripts from 13.1 repo. All the above work fine with lensfun-0.2.3 built from sbo, but trying to update lensfun to 0.2.5 causes segfaults in digiKam and ufraw.
Anyone else seen this and is there a fix? Seems to be caused by a change in lensfun between versions, but I think it's beyond me to sort on my own. Lensfun-0.2.5 seems to build fine without errors, but I believe there were warnings with respect to makedep. Digikam and ufraw locate the lensfun libraries during the build. Ufraw segfaults on startup and digikam segfaults when the auto lens correction tool is selected from the menu. I know none of these versions are officially supported either alone or in -current,
The version of mencoder I currently have installed segfaults (immediately) when you ask it to convert x264-encoded MKVs to another format. One sample command-line would be:
Code:
mencoder -nosound -ovc libdv Puella_Magi_Madoka_Magica_720p_GG_-_06.mkv -o a.avi
This produces the following output:
Code:
MEncoder 20110702-4.5.2 (C) 2000-2011 MPlayer Team
success: format: 0 data: 0x0 - 0x1c43987e
libavformat file format detected.
[Code]...
Incidentally, I'm wondering if the version of FFMpeg that the MPlayer configure script downloads might be at fault. The slightly outdated FFMpeg I installed from SBo (6.1) does not crash when converting the same file. And no, I can't use either Alien Bob's Mplayer build or the MPlayer binaries included with Slackware. Neither is built against either libdv or x264. I need libdv as an output codec.
Upgraded from 13.0 to 13.1 following the instructions. Downloaded latest nvidia package (NVIDIA-Linux-x86-96.43.16-pkg1.run) for my geForce4 MX 4000. Compiled and installed new module (old one was 96.43.13).
Xorg fails to start with this:
Code:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.1 Slackware Linux Project
Current Operating System: Linux mercury 2.6.33.4-smp #1 SMP Wed May 12 21:39:37 CDT 2010 i686
Kernel command line: BOOT_IMAGE=Linux ro root=805 vt.default_utf8=0 3
Build Date: 05 May 2010 01:54:53AM
Current version of pixman: 0.16.6
Before reporting problems, check [URL]
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.....
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a1e6b]
1: /usr/bin/X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
Segmentation fault at address 0xc
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
The "nv" driver works.
Starting around two weeks ago, Iceweasel began closing at unpredictable intervals for no apparent reason. When I ran it in GDB, it came up as a segfault, though the backtraces were different each time. It would even do this in safe mode, though it generally took longer. Icedove began doing the same thing around the same time.
So, I decided to reset my profile and start over. But now it's still segfaulting, even in safe mode.
A cursory use of memtester didn't turn up anything unusual.
Could it be some browser addon that is causing problems even when it's not activated?
If so, why is Icedove doing the same thing occasionally?
The biggest problem is that it's intermittent, so I would have to use my browser with a new profile for a long time before I could confirm that the problem is actually fixed.
I'm trying to upgrade Karmic to Lucid. I open the update manager, click the "upgrade" button, and then again the "upgrade" button in the window that pops up. Then it just closes down. When running the update manager from a terminal, the only output is "Segmentaion fault".
View 2 Replies View RelatedI have been using a ARM device with 512MB ram and flash to send messages via Bluetooth to everyone in the proximity. I am doing this with OpenProximity (Python) and it worked for the last week, it did stop for two times but since I didn't have time to find the cause, I just rebooted it (Windows style ) and it worked again, but suddenly it stopped working again last Saturday. When I did /etc/init.d/bluetooth restart it did not say it failed or something, but when I did /etc/init.d/bluetooth status it said "bluetooth is not running ... failed!". This is what I got in the syslog:
Code:
Apr 27 13:52:45 debian bluetoothd[31243]: Bluetooth daemon 4.60
Apr 27 13:52:45 debian bluetoothd[31243]: Starting SDP server
Apr 27 13:52:45 debian bluetoothd[31243]: Starting experimental netlink support
Apr 27 13:52:45 debian bluetoothd[31243]: Failed to find Bluetooth netlink family
Apr 27 13:52:45 debian bluetoothd[31243]: Failed to init netlink plugin
Apr 27 13:52:45 debian bluetoothd[31243]: Can't create GN bridge
[Code]...
You'll probably note that the first message is version 4.60 and the second one 4.63, this is because I tried to upgrade, but that did not work completely, but the error above is the same as first before the upgrade.
Don't know if it matters, but I am using Debian Squeeze and the output of uname -a is: Linux debian 2.6.32.2 #1 PREEMPT Fri Dec 18 22:54:28 MST 2009 armv5tel GNU/Linux. Hope someone know how this could happen suddenly, and even better, knows how to fix it
EDIT: Forgot to say, I am using a SENA Parani UD100 Bluetooth USB Adapter which uses the Toshiba Bluetooth stack.
UPDATE: It won't crash until the Bluetooth stick is inserted, so it should be a driver problem?
I have a tv tuner card connected to a cctv camera for streaming, all works good in tvtime, cheese used to work but then I changed the resolution to a lower one and now it segfaults, purged reinstalled same issue, also I tried with mplayer, mencoder, mythtv (coludn't find any signal on the input) and camorama.
Code:
mplayer tv:// -tv driver=v4l2:input=1:channel=1:width=768:height=768:device=/dev/video0
And it displays lines through everything but I can see the messed up image, I believe this is due to the current input format being YVU420, I was able in another program to verify this by changing the input codec to yvuv i think it was, how do I change the in mplayer, mencoder, camorama has this bug too, how to change this setting ut codec in mplayer and mencoder, also canorama has this issue, but I can actually see everything, b/w and with lines through it. I am just trying to record video to AVI.
I've probably exhausted all possible ffmpeg argument combinations for encoding with a libx264 codec - none worked, the codec always either segfaults or tells me incorrect parameters. I've installed, uninstalled and re-installed all available versions of the codec - no difference. Did anyone have any luck with it? Are there any tricks or conflicts in different arguments? Does the input file have to be in any particular container/format/codec for the x264 to work on?
My examples: >ffmpeg -i video.mpg -vcodec libx264 video.mkv >... Error while opening encoder for output stream #0.0 - maybe incorrect parameters such as bit_rate, rate, width or height >ffmpeg -i video.mpg -vcodec libx264 -b 4000 -s hd1080 -f h264 video.mkv Same error If I use any other codec, they all work fine. give a working ffmpeg arguments example,
I am running kde 4.4 in virtualbox , but cannot create xorg.conf to get a correct resolution. X -configure = segfault. Older releases were fine - lenny, even ubuntu hardy / lucid.
View 6 Replies View Related