The firewall has encountered an error

nasheayahu

Was wonder why I could not connect, had to go to the direct console to repeating messages, after rebooting was directed to view the Crash Reporter and got this:

Crash report begins.  Anonymous machine information:

amd64
12.3-STABLE
FreeBSD 12.3-STABLE RELENG_2_6_0-n226742-1285d6d205f pfSense

Crash report details:

No PHP errors found.

Filename: /var/crash/info.0
Dump header from device: /dev/ada0p3
  Architecture: amd64
  Architecture Version: 4
  Dump Length: 74752
  Blocksize: 512
  Compression: none
  Dumptime: Wed May 11 16:58:38 2022
  Hostname: pfSense.kohanyim.com
  Magic: FreeBSD Text Dump
  Version String: FreeBSD 12.3-STABLE RELENG_2_6_0-n226742-1285d6d205f pfSense
  Panic String: 
  Dump Parity: 2187160421
  Bounds: 0
  Dump Status: good
  ...
  ..
  .

This is a PC Build and below are the generated files. Is it possible for someone to take a look at them to discover the reason why the system crashed so I can fix the problem before it happens again?.

textdump.tar.0 info.0

stephenw10

The backtrace shows:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100014 td 0xfffff800055f7740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe0074779950
vt_kbdevent() at vt_kbdevent+0x16a/frame 0xfffffe00747799b0
kbdmux_intr() at kbdmux_intr+0x3f/frame 0xfffffe00747799d0
taskqueue_run_locked() at taskqueue_run_locked+0x144/frame 0xfffffe0074779a30
taskqueue_run() at taskqueue_run+0x72/frame 0xfffffe0074779a50
ithread_loop() at ithread_loop+0x23c/frame 0xfffffe0074779ab0
fork_exit() at fork_exit+0x7e/frame 0xfffffe0074779af0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0074779af0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

Which is not very helpful.

The message buffer shows Snort crashing out:

<118>Bootup complete
<6>igb0: promiscuous mode enabled
<6>igb1: promiscuous mode enabled
<6>pid 94358 (snort), jid 0, uid 0: exited on signal 11 (core dumped)
<6>pid 94944 (snort), jid 0, uid 0: exited on signal 11 (core dumped)
KDB: enter: manual escape to debugger

There's no time stamp so we can't say if that's related but it certainly shouldn't do that.

Check the System and Snort logs.

Steve

nasheayahu

@stephenw10 said in The firewall has encountered an error:

There's no time stamp so we can't say if that's related but it certainly shouldn't do that.
Check the System and Snort logs.

Okay thanks, I also notified Snort via email....