McAfee application stops running with a crash seen in the serial0_YYYYMMDD log file

book

Article ID: 167964

calendar_today

Updated On:

Products

XOS

Issue/Introduction

McAfee application stops running with a crash seen in the serial0_YYYYMMDD log file
  • McAfee VAP stops running and only comes up after the module is reloaded
  • In addition, a crash is seen (sample below) in the serial0-YYYYMMDD- logs around the time the application stopped running:
----------------------------------------serial0_20130618-060716--------------------------------------------------------- 
2013-07-03 07.52.54:<: ad0: TIMEOUT - WRITE_DMA retrying (5 retries left) LBA=5197104 
2013-07-22 22.14.04:<: kernel trap 12 with interrupts disabled <<<<<<<<<<<<<<<<<<<<<<<<<<<< 
2013-07-22 22.14.04:<: 
2013-07-22 22.14.04:<: 
2013-07-22 22.14.04:<: Fatal trap 12: page fault while in kernel mode <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 
2013-07-22 22.14.04:<: cpuid = 0; apic id = 00 
2013-07-22 22.14.04:<: fault virtual address^I= 0x20 
2013-07-22 22.14.04:<: fault code^I^I= supervisor read data, page not present 
2013-07-22 22.14.04:<: instruction pointer^I= 0x20:0xffffffff804ac268 
2013-07-22 22.14.04:<: stack pointer^I = 0x28:0xffffff813454b5f0 
2013-07-22 22.14.04:<: frame pointer^I = 0x28:0xffffff813454b620 
2013-07-22 22.14.04:<: code segment^I^I= base 0x0, limit 0xfffff, type 0x1b 
2013-07-22 22.14.04:<: ^I^I^I= DPL 0, pres 1, long 1, def32 0, gran 1 
2013-07-22 22.14.04:<: processor eflags^I= resume, IOPL = 0 
2013-07-22 22.14.04:<: current process^I^I= 11 (irq268: em4:rx 0) 
2013-07-22 22.14.04:<: trap number^I^I= 12 
2013-07-22 22.14.04:<: panic: page fault 
2013-07-22 22.14.04:<: cpuid = 0 
2013-07-22 22.14.04:<: Uptime: 34d16h4m18s 
2013-07-22 22.14.04:<: Pausing other CPUs 
2013-07-22 22.14.04:<: CPUs paused; starting dump 
2013-07-22 22.14.05:<: Physical memory: 10224 MB 
2013-07-22 22.14.05:<: Dumping 1924 MB: (CTRL-C to abort) 
2013-07-22 22.14.10:<: ^H^H^H^H1909^H^H^H^H1893^H^H^H^H1877^H^H^H^H1861^H^H^H^H1845^H^H^H^H1829^H^H^H^H1813^H^H^H^H1797^H^H^H^H1781^H^H^H^H1765^H^H^H^H1749^H^H^H^H1733^H^H^H^H1717^H^H^H^H1701^H^H^H^H1685^H^H^H^H1669^H^H^H^H1653^H^H^H^H1637^H^H^H^H1621^H
2013-07-22 22.14.54:>: + ^H^H^H1605^H^H^H^H1589^H^H^H^H1573^H^H^H^H1557^H^H^H^H1541^H^H^H^H1525^H^H^H^H1509^H^H^H^H1493^H^H^H^H1477^H^H^H^H1461^H^H^H^H1445^H^H^H^H1429^H^H^H^H1413^H^H^H^H1397^H^H^H^H1381^H^H^H^H1365^H^H^H^H1349^H^H^H^H1333^H^H^H^H1317^H 
2013-07-22 22.15.44:>: + ^H^H^H1301^H^H^H^H1285^H^H^H^H1269^H^H^H^H1253^H^H^H^H1237^H^H^H^H1221^H^H^H^H1205^H^H^H^H1189^H^H^H^H1173^H^H^H^H1157^H^H^H^H1141^H^H^H^H1125^H^H^H^H1109^H^H^H^H1093^H^H^H^H1077^H^H^H^H1061^H^H^H^H1045^H^H^H^H1029^H^H^H^H1013^H 
2013-07-22 22.16.34:>: + ^H^H^H 997^H^H^H^H 981^H^H^H^H 965^H^H^H^H 949^H^H^H^H 933^H^H^H^H 917^H^H^H^H 901^H^H^H^H 885^H^H^H^H 869^H^H^H^H 853^H^H^H^H 837^H^H^H^H 821^H^H^H^H 805^H^H^H^H 789^H^H^H^H 773^H^H^H^H 757^H^H^H^H 741^H^H^H^H 725^H^H^H^H 709^H 
2013-07-22 22.17.23:>: + ^H^H^H 693^H^H^H^H 677^H^H^H^H 661^H^H^H^H 645^H^H^H^H 629^H^H^H^H 613^H^H^H^H 597^H^H^H^H 581^H^H^H^H 565^H^H^H^H 549^H^H^H^H 533^H^H^H^H 517^H^H^H^H 501^H^H^H^H 485^H^H^H^H 469^H^H^H^H 453^H^H^H^H 437^H^H^H^H 421^H^H^H^H 405^H 
2013-07-22 22.18.13:>: + ^H^H^H 389^H^H^H^H 373^H^H^H^H 357^H^H^H^H 341^H^H^H^H 325^H^H^H^H 309^H^H^H^H 293^H^H^H^H 277^H^H^H^H 261^H^H^H^H 245^H^H^H^H 229^H^H^H^H 213^H^H^H^H 197^H^H^H^H 181^H^H^H^H 165^H^H^H^H 149^H^H^H^H 133^H^H^H^H 117^H^H^H^H 101^H 
2013-07-22 22.19.00:>: + ^H^H^H 85^H^H^H^H 69^H^H^H^H 53^H^H^H^H 37^H^H^H^H 21^H^H^H^H 5^H^H^H^H 
2013-07-22 22.19.14:<: Dump complete 
2013-07-22 22.19.14:<: Restarting other CPUs 
2013-07-22 22.19.14:<: Automatic reboot in 15 seconds 
2013-07-22 22.19.29:<: Rebooting... 
2013-07-22 22.19.30:<: cpu_reset: Stopping other CPUs 
 

Cause

If a crash has occurred as found in the Symptom section, it is very likely that McAfee support can examine the crash and application logs to determine the root cause and provide a fix.

Specifically for the case above,
McAfee support determined that the firewall was having issues scanning files for viruses thus causing the HTTP proxy to queue too much data and eventually core, creating the crash info.

 
 
 

Resolution

When a McAfee crash is discovered, please open a case with McAfee Support in parallel for their findings and recommended next steps for this issue.

Workaround

n/a