kernel failure? in vnc

[Red Squirrel]

I installed VNC on my main server and installed gnome so I can use virtualbox for my VMs, as I want to migrate away from vmware server (2.0's interface sucks and 1.0 wont install on that distro without dying my hair gray).

I vnced in and got this huge warning about a kernel failure. Is there a way to get a log of exactly what happened? The dialog only had an option to report it but not to view a log. I figured /var/faillog but it's not readable, it's all binary data.

Other then that the system is running fine, though a few days ago it did totally lock up and I had to reboot, but it's been ok since then. I got this error twice so it's something that must be happening repeatedly in the background.

 

[Nothinman]

/var/log/faillog is the log of login failures. I believe RH drops all kernel messages in /var/log/messages by default.

 

[her209]

I get kernel failure messages after install FC9 in VMware Server VMs.

 

[Red Squirrel]

Did not find anything in /var/log/messages then again lot of the kernel level stuff in there is hard to make out on whether or not it's an error.

Is this something I should even worry about? The system is running fine.

 

[Nothinman]

It's impossible to say without knowing what the message said...

 

[Red Squirrel]

This is my messages log. This kernel error happened after I had used my external hdd for something, well it also happened before that. I got the error twice in vnc (it provides zero information, it just says that there was a kernel failure)



Using username "ryan".
ryan@borg.loc's password:
Last login: Sat Feb 14 23:32:55 2009 from destroyer.loc
-bash-3.2$ cat /var/log/messages
cat: /var/log/messages: Permission denied
-bash-3.2$ su -
Password:
[root@borg ~]# cat /var/log/messages
Feb 15 04:34:36 borg kernel: imklog 3.18.1, log source = /proc/kmsg started.
Feb 15 04:34:36 borg rsyslogd: [origin software="rsyslogd" swVersion="3.18.1" x-pid="2177" x-info="http://www.rsyslog.com"] restart
Feb 15 06:32:33 borg ntpd[3445]: time reset +0.202523 s
Feb 15 06:36:32 borg ntpd[3445]: synchronized to 192.43.244.18, stratum 1
Feb 15 14:47:43 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Accepted password for user root from 127.0.0.1
Feb 15 15:03:45 borg kernel: VirtualBox[24785] trap int3 ip:22cf88f sp:4126fc70 error:0
Feb 15 15:04:08 borg kernel: VirtualBox[24803] trap int3 ip:7fff78b3088f sp:41ff8c70 error:0
Feb 15 15:35:32 borg gconfd (vmuser-19385): Exiting
Feb 15 15:35:32 borg kernel: tomboy[19535]: segfault at 34b720 ip 34b720 sp 7fff9e5f1ca8 error 14 in mono[400000+1f3000]
Feb 15 15:36:42 borg gconfd (vmuser-25151): starting (version 2.22.0), pid 25151 user 'vmuser'
Feb 15 15:36:42 borg gconfd (vmuser-25151): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Feb 15 15:36:42 borg gconfd (vmuser-25151): Resolved address "xml:readwrite:/home/vmuser/.gconf" to a writable configuration source at position 1
Feb 15 15:36:42 borg gconfd (vmuser-25151): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Feb 15 15:36:42 borg pulseaudio[25159]: polkit.c: Cannot set UID on session object.
Feb 15 15:36:42 borg pulseaudio[25159]: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
Feb 15 15:36:42 borg pulseaudio[25159]: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
Feb 15 15:36:42 borg pulseaudio[25159]: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
Feb 15 15:36:42 borg pulseaudio[25159]: pid.c: Stale PID file, overwriting.
Feb 15 15:36:42 borg pulseaudio[25159]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Feb 15 15:36:42 borg pulseaudio[25159]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Feb 15 15:36:44 borg hcid[3361]: Default passkey agent 1.100, /org/bluez/passkey) registered
Feb 15 15:36:44 borg hcid[3361]: Default authorization agent 1.100, /org/bluez/auth) registered
Feb 15 15:36:46 borg gconfd (vmuser-25151): Resolved address "xml:readwrite:/home/vmuser/.gconf" to a writable configuration source at position 0
Feb 15 15:37:06 borg kerneloops: Submitted 0 kernel oopses to www.kerneloops.org
Feb 15 17:53:09 borg ntpd[3445]: kernel time sync status change 4001
Feb 15 19:18:31 borg ntpd[3445]: kernel time sync status change 0001
Feb 15 20:13:10 borg kernel: usb 2-3: new high speed USB device using ehci_hcd and address 2
Feb 15 20:13:10 borg kernel: usb 2-3: configuration #1 chosen from 1 choice
Feb 15 20:13:10 borg kernel: usb 2-3: New USB device found, idVendor=067b, idProduct=2507
Feb 15 20:13:10 borg kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 15 20:13:10 borg kernel: usb 2-3: Product: Mass Storage Device
Feb 15 20:13:10 borg kernel: usb 2-3: Manufacturer: Prolific Technology Inc.
Feb 15 20:13:11 borg kernel: Initializing USB Mass Storage driver...
Feb 15 20:13:11 borg kernel: scsi12 : SCSI emulation for USB Mass Storage devices
Feb 15 20:13:11 borg kernel: usbcore: registered new interface driver usb-storage
Feb 15 20:13:11 borg kernel: USB Mass Storage support registered.
Feb 15 20:13:16 borg kernel: scsi 12:0:0:0: Direct-Access ST332062 0A 3.AA PQ: 0 ANSI: 0
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB)
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] Write Protect is off
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] Assuming drive cache: write through
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB)
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] Write Protect is off
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] Assuming drive cache: write through
Feb 15 20:13:16 borg kernel: sde: sde1
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: [sde] Attached SCSI disk
Feb 15 20:13:16 borg kernel: sd 12:0:0:0: Attached scsi generic sg5 type 0
Feb 15 20:15:28 borg kernel: kjournald starting. Commit interval 5 seconds
Feb 15 20:15:28 borg kernel: EXT3 FS on sde1, internal journal
Feb 15 20:15:28 borg kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 15 20:15:39 borg kernel: CIFS VFS: Unexpected lookup error -112
Feb 15 20:15:49 borg kernel: CIFS VFS: Unexpected lookup error -112
Feb 15 20:15:59 borg kernel: CIFS VFS: Unexpected lookup error -112
Feb 15 20:16:09 borg kernel: CIFS VFS: Unexpected lookup error -112
Feb 15 22:05:03 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Accepted password for user root from 127.0.0.1
Feb 15 22:09:14 borg ntpd[3445]: kernel time sync status change 4001
Feb 15 22:35:39 borg kernel: CIFS VFS: No response for cmd 114 mid 4910
Feb 15 22:38:10 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 15 22:38:10 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 15 22:38:10 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 15 22:38:29 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 15 22:38:29 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 15 22:38:29 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 15 22:42:07 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 15 22:42:07 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 15 22:42:07 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 15 22:43:20 borg ntpd[3445]: kernel time sync status change 0001
Feb 15 22:44:00 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 15 22:44:00 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 15 22:44:01 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 15 22:48:15 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 15 22:48:15 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 15 22:48:15 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 15 23:00:16 borg kernel: CIFS VFS: cifs_mount failed w/return code = -6
Feb 15 23:34:35 borg ntpd[3445]: kernel time sync status change 4001
Feb 15 23:51:41 borg ntpd[3445]: kernel time sync status change 0001
Feb 16 00:18:03 borg kernel: CIFS VFS: No response for cmd 50 mid 45245
Feb 16 00:20:01 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 16 00:20:01 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 16 00:20:02 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 16 00:25:50 borg ntpd[3445]: kernel time sync status change 4001
Feb 16 01:17:08 borg ntpd[3445]: kernel time sync status change 0001
Feb 16 02:59:32 borg ntpd[3445]: kernel time sync status change 4001
Feb 16 03:18:09 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Rejected password for user root from 127.0.0.1
Feb 16 03:18:14 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Accepted password for user root from 127.0.0.1
Feb 16 03:33:39 borg ntpd[3445]: kernel time sync status change 0001
Feb 16 04:31:33 borg ntpd[3445]: time reset -0.366732 s
Feb 16 04:31:33 borg ntpd[3445]: kernel time sync status change 4001
Feb 16 04:36:53 borg ntpd[3445]: synchronized to 192.43.244.18, stratum 1
Feb 16 04:36:53 borg ntpd[3445]: kernel time sync status change 0001
Feb 16 07:16:47 borg ntpd[3445]: time reset +0.214545 s
Feb 16 07:21:07 borg ntpd[3445]: synchronized to 208.83.212.8, stratum 3
Feb 16 07:24:31 borg ntpd[3445]: synchronized to 192.43.244.18, stratum 1
Feb 16 12:20:01 borg kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 16 12:20:01 borg kernel: CIFS VFS: Send error in SessSetup = -13
Feb 16 12:20:01 borg kernel: CIFS VFS: cifs_mount failed w/return code = -13
Feb 16 14:27:25 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Accepted password for user root from 127.0.0.1
Feb 16 17:25:51 borg /usr/lib/vmware/bin/vmware-hostd[3281]: Accepted password for user root from 127.0.0.1
[root@borg ~]#

 

[Nothinman]

The PulseAudio stuff might need looking at but if sound works I wouldn't worry about it, it looks like it's just failing to set itself up for real-time priority.

The only other parts of that that I would consider real errors are the CIFS stuff but that just looks like a bad password.