On 02.05.15 09:06, Gene Heskett wrote: > Here is a snippet from /var/log/messages showing one such crash and my > pressing of the reset button when I found the mouse was frozen:
Aha, "crash" doesn't mean the host is rebooting. If it were, I'd expect swearwords in kern.log. But it it isn't, so it's probably some process hogging all the cycles. If you're already logged in over the network, running htop, then you might catch it - though it'll take a while to seep out with the hog up to its derriere in it. If you just have htop (or top) displaying on the offending host, then the X11 freeze ought to retain for a little while the figures immediately preceding the freeze. It isn't any process crashing - that'll just give a coredump if you've done a "ulimit -c unlimited", or otherwise leave the party unnoticed, and X won't freeze. You could run iotop as well, for good measure, but you'd probably hear disk thrashing unless it's a SSD. > Apr 29 14:42:51 lathe kernel: [62057.888772] hm2/hm2_5i25.0: IO Pin 033 > (P2-13): IOPort > Apr 29 14:42:51 lathe kernel: [62057.888955] hm2/hm2_5i25.0: registered > Apr 29 14:42:51 lathe kernel: [62057.888961] hm2_5i25.0: initialized AnyIO > board at 0000:05:00.0 > Apr 29 15:03:03 lathe kernel: imklog 4.2.0, log source = /proc/kmsg started. > Apr 29 15:03:03 lathe rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" > x-pid="755" x-info="http://www.rsyslog.com";] (re)start > Apr 29 15:03:03 lathe rsyslogd: rsyslogd's groupid changed to 103 > Apr 29 15:03:03 lathe rsyslogd: rsyslogd's userid changed to 101 > Apr 29 15:03:03 lathe kernel: [ 0.000000] Initializing cgroup subsys cpuset > Apr 29 15:03:03 lathe kernel: [ 0.000000] Initializing cgroup subsys cpu > Apr 29 15:03:03 lathe kernel: [ 0.000000] Linux version 2.6.32-122-rtai > (root@moses-6core) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #rtai SMP > Tue Jul 27 12:44:07 CDT 2010 (Ubuntu 2.6.32-122.35.rtai-rtai > 2.6.32.11+drm33.2) > Apr 29 15:03:03 lathe kernel: [ 0.000000] KERNEL supported cpus: > Apr 29 15:03:03 lathe kernel: [ 0.000000] Intel GenuineIntel > Apr 29 15:03:03 lathe kernel: [ 0.000000] AMD AuthenticAMD > Apr 29 15:03:03 lathe kernel: [ 0.000000] NSC Geode by NSC > Apr 29 15:03:03 lathe kernel: [ 0.000000] Cyrix CyrixInstead > Apr 29 15:03:03 lathe kernel: [ 0.000000] Centaur CentaurHauls > Apr 29 15:03:03 lathe kernel: [ 0.000000] Transmeta GenuineTMx86 > Apr 29 15:03:03 lathe kernel: [ 0.000000] Transmeta TransmetaCPU > > I don't see a thing in that. Nah, but not totally surprising. The bad stuff usually appears in /var/log/kern.log, and you're only freezing X. That's something I've only ever handled by coming in over the network to look at it, and usually kill the offending process. Erik ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
