General :: Segfaults Are Not Logging Into /var/log/messages
Dec 8, 2010
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 have a syslog-ng running and kernel build of 2.6.34.8 I use a syslog API in my program with facility LOG_LOCAL5 and and levels debug err and crit and info. when I ran on the older syslog facility I had everything logged fine as I intended. now I have written these rules into the syslog-ng.conf:
Generally SSH related log messages are logged in /var/log/messages file. Is there a way to log them in another different file? I mean is there some configuration setting to enable this?
I am facing a problem while trying to log SSH messages in a separate file, say, /var/log/ssh_logs. I have tried modifying the syslog-ng.conf file as follows:
I have a Asus RT-n12 router with DD-WRT v24-sp2 (12/19/10) mini(SVN revision 15943M NEWD-2 K2.6 Eko)I can not get my rsyslog on my linux pc to log messages from the router. I did a netstat -arn and got:
Code: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
I�m looking into preventing the samba messages from appearing in the system log (/var/log/messages).I added syslog = 0 to smb.conf and reloaded the config but messages are still appearing�suppress logging or reconfiguremba such that the �nmbd� and �winbindd� messages do not appear in /var/log/messages
I've got a Shorewall (Shoreline?) firewall up and running, but it's logging to /var/log/messages. I'd much rather have it logging to another location e.g. /var/log/firewall but can't find (a clear enough) explanation on how to do this. Apparently, it varies greatly depending on the distro, the kernel, and the version of Shorewall that is running. You'd think it would be something as simple as setting a path in a config file, but apparently not. I'm running a stock Lenny kernel on the firewall machine. It comes with version 4.0.15 of Shorewall.
I wish to prevent the samba messages (mainly nmbd and winbindd) from appearing in the system log (/var/log/messages). I want to allow samba logging to the standard samba logfiles, but prevent the syslog getting clogged up by samba. I added syslog = 0 to smb.conf and reloaded the config but the messages were still appearing. I also tried the following (and restarted the syslog via /sbin/service syslog restart) # Suppress messages from samba.
For interests sake the messages I'm getting are below (I'm not concerned about the messages themselves, I can chase them up at my leisure via the samba logs) Mar 18 09:58:29 SERVER nmbd[3808]: query_name_response: Multiple (2) responses received for a query on subnet xx.yy.z.zz for name DOMAIN<1d>. Mar 18 09:58:29 SERVER nmbd[3808]: This response was from IP xx.yy.z.zz, reporting an IP address of xx.yy.z.zz.
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).
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.
More than 7 G bytes were logged to the messages file last three weeks I got this message in /var/log/messages I want to stop this messaging cause it takes to much space
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.
I 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]
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.
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.
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]
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)
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.
I've installed OpenSUSE on my server and want to set ssh to log every command, which is send to system over it.
I've found this in my sshd_config:
I guess that both of those directives has to be uncommented, but I'd like to log every command, not only authorization (login/logout via SSH). I just want to know, if someone breaks into my system, what did he do.
I notice that one of the functions I can make a keyboard shortcut for in KDE is Log Out Without Confirmation. This might show a lack of imagination, but when might I want to do that?
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.
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.
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.
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
