Errors in Kernel logs on my RV120W
Hello, after succesfully update to version 1.0.5.6, I have errors in my log.
I made a factory reset after update and manualy set everything.
I have cable internet connection, DHCP server in Cisco, use wifi and I have a few firewall and forwarding rules.
I tried to uncheck all in Firewall settings on Attack prevention and after restart is everything the same.
There are a lot the same logs and there are no free memory for next records.
Everything I set in my log setting is Kernel Errors logging - there is only one way to log dropped or allowed connections.
My log is here:
Mon Oct 14 17:08:53 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:08:53 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:08:53 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:28 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 3 messages suppressed.
Mon Oct 14 17:09:28 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:09:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:08 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:08 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:18 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:18 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:28 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:28 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:33 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:43 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:43 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:43 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:43 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:48 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:48 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:48 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:10:58 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:03 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:24 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:24 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:24 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:24 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:29 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:34 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:34 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:44 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:44 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:54 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:11:54 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:04 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:29 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:29 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:34 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:34 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:34 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:39 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:39 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:39 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:49 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:49 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:59 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:12:59 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:09 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:09 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:14 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:19 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 5 messages suppressed.
Mon Oct 14 17:13:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:29 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:29 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:39 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:39 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:49 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:49 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:59 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:13:59 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:09 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:09 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:14:19 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:19:55 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:00 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:20:10 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 487 messages suppressed.
Mon Oct 14 17:20:10 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:22:05 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 130 messages suppressed.
Mon Oct 14 17:22:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:22:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:23:15 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:29:30 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 17:29:30 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 17:33:05 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 4 messages suppressed.
Mon Oct 14 17:33:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:33:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:33:05 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:34:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:35:35 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 67 messages suppressed.
Mon Oct 14 17:35:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:35:35 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:39:30 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 17:39:30 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 2 messages suppressed.
Mon Oct 14 17:48:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:06 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 10 messages suppressed.
Mon Oct 14 17:49:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:41 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:46 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:46 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:46 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:49:56 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:50:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:51:36 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:51:36 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:51:36 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:53:16 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:54:56 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 5 messages suppressed.
Mon Oct 14 17:54:56 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:01 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:06 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:07 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:07 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:07 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:42 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:42 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:42 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:57:47 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:58:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:01:22 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 5 messages suppressed.
Mon Oct 14 18:01:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:03:22 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] printk: 4 messages suppressed.
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:17 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:37 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:04:37 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 18:05:22 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 18:05:22 2013(EET) [Kaudigate][Kernel][KERNEL] ERROR:endChantRecv: protocol PNAC returned !OK
Mon Oct 14 18:07:32 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Mon Oct 14 17:08:53 2013(EET) [Kaudigate][Kernel][KERNEL] cvm_ipfwd_cache_flow: Failed to allocate flow info buffer
Dear Jan,
Thank you for reaching the Small Business Support Community.
I would think is a memory failure but anyway, and since you have already done the possible troubleshooting and there are no known issues about this, I suggest you to contact the Small Business Support Center to figure this out;
https://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
Please do not hesitate to reach me back if there is any further assistance I may help you with in the meantime.
Kind regards,
Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer
*Please rate the Post so other will know when an answer has been found.
Similar Messages
-
Error 41 - Kernel Power in event log after clean shutdown - Windows 8.0
HP Envy H9-1405A - 16MB RAM, Windows 8.0, and up to date with updates. (16 months old but under extended h/w warranty). All user data backed-up daily.
After problems earlier today I noticed that after a controlled shutdown and start from cool (ie on/off button on PC, not mains power at the wall) the startup took over 10 minutes. Event browser showed error 41 - Kernel Power - "after system crash or lost power unexpectedly", which it definitely hadn't as I was testing a controlled shutdown.
When starting from overnight sleep mode this morning it came up with blue screen and an error mssage something like 'hard disk driver error', or similar (before first coffee so I wasn't really awake). PC wouldn't restart in anything like reasonable time until powered off at wall, after which it struggled up and ran normally for a while. Went out for a couple of hours and on return again the PC wouldn't re-start from sleep mode. Again used the wall power switch to effect the restart and PC and after very slow restart it ran normally. Event log showed Startup Repair ran due to a corrupted registry hive, and reboot used an earlier version.
Checkdisk ran clean and the HP Support Assistant diags just looped for ever.
I then tried a system restart, which worked but took a long time, and then a controlled power down and start from cool which also took a long time as described above. I've temporarily turned off sleep mode so as to keep working.
Question - do I have a transient software problem which might be fixable with Recovery, or failing hardware that should be covered by warranty, and where might I find some hardware diagnostics to show to the supplier? Thanks.Hello @mikerb,
I have read your post on how your desktop computer is displaying an error message in regards to a Kernel event log, and I would be happy to assist you in this matter!
To further diagnose this issue, I recommend following the steps in this document on Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first". This should help to resolve the critical error message.
Just to be on the safe side, I also suggest following this resource on Testing for Hardware Failures (Windows 8); which should help determine if there is a hardware defect with one or multiple hardware components on your computer.
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping! -
Hallo,<br>
<br>
I try to recover a Database with the HP Data Protector Plug-in. I had made a Full-Backup and a Trans-Backup. These sessions were terminated successfully. <br><br><br>
<br>
After that i had deleted the Data volume and the Log volume of the database and rebooted the Server. Now I want recover the Database.<br><br><br>
<br>
Following actions are done by Data Protector:<br><br>
Executing the dbmcli command: `user_logon'.<br>
Executing the dbmcli command: `dbm_configset -raw BSI_ENV /var/opt/omni/tmp/DEMODB.bsi_env'.<br>
Executing the dbmcli command: `db_admin'.<br>
Executing the dbmcli command: `dbm_configset -raw set_variable_10 OB2BACKUPAPPNAME=DEMODB'.<br>
Executing the dbmcli command: `dbm_configset -raw set_variable_11 OB2BACKUPHOSTNAME=n4shost.sapdb.local'.<br>
Executing the dbmcli command: `util_connect'.<br>
Restoring backup 2009/06/04 0020.<br>
Executing the dbmcli command: `medium_put BACKDP-Data[1]/1 /var/opt/omni/tmp/DEMODB.BACKDP-Data[1].1 PIPE DATA 0 8 NO NO \"\" BACK'.<br>
Executing the dbmcli command: `recover_start BACKDP-Data[1] DATA ExternalBackupID "DEMODB 09060420:1 Stream"'.<br>
<br>
STARTING Media Agent "LTO_drive2"<br>
<br>
Starting OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Completed OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Restoring backup 2009/06/04 0021.<br>
<br>
Executing the dbmcli command: `medium_put BACKDP-Archive/1 /var/opt/omni/tmp/DEMODB.BACKDP-Archive.1 PIPE LOG 0 8 NO NO \"\" BACK'.<br>
<br>
Executing the dbmcli command: `db_state'.<br>
<br>
Executing the dbmcli command: `recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09060421:1 Stream"'.<br>
<br>
Starting OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Completed OB2BAR Restore: n4shost.sapdb.local:/DEMODB/Data/1 "SAPDB"<br>
<br>
Executing the dbmcli command: `db_state'.<br>
<br>
Executing the dbmcli command: `recover_start BACKDP-Archive LOG ExternalBackupID "DEMODB 09060421:2 Stream"'.<br>
<br>
Error: SAPDB responded with: -24920,ERR_BACKUPOP: backup operation was unsuccessful<br>
The database was unable to fulfill a request (-1, ).<br>
.<br>
<br>
Executing the dbmcli command: `exit'.
<br>
<br>
<br>
The recovery of the last Full-Backup is successful. But the logfiles not.<br>
<br>
First time I get this error in the Kernel log:<br>
2009-06-04 17:25:57 35 ERR 11000 d0_vatta Cannot open volume, No such file or directory <br>
2009-06-04 17:25:57 35 ERR 11000 d0_vatta Volume name 'DISKL0001'
<br>
(DISKL001 is my Database Log file)<br>
I had generated a new Log-File with db_activate.<br>
<br>
Now I get:<br>
2009-06-04 17:50:09 24 ERR 51080 SYSERROR -9407 unexpected error<br>
2009-06-04 17:50:09 24 ERR 3 Admin Kernel_Administration.cpp:606<br>
2009-06-04 17:50:09 24 ERR 3 Admin 2009-06-04 17:50:09 Admin Error 3<br>
2009-06-04 17:50:09 24 ERR 3 Admin Database state: OFFLINE<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Log_Volume.cpp:342<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Log Error 20040<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Logrecovery is not allowed, because state of log volume is 'HistoryLost' (log must be cleared)<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Log_Volume.cpp:343<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Log Info 8<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Log- and Data are not compatible because 'Restore Log with Log State 'HistoryLost' is not allowed'.<br>
2009-06-04 17:50:09 24 ERR 3 Admin + Kernel_Administration.cpp:762<br>
2009-06-04 17:50:09 24 ERR 3 Admin + 2009-06-04 17:50:09 Admin Warning 20025<br>
2009-06-04 17:50:09 24 ERR 3 Admin - Initialization of log for 'restore log' failed with 'LogAndDataIncompatible'<br>
2009-06-04 17:50:11 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)<br>
2009-06-04 17:50:11 ___ Stopping GMT 2009-06-04 15:50:11 7.6.00 Build 018-123-119-055
<br>
<br>
How can I clear the History Log. I had try rename the dbm.knl file. Now the Backup history in the dbmcli is empty. But the error is still there.<br>
<br>
Can anyone help me to fix this issue?<br>
<br>
Thanks to everyone!<br>
Edited by: Timm Letzel on Jun 4, 2009 6:59 PMThis is the knldiag-file:<br>
<br>
<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 66 servertasks for 'Backup / Restore'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 2 servertasks for 'Backup / Restore'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 SrvTasks 31: Permanently reserved 1 servertasks for 'Savepoint'.<br>
Thread 0x45A Task 1 2009-06-15 12:49:25 RTETask 18: Kernel initialization done<br>
DESCRIPTION:<br>
The initialization of the Kernel components has finished. All special tasks are started now.<br>
Thread 0x45B Task 232 2009-06-15 12:51:48 CONNECT 12633: Connect req. (MAXDB1, T232, connection obj. 0x2afdf1840070, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1840348, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 as number 3 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 as number 3 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 3.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 71: start of formatting of volume LOG_VOLUME_001 ( from file position 8192 to 52428800 ),PAGESIZE=6400,PAGE_OFFSET=1<br>
DESCRIPTION:<br>
Start of formatting volume LOG_VOLUME_001. Beginning to write from the 8192. byte to the size of 52428800. This matches the database page from 1 to the size of 6400 pages. The RTE header page is included here.<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12677: Client has released connection, T231<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 74: Number of pages left to format /var/opt/sdb/data/MAXDB1/log/DISKL0001:6399<br>
DESCRIPTION:<br>
Since formatting the volume /var/opt/sdb/data/MAXDB1/log/DISKL0001 takes some time, every 5 seconds the amount of remaining pages is put out. Currently 6399 pages are left.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 76: formatting of volume /var/opt/sdb/data/MAXDB1/log/DISKL0001 completed<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/log/DISKL0001 with number 3 was closed<br>
Thread 0x45B Task 231 2009-06-15 12:51:51 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1840348)<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 10: volume LOG_VOLUME_001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:51 RTEIO 8: attach volume LOG_VOLUME_001 on /var/opt/sdb/data/MAXDB1/log/DISKL0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type LOG_VOLUME_001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/log/DISKL0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 11: detach of volume LOG_VOLUME_001 path /var/opt/sdb/data/MAXDB1/log/DISKL0001<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/log/DISKL0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:51 RTEIO 10: volume LOG_VOLUME_001 has identification 2,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume LOG_VOLUME_001 with the logical volume number 1 is identified by 2.<br>
2009-06-15 12:51:51 RTEIO 8: attach volume LOG_VOLUME_001 on /var/opt/sdb/data/MAXDB1/log/DISKL0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type LOG_VOLUME_001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/log/DISKL0001 is being attached.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 112: Open of medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE successfull<br>
DESCRIPTION:<br>
Opening medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 as number 2 for WRITE was successfull. A medium is opened for data backup and data restoration. A database volume can also be opened as a medium. The medium received the internal number 2.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 71: start of formatting of volume DATA_VOLUME_0001 ( from file position 8192 to 1073741824 ),PAGESIZE=131072,PAGE_OFFSET=1<br>
DESCRIPTION:<br>
Start of formatting volume DATA_VOLUME_0001. Beginning to write from the 8192. byte to the size of 1073741824. This matches the database page from 1 to the size of 131072 pages. The RTE header page is included here.<br>
Thread 0x442 Task - 2009-06-15 12:51:51 RTEIO 74: Number of pages left to format /var/opt/sdb/data/MAXDB1/data/DISKD0001:131071<br>
DESCRIPTION:<br>
Since formatting the volume /var/opt/sdb/data/MAXDB1/data/DISKD0001 takes some time, every 5 seconds the amount of remaining pages is put out. Currently 131071 pages are left.<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1841678, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:52 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1841678)<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf1841678, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:54 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf1841678)<br>
Thread 0x442 Task - 2009-06-15 12:51:56 RTEIO 76: formatting of volume /var/opt/sdb/data/MAXDB1/data/DISKD0001 completed<br>
Thread 0x442 Task - 2009-06-15 12:51:56 RTEIO 114: medium /var/opt/sdb/data/MAXDB1/data/DISKD0001 with number 2 was closed<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 10: volume DATA_VOLUME_0001 has identification 3,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 3.<br>
2009-06-15 12:51:56 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 11: detach of volume DATA_VOLUME_0001 path /var/opt/sdb/data/MAXDB1/data/DISKD0001<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 is being detached from the active database configuration. The used path is /var/opt/sdb/data/MAXDB1/data/DISKD0001.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 RTEIO 10: volume DATA_VOLUME_0001 has identification 3,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume DATA_VOLUME_0001 with the logical volume number 1 is identified by 3.<br>
2009-06-15 12:51:57 RTEIO 8: attach volume DATA_VOLUME_0001 on /var/opt/sdb/data/MAXDB1/data/DISKD0001,VOLUME_NO=1<br>
DESCRIPTION:<br>
The volume of the type DATA_VOLUME_0001 with the logical number 1 and the path of /var/opt/sdb/data/MAXDB1/data/DISKD0001 is being attached.<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 DATACACH 53000: Begin data cache restart<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE STRIPES : 16<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE HASH LIST :2553088<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE head item siz: 16<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE CONTROLBLOCKS:4954112<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DATACACHE cblock size : 128<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 20 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 30 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 40 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 50 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 60 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 70 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 80 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 90 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 95 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 KernelDBE_ 20005: data cache size rise above 99 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynpool 54003: DYNP_B20_DATACACHE :7816832<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 dynDATA 54003: DYND_B20_DATACACHE : 38704<br>
Thread 0x45B Task 232 2009-06-15 12:51:57 DATACACH 53000: Finish data cache restart<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12633: Connect req. (MAXDB1, T231, connection obj. 0x2afdf18435f8, Node:'n4shost-stby.sapdb.local', PID: 1065)<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12677: Client has released connection, T231<br>
Thread 0x45B Task 231 2009-06-15 12:51:58 CONNECT 12651: Connection released (MAXDB1, T231, connection obj. 2afdf18435f8)<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 53000: Begin data cache shutdown<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 95 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 90 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 80 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 70 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 60 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 50 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 40 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 30 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 KernelDBE_ 20006: data cache size fell below 20 percent of initial size<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 54003: Released cache frames: 38704<br>
Thread 0x45B Task 232 2009-06-15 12:51:58 DATACACH 53000: Finish data cache shutdown<br> -
Mac Mini Audio Intermittent over HDMI, Cuts out with Assertion in kernel.log
Hello. I've been having trouble with a mac mini (Mid 2011) that I bought on Thursday. It's running OSX 10.7. The Mac Mini is the $599 unit.
I've got it hooked up to my Sony BRAVIA HDTV (also this year's model) via HDMI, with audio configured to be delivered via HDMI to the TV alongside video. Initially the audio will play through my TV, but after an hour or two of watching something, it will cut out, and there will be no more sound coming out of the TV from the mac. Ultimately, the only way I can fix it is to reboot the Mac Mini. I've also observed that at about the same time sound cuts out, the following error message appears in kernel.log:
Aug 12 19:21:40 joshs-Mac-mini kernel[0]: Sound assertion "0 != result" failed in AppleHDAWidget at line 3957 goto handler
Aug 12 19:22:10 --- last message repeated 5 times
As far as I know, assertions failures usually mean software problems (bugs). I suspect I may be encountering a kernel-level bug in Lion, as this error message is showing in kernel.log.
The following is a list of diagnostic steps I've taken:
- I've double-checked the sound output device in preferences. It didn't spontaneously change from SONY TV (HDMI) after sound cut out.
- I've tried changing output to the internal speakers. It plays sound from the mac mini (as expected). When I change it back to HDMI, still no sound from the TV.
- I've tried turning off and back on the tv. No effect.
- I've tried unplugging and replugging the HDMI cable. No effect.
- I've tried replacing the HDMI cable with two other alternates. No effect.
- I've tried other HDMI inputs for my TV with HDMI attached. No effect.
- Note: I've got a ps3 and xbox360 on the TV that has successfully used the HDMI inputs and cables tested on. They've never had this type of problem, so I don't think there's a problem with the TV.
- I've tried rebooting the mac and resetting the "PRAM" (Command-Option-P-R before the grey screen on bootup). Sound still cuts out after a while.
- All updates are applied.
Does anybody else have any ideas about what I could try to fix this? This problem is pretty much a deal breaker, as rebooting the mac mini mid-movie kind of destroys the movie-watching experience.
ThanksI'd just like to jump in on this thread to report exactly the same problem.
2011 Mac Mini (the 2.5GHz i5 model) running Lion, Sony Bravia TV, HDMI sounds cuts out after a while with the console error "Aug 15 18:30:25 Mini kernel[0]: Sound assertion "0 != result" failed in AppleHDAWidget at line 3957 goto handler".
Interestingly, after the error occurs, I can still get 5.1 sound through Plex, but not through Quicktime. 2.0 sound and system sounds all fail until I reboot the system.
Any help would be appreciated. I would prefer not to have to return the Mini.
Thanks. -
Hi
the below errors are in Timesten , please any one tell me why this errors reported in log file.
Oct 21 13:59:06 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994
Oct 21 13:59:06 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 846.
Oct 21 13:59:07 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: monitor thread failed to disconnect, tt error 994.
Oct 21 13:59:16 msp2 TimesTen Data Manager 5.1.28.msp[10851]: [ID 702911 user.error] 10851: Error -131 reading line from socket 47
Oct 21 13:59:17 msp2 HA-MSP: [ID 702911 daemon.error] [msp-rg,msp-res] stop-msp: - MSP still running killing JVM process
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 507009 user.error] EventID=99| ttShmCreate: shmget(-33553667, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 378027 user.error] EventID=99| ttShmCreate: shmget(-33553666, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 507008 user.error] EventID=99| ttShmCreate: shmget(-33553665, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 378026 user.error] EventID=99| ttShmCreate: shmget(-33553664, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 507009 user.error] EventID=99| ttShmCreate: shmget(-33553667, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 378027 user.error] EventID=99| ttShmCreate: shmget(-33553666, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 507008 user.error] EventID=99| ttShmCreate: shmget(-33553665, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 378026 user.error] EventID=99| ttShmCreate: shmget(-33553664, 1048576, flags) failed with system error 17
Thanks .It looks top me like this is only a selection of the messages. Do you have verbose logging turned on (-verbose specified in the daemon options file: ttendaemon.options)? Without verbose logging it is very hard, if not impossible, to properly doiagnose these kinds of errors.
The first 4 lines are there because something caused the TimesTen datastore to become invalidated. However, these lines on their own do not give any indication why that happened. Theres should be other lines before these that show which process caused that.
The last 8 lines are a result of us being unable to create a new shared memory segment. This could be due to lack of memory, incorrect kernel parameters or because an 'old' segment (for the invalidated datastore) still exists.
Chris -
[Solved] Harddisks: lot of output in both dmesg and kernel.log
Situation:
Since a few weeks I'm having a new little home server. An intel atom d525 cpu with 2gb ram, which seems to be a nice compromise between speed, price and power consumption. I'm wanting to use this server mainly as file server (backup, bulk data), download server, automatic backups, video streaming for the TV and my computer, mpd server and just for some experiments.
For the data I've got 2 disks, 2Tb each in a mdadm raid1 set with a layer of lvm and ext4 as the filesystem. I've used a brand new usb stick of 8Gb for the / filesystem. I know usb sticks are not made to be used as a / filesystem, but it should work and when the stick wears out (years?) I can replace it easily and cheap.
First signs of problems:
After the arch install I went ahead and installed some services. Everything seemed to be fine and I was really happy with the new server. Until after 2-3 days uptime it 'crashed'. I didn't bother looking in the logs or whatever, so I just gave it a fine reset and it went up without troubles. Again 2-3 days later it crashed again. I plugged in the monitor again and it seemed to be the / file system giving some troubles. After some io errors on the / it remounted itself read only, which gives me an unusable server. After some ext4 checks, it happened again the reboot after.
After that I decided it must be either the usb stick or the usb controller be doing something fishy. I've put the / on an old 2gb usb stick and since then it seems to be running fine (uptime now a weak).
Untill the / is full:
Strange, the 2gb / is full whilst a week ago when moving the arch install from the old usb stick, it only used about 1300Mb. After some smart usage of du and find I found out that the logs were to blame. Both the kernel.log en everything.log were 300+mb.
I hope there is somebody here who can help me figure out why the logs are getting filled with these messages and how to fix it. And to tell me if there is a serious problem with the raid1 set (mounted on /home), since I need to be able to rely on it to some extends.
raid set:
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
/dev/sdc1 is the usb stick mounted on /
dmesg:
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
nmbd(11212): dirtied inode 801 (wins.dat.11212) on sdc1
jbd2/sdc1-8(725): WRITE block 1584712 on sdc1
nmbd(11212): dirtied inode 72329 (?) on sdc1
flush-8:32(1309): WRITE block 3072016 on sdc1
jbd2/sdc1-8(725): WRITE block 1584720 on sdc1
jbd2/sdc1-8(725): WRITE block 1584728 on sdc1
jbd2/sdc1-8(725): WRITE block 1584736 on sdc1
jbd2/sdc1-8(725): WRITE block 1584744 on sdc1
jbd2/sdc1-8(725): WRITE block 1584752 on sdc1
jbd2/sdc1-8(725): WRITE block 1584760 on sdc1
jbd2/sdc1-8(725): WRITE block 1584768 on sdc1
jbd2/sdc1-8(725): WRITE block 1584776 on sdc1
jbd2/sdc1-8(725): WRITE block 1584784 on sdc1
jbd2/sdc1-8(725): WRITE block 1584792 on sdc1
jbd2/sdc1-8(725): WRITE block 1584800 on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
syslog-ng(1224): dirtied inode 5027 (syslog-ng.persist) on sdc1
jbd2/sdc1-8(725): WRITE block 1584808 on sdc1
flush-8:32(1309): WRITE block 3668432 on sdc1
flush-8:32(1309): WRITE block 3668440 on sdc1
flush-8:32(1309): WRITE block 3668448 on sdc1
flush-8:32(1309): WRITE block 3668456 on sdc1
flush-8:32(1309): WRITE block 3668464 on sdc1
flush-8:32(1309): WRITE block 3668472 on sdc1
flush-8:32(1309): WRITE block 3668480 on sdc1
flush-8:32(1309): WRITE block 3668488 on sdc1
flush-8:32(1309): WRITE block 3668496 on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
syslog-ng(1224): dirtied inode 72847 (kernel.log) on sdc1
flush-8:32(1309): WRITE block 3684888 on sdc1
flush-8:32(1309): WRITE block 3684896 on sdc1
flush-8:32(1309): WRITE block 3684904 on sdc1
flush-8:32(1309): WRITE block 3684912 on sdc1
flush-8:32(1309): WRITE block 3684920 on sdc1
flush-8:32(1309): WRITE block 3684928 on sdc1
flush-8:32(1309): WRITE block 3684936 on sdc1
flush-8:32(1309): WRITE block 3684944 on sdc1
flush-8:32(1309): WRITE block 3684952 on sdc1
flush-8:32(1309): WRITE block 1309280 on sdc1
flush-8:32(1309): WRITE block 1136 on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
syslog-ng(1224): dirtied inode 72851 (everything.log) on sdc1
dmesg(11213): READ block 265816 on sdc1
kernel.log
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407424 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407432 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407440 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407448 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407456 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407464 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407472 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407480 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407488 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407496 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407504 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407512 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407520 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407528 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407536 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407544 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407552 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407560 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407568 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407576 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407584 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407592 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407600 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407608 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407616 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407624 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407632 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407640 on dm-0
Jan 24 19:34:58 nas kernel: python2(1584): WRITE block 2223407648 on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 40370181 (sabnzbd.log) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: python2(1582): dirtied inode 46139255 (flying.wild.alaska.s01e02.720p.hdtv.x264-momentum.part18.rar) on dm-0
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sdb1
Jan 24 19:34:58 nas kernel: md127_raid1(1074): WRITE block 8 on sda1
Jan 24 19:34:59 nas kernel: bash(11231): READ block 916240 on sdc1
Jan 24 19:34:59 nas kernel: tail(11231): READ block 916272 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3692640 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 3709104 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588128 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588136 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588144 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588152 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588160 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588168 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588176 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588184 on sdc1
Jan 24 19:34:59 nas kernel: jbd2/sdc1-8(725): WRITE block 1588192 on sdc1
Especially the lines with 'dirtied inode' do worry me .
Ps: I do know that running archlinux on a server is not 'smart'. Same for using a usb flash device for /. Both are not considered smart choices, but for a home server which doesn't need to have a 100% uptime not always a bad choice and are not the topic of discussion .
Last edited by evert_ (2011-01-24 21:21:55)There are both log entries about the flash disk and the raid 1 set. The flash disk (sdc) entries don't seem to be critical, but I have no clue why they appeared...
I make a regular backup of my / to protect myself against loss of data due to wear some day. I've ran a little server in the past on a 4gb usb flash medium for several years, without any problems what so ever.
Last edited by evert_ (2011-01-24 18:52:54) -
Please help with Windows 7 x64 System error: Critical Kernel-power Event 41
I'm recieving this error while moving my laptop or working with it? Can someone help me to read memory dumps and to understand what causes this error please?
Where i can fount theese dump files? Can someone read them and is it possible to understand what is happening?
I have made full check of my memory and there are No errors I've also checked HDD with regenerator there are no errors too. but this not means that they can not be the problem. There is doubt about one of my HDD because when laptop is blocking there is bad
noise from HDD.
PS: There is another issue which is strange two of times when this happens the whole MBR was destroyed and the system refuses to boot ... only reboots. And i made bootrec /fixboot /fixmbr and this solve the problem ... I don't know is this connected with
system error, but i'm trying to give more details.
Thanks a lot.
Here are i'm posting my error details:
System
Provider
[ Name]
Microsoft-Windows-Kernel-Power
[ Guid]
{331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID
41
Version
2
Level
1
Task
63
Opcode
0
Keywords
0x8000000000000002
TimeCreated
[ SystemTime]
2011-06-25T20:38:38.328017300Z
EventRecordID
7571
Correlation
Execution
[ ProcessID]
4
[ ThreadID]
8
Channel
System
Computer
Rumen-PC
Security
[ UserID]
S-1-5-18
EventData
BugcheckCode
0
BugcheckParameter1
0x0
BugcheckParameter2
0x0
BugcheckParameter3
0x0
BugcheckParameter4
0x0
SleepInProgress
true
PowerButtonTimestamp
129535076822776383Before every critical Errors in event log i found information about Kernel Power I'm pasting it here:
System
Provider
[ Name]
Microsoft-Windows-Kernel-Power
[ Guid]
{331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID
89
Version
0
Level
4
Task
86
Opcode
0
Keywords
0x8000000000000020
TimeCreated
[ SystemTime]
2011-06-27T16:07:21.023625500Z
EventRecordID
9262
Correlation
Execution
[ ProcessID]
4
[ ThreadID]
44
Channel
System
Computer
Rumen-PC
Security
[ UserID]
S-1-5-18
EventData
ThermalZoneDeviceInstanceLength
21
ThermalZoneDeviceInstance
ACPI\ThermalZone\TZS1
AffinityCount
1
_PSV
0
_TC1
0
_TC2
0
_TSP
0
_AC0
0
_AC1
0
_AC2
0
_AC3
0
_AC4
0
_AC5
0
_AC6
0
_AC7
0
_AC8
0
_AC9
0
_CRT
361
_HOT
0
_PSL
0000000000000000
System
Provider
[ Name]
Microsoft-Windows-Kernel-Power
[ Guid]
{331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID
89
Version
0
Level
4
Task
86
Opcode
0
Keywords
0x8000000000000020
TimeCreated
[ SystemTime]
2011-06-27T16:07:21.039225600Z
EventRecordID
9263
Correlation
Execution
[ ProcessID]
4
[ ThreadID]
44
Channel
System
Computer
Rumen-PC
Security
[ UserID]
S-1-5-18
EventData
ThermalZoneDeviceInstanceLength
21
ThermalZoneDeviceInstance
ACPI\ThermalZone\TZS0
AffinityCount
1
_PSV
359
_TC1
0
_TC2
50
_TSP
0
_AC0
0
_AC1
0
_AC2
0
_AC3
0
_AC4
0
_AC5
0
_AC6
0
_AC7
0
_AC8
0
_AC9
0
_CRT
361
_HOT
0
_PSL
0000000000000000
These two informations are before every critical error. -
Receiving "Error truncating change log: null" after redeploying application
Hi,
I am running Weblogic 8.1 SP5 on Windows 2003. We are running into a problem where we redeploy an EAR on the server and it's causing an error "Error truncating change log: null" in the admin server. Here are the basic steps:
1) We have an application from a third-party that is deployed to the managed nodes in a cluster.
2) We Stop the application.
3) We redeploy the application. The application redeploys ok.
4) We stop the application for a 2nd time.
5) We redeploy the application. This time, the server reports that it's in progress forever. This is when we start to see the errors in the log.
6) To get the server back, we need to shut down the managed and admin servers.
7) We have to kill the java.exe process on each node.
8) We have to delete the ldap directory on the admin node.
9) Once we restart the server, we are back again.
So, after receiving hundreds (maybe a few thousand), we get the error:
java.io.IOException: More than 2048 open files
If anyone has any idea what's happening, it would be greatly appreciated.
Thanks,
Eric
Here is the full stack trace:
####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <Error truncating change log: null>
####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.io.IOException: More than 2048 open files>
####<Sep 2, 2011 12:44:15 PM EDT> <Critical> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.io.IOException: More than 2048 open files
at java.io.RandomAccessFile.open(Ljava.lang.String;I)V(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:204)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:94)
at com.octetstring.vde.replication.BackendChangeLog.open(BackendChangeLog.java:192)
at com.octetstring.vde.replication.BackendChangeLog.truncate(BackendChangeLog.java:183)
at com.octetstring.vde.replication.BackendChangeLog.receiveEntryChanges(BackendChangeLog.java:540)
at com.octetstring.vde.backend.BackendHandler.modify(BackendHandler.java:717)
at com.octetstring.vde.operation.ModifyOperation.perform(ModifyOperation.java:144)
at com.octetstring.vde.MessageHandler.doModify(MessageHandler.java:280)
at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:73)
at com.octetstring.vde.WorkThread.executeWorkQueueItem(WorkThread.java:83)
at weblogic.ldap.LDAPExecuteRequest.execute(LDAPExecuteRequest.java:28)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
####<Sep 2, 2011 12:44:15 PM EDT> <Error> <EmbeddedLDAP> <cdtscms11p> <VgnAdminServer> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <000000> <java.lang.NullPointerException: null>Chris
Could you please tell us what version of DVD SP your are using?
If its 3.x or earlier, then A.Pack should be used.
If it's 4.x, then you will need to use compressor's, Dolby 2.0 audio encoding, because A.Pack will have been removed by the DVD SP 4's installer.
There are also adjustments you will need to make to the basic settings of the Dolby 2.0 settings that come with compressor or A.Pack, to get the best output.
Here's a how to: http://www.kenstone.net/fcphomepage/a_packwarmouth.html -
RAC crashed - errors in messages log
2 node RAC. running 1 node config.
OEL 5.
Oracle 11.2.0.2.0
RAC crashed this morning with following errors in ASM log
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpsemsper
Found blog notes to up the semaphores in the kernel. http://arjudba.blogspot.ie/2008/09/database-startup-fails-with-ora-27302.html
bumped up to the following as per note but didnt fix
from: kernel.sem = 256 32000 100 128
to: kernel.sem = 256 32768 100 228
then tried 258 - didnt work
found another blog note that said to try 288 and that DID work so appears to be a semaphore issue. 2 questions:
1: How can this happen all of a sudden? no changes on box for last 5-6 weeks, nothing else running except RAC.
2. Error in /var/log/messages log file. RAC came down at 10:02, messges in the log file from 10:01, must be related. anyone know what they are? Looks like storage to me.
Jan 10 10:01:48 orcldub817 kernel: lpfc 0000:08:00.0: 0:(0):0713 SCSI layer issued Device Reset (0, 23) return x2002
Jan 10 10:02:17 orcldub817 kernel: INFO: task MpxPeriodicCall:28484 blocked for more than 120 seconds.
Jan 10 10:02:17 orcldub817 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 10 10:02:17 orcldub817 kernel: MpxPeriodicCa D ffffffff80151248 0 28484 1 28485 28483 (L-TLB)
Jan 10 10:02:17 orcldub817 kernel: ffff810c0d8e78a0 0000000000000046 ffff810095560840 ffff810c2f7b14f8
Jan 10 10:02:17 orcldub817 kernel: ffff810c2f7b1000 000000000000000a ffff810c28a96100 ffff81062fd6a100
Jan 10 10:02:17 orcldub817 kernel: 00267af542a39442 0000000000008106 ffff810c28a962e8 000000072e01a0c8
Jan 10 10:02:17 orcldub817 kernel: Call Trace:
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff80064167>] wait_for_completion+0x79/0xa2
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8008e16d>] default_wake_function+0x0/0xe
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff801459cc>] blk_execute_rq_nowait+0x86/0x9a
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff80145a78>] blk_execute_rq+0x98/0xc0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8840b90d>] :emcp:emcp_scsi_cmd_ioctl+0x2ad/0x400
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88412cb5>] :emcp:PowerPlatformBottomDispatch+0x3d5/0x760
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff884130d8>] :emcp:PowerSyncIoBottomDispatch+0x78/0xd0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88413626>] :emcp:PowerDispatchX+0x356/0x410
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff884147fd>] :emcp:EmsInquiry+0x9d/0x1a0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8863245a>] :emcpmpx:ClariionKLam_getPathLunStatus+0x8a/0x110
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88622391>] :emcpmpx:MpxDefaultTestPath+0x21/0x80
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88631bf3>] :emcpmpx:MpxLnxTestPath+0x43/0x270
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff800a1bad>] autoremove_wake_function+0x9/0x2e
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8008c597>] __wake_up_common+0x3e/0x68
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8002e511>] __wake_up+0x38/0x4f
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88407e9e>] :emcp:PowerPutSema+0x4e/0x60
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8006f1f5>] do_gettimeofday+0x40/0x90
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8862a054>] :emcpmpx:MpxTestPath+0x234/0x1fc0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff80063ff8>] thread_return+0x62/0xfe
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8862e8cb>] :emcpmpx:MpxPeriodicTestPath+0x9b/0x230
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8840e9c4>] :emcp:PowerTimeout+0x1a4/0x1e0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8006f1f5>] do_gettimeofday+0x40/0x90
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8862ed5a>] :emcpmpx:MpxPeriodicCallout+0x2fa/0x410
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8862ea60>] :emcpmpx:MpxPeriodicCallout+0x0/0x410
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8841164d>] :emcp:PowerServiceDaemonQ+0xad/0xd0
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8005efb1>] child_rip+0xa/0x11
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff88411670>] :emcp:PowerDaemonStart+0x0/0x20
Jan 10 10:02:17 orcldub817 kernel: [<ffffffff8005efa7>] child_rip+0x0/0x11
Jan 10 10:02:17 orcldub817 kernel:second node messages log has exact same...
Jan 10 10:01:48 orcldub818 kernel: lpfc 0000:08:00.0: 0:(0):0713 SCSI layer issued Device Reset (1, 23) return x2002
Jan 10 10:02:11 orcldub818 kernel: INFO: task MpxPeriodicCall:28298 blocked for more than 120 seconds.
Jan 10 10:02:11 orcldub818 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 10 10:02:11 orcldub818 kernel: MpxPeriodicCa D ffffffff80151248 0 28298 1 28299 28297 (L-TLB)
Jan 10 10:02:11 orcldub818 kernel: ffff810626d7d8a0 0000000000000046 ffff8107adac6500 ffff810c2ff7e4f8
Jan 10 10:02:11 orcldub818 kernel: ffff810c2ff7e000 000000000000000a ffff81062a2ad7a0 ffff81062fcf80c0
Jan 10 10:02:11 orcldub818 kernel: 00267d060c8f888d 000000000002ac41 ffff81062a2ad988 0000000676dd2cd8
and same messages as per node 1 above.Edited by: 961469 on Jan 10, 2013 5:46 AMDude wrote:
Why do you think it's a problem with kernel semaphores?
There are 2 other issues that I suggest to look into first:
SCSI layer issued Device Reset (0, 23)
ORA-27301: OS failure message: No space left on device
To me this looks like a hardware problem with your EMC storage
Also please provide exact details about your OS version and system.See the errors in the ASM first of all. A few notes are thrown up when we look for those errors. Upping the semaphores resolved. My task now is to get to root cause.
versions: x86_64 2.6.18-194.el5
While increasing the semaphores resolved, I too think it looks like a problem with the storage as we get the same issue in the messages fil eon both nodes at same time.
couple of things looking at ipcs that dont make sense
[root@orcld818 proc]# ipcs -sa | wc -l
242
[root@orcl818 proc]# ipcs -sa
242 listed -
0x45116b13 7241949 root 666 1
0x45116ab3 7274718 root 666 1
0x45116a13 7307487 root 666 1
0x45116a73 7340256 root 666 1
0x45116a93 7373025 root 666 1
0x45119ca9 7405794 root 666 1
0x451187f7 7438563 root 666 1 All those returned are root owned, this doesnt make sense to me, I thought there should be only a few listed owned by oracle
If I try to identify any the processes associated with those, theres a PID listed, yet the pid doesnt exist when I try to query it e.g. the last one listed above...
[root@orcl818 proc]# ipcs -i 7438563 -s
Semaphore Array semid=7438563
uid=0 gid=0 cuid=0 cgid=0
mode=0666, access_perms=0666
nsems = 1
otime = Thu Jan 10 11:15:13 2013
ctime = Thu Jan 10 11:15:12 2013
semnum value ncount zcount pid
0 0 0 0 22922
[root@orcl818 proc]# ps -ef | grep 22922
root 19611 9740 0 14:54 pts/2 00:00:00 grep 22922
[root@orcl818 proc]#
[root@orcl818 proc]# ls /proc/22922
ls: /proc/22922: No such file or directory
[root@orcl818 proc]# -
ACPI Error filling up logs, is generally disconcerting.
I keep getting these errors in my kernel log
Sep 6 00:02:01 computer kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L09] (Node eb80fdb0), AE_LIMIT
Sep 6 00:02:01 computer kernel: ACPI Exception (evgpe-0568): AE_LIMIT, while evaluating GPE method [_L09] [20090320]
Sep 6 00:02:01 computer kernel: ACPI Error (hwvalid-0154): Illegal I/O port address/length above 64K: 0x00400020/4 [20090320]
Sep 6 00:02:01 computer kernel: ACPI Exception (evregion-0422): AE_LIMIT, Returned by Handler for [SystemIO] [20090320]
They just repeat over and over again. The only problem I'm noticing is my logs are getting ridiculously large. I could probably change syslog around and never know I have a problem but I figure that would just lead to trouble later on. Google and some other linux sources turned up nothing helpful on these errors. So I'm hoping someone can atleast tell me where to start looking if they don't know exactly what's wrong.Suppose if the source or the endsystem is in maintenance and is not availabel for the whole day.Now a days, it should be really a very rare scenario where a system goes down for an entire day for maintenance. 2-3 hours maintenance window is normal. If in your case, long maintenance windows are normal and frequent then I would suggest to change the design. Instead of polling remote system, let remote system push the files to OSB server (may be on JMS or any other persistent destination) and then even if remote system goes down it won't affect OSB.
As far enabling and disabling proxy services are concerned, you may handle it through scripts or java API's -
https://blogs.oracle.com/ateamsoab2b/entry/automatic_disabling_proxy_service_when
http://orasoa.blogspot.in/2011/05/disable-and-enable-osb-proxy-services.html
still no other choice?If most of the maintenance windows are scheduled then it is easy to handle the scenario with manual enable/disable of proxy services, but if mostly it is unscheduled then changing the solution design seems better option.
Regards,
Anuj -
WebClient Error - Failed to log on to the comm. mgmt. software
Hi, following the CR410 i have created a webclient profile/ framework, and assigned the profile to an org unit.
now when try to open the webclient using crm_ic, i am getting the above error on the IDES system.
<b>"Failed to log on to the communication management software system"</b>
<b>Details of the above error</b>
Diagnosis
An error occurred while logging in to the communication management software system.
System Response
The multichannel services are not available. You will not be able to work with contacts such as phone calls, e-mails, or chat sessions.
Procedure
Contact your system administrator.
Procedure for System Administration
Review the ICI trace.
what could be error...
Thanks,Have you configured CTI with IC WebClient? If yes under IC WebCLient profile look for CONTACTCENTER function profile and enter correct profile.
If you do not have CTI in place make sure that CONTACTCENTER entry is blank under IC WebClient profile.
Thanks,
Thirumala. -
Error 1017 received logging on to the standby
Hi anyone,
Please help me...
i have database running on Oracle 10gR1 EE (10.1.0.4.0) on Linux Red Hat. and this server is replicate to DR server for backup. we change 'SYS' password about a week ago and nothing occur until today, the database is not connecting to DR server. here is the error obtain from the alert_log file. is there i 've missed anything when changing SYS password?
somebody please help me.. im in horror now.
thanks in advance.
-Nonieforgot to paste the error.
Mon Jan 21 14:54:20 2008
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
It may be necessary to define the DB_ALLOWED_LOGON_VERSION
initialization parameter to the value "10". Check the
manual for information on this initialization parameter.
-Nonie -
Oracle error 1012 ("Not Logged On") & AUTOTRAN=Y
Hi.
I have a problem trying to access an Oracle 8.0.6
database from a 6.5 Tuxedo server.
Both TMS and server execute tpopen correctly
All services are declared as AUTOTRAN
Everything seems to be OK according to the logsgenerated by Oracle XA libraries
However, I always get the Oracle error 1012 ("Not Logged On")
when executing SQL statements from my pro*C server.
I just can't figure out why this error occurs.
I also tried to explicitly open a transaction from the client,
but the result is exactly the same (tpbegin is successfull,
however).
Could someone help me to make this work ?
Thanks.Solved by removing "DB=<db>" from my OPENINFO string, as far as this parameter
should only be used when using proc*C "EXEC SQL ... AT <db>" statements.
"Mathieu Chauvin" <[email protected]> wrote:
>
Hi.
I have a problem trying to access an Oracle 8.0.6
database from a 6.5 Tuxedo server.
Both TMS and server execute tpopen correctly
All services are declared as AUTOTRAN
Everything seems to be OK according to the logsgenerated by Oracle XA libraries
However, I always get the Oracle error 1012 ("Not Logged On")
when executing SQL statements from my pro*C server.
I just can't figure out why this error occurs.
I also tried to explicitly open a transaction from the client,
but the result is exactly the same (tpbegin is successfull,
however).
Could someone help me to make this work ?
Thanks. -
Error reading job logs of Apps server from Central Instance
Dear Gurus,
We have newly installed system with one CI ( cluster environment) and 2 application Instances.
Systems are recently installed by other team. I am looking into support part after handover.
We have noticed below error while reading failed background job logs from our CI. If suppose any job is failing, we can read respective job log from that application instance but it throws error while reading job log from CI to either of application instance.
I checked /sapmnt/SID/global is shared among all 3 servers and i am successfully able to "Touch a" from applications instances.
Even though i have given "777" permissions to all folders like /sapmnt/SID , /sapmnt/SID/global , /sapmnt/SID/global/400JOB*
I am not able to read job log from CI , for same failed job I can read job log from respective application instance.
Error log :
Error reading job log JOBLGX00080700X39290
Message no. BT167
Diagnosis
The background processing system was unable to read the job log named in the message.
This message suggests that there is a problem with the TEMSE storage system of the SAP system. The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.
This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:
Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
A CRON (or equivalent scheduler) job has deleted the TEMSE file.
The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.
SM21 logs :
Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global
BP_JOBLOG_SHOW: Failed to display jobs. Reason:
> Error reading job log JOBLGX00080700X39290
Strange this is I can check failed job log on one application instance frfom other application instance but not from CI.
Kindly throw some lights where to check.
Regards,Hi Shravan,
I guess it is related to permission to /sapmnt/SID/global folder. Please ensure owner is sidadm:sapsys in all the systems viz CI, App servers etc.
Check the mounting options are correctly set with read/write mode.
Hope this helps.
Regards,
Deepak Kori -
HI all,
this is not a security query, but I need help in this regard.
Following error msg i showing in system log. I'm getting this error whenever i'm trying to read the Job in SM37. And in some cases I'm unable to see the spool list which is generated by the bg jobs. what coul be the reason?
<b>> Error reading job log JOBLGX15165600X64603
Error 2 for write/read access to a file. File = /usr/sap/PRD/SYS/global/999JOBLG/0001X15165600X64603
BP_JOBLOG_SHOW: Failed to display jobs. Reason:</b>Thanks Jose
Porblem is solved.
/sapmnt/PRD/global and profile are not mounted on that server.
Thnak u so much for ur cooperation.
Regards,
Raja
Maybe you are looking for
-
ZapfDingbats no longer working in FM7.2
Hi everyone, (FM7.2, Windows XP SP3) I have a strange problem with my ZapfDingbats font that I hope someone can help me with. I recently upgraded my laptop to a Dell Latitude E6500, and installed both FM7.2 and FM8.0 on it, along with all my usual ap
-
Search help in output(using alvgrid function module)
HEllo Experts, I hav developed report using ALV grid function module, now my req is I need to provide the search help for particular field in the output. my output contains .MATNO, PLANT AND STORAGE LOCATION. Now based on mat and plant I need to
-
So I don't know whether to buy an iPad or a Macbook Pro. In the next year I will be:- Doing the final year of my Musical Theatre course (Research, email, the odd written document every so often) Travelling to Germany for a fortnight
-
All audio tracks disappeared form the Timeline, but audio still works
Hi there. I've been using Premiere for quite a while (I still have the 2.0 version), but this problem never occured before. I'm running Premiere on Win Vista. I've been working on a project for a few weeks and eventually I got a version that was more
-
Hello, I have a project that has a small distribution network and can draw splines about the amount of power the consumers and producers consume and produce. This works. Now I want to let a thread "scout" the entire network, searching for producers a