What does "core dumped" and "Caught Term Signal" mean?



  • Recently I'm seeing these two log entries, what do they mean?

    
    Jun 9 17:54:29	kernel		pid 73695 (pkg), uid 0: exited on signal 11 (core dumped)
    Jun 9 12:06:47	check_reload_status		Syncing firewall
    Jun 9 12:06:47	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] The Rules update has finished.
    Jun 9 12:06:47	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Snort has restarted with your new set of rules...
    Jun 9 12:06:46	kernel		igb1: promiscuous mode enabled
    Jun 9 12:06:44	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Snort START for WAN(igb1)...
    Jun 9 12:06:41	kernel		pid 15956 (snort), uid 0: exited on signal 4
    Jun 9 12:06:41	kernel		igb1: promiscuous mode disabled
    Jun 9 12:06:41	snort	15956	*** Caught Term-Signal
    Jun 9 12:06:41	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Snort STOP for WAN(igb1)...
    Jun 9 12:06:41	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Building new sid-msg.map file for WAN...
    Jun 9 12:06:40	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Enabling any flowbit-required rules for: WAN...
    Jun 9 12:06:29	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Updating rules configuration for: WAN ...
    Jun 9 12:06:29	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Removed 49 obsoleted rules category files.
    Jun 9 12:06:29	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Hide Deprecated Rules is enabled. Removing obsoleted rules categories.
    Jun 9 12:06:23	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Emerging Threats Open rules are up to date...
    Jun 9 12:06:16	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Snort OpenAppID detectors are up to date...
    Jun 9 12:06:10	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] Snort VRT rules file update downloaded successfully
    Jun 9 12:05:00	php		/usr/local/pkg/snort/snort_check_for_rule_updates.php: [Snort] There is a new set of Snort VRT rules posted. Downloading snortrules-snapshot-2980.tar.gz...
    Jun 9 09:55:28	kernel		pid 86083 (pkg), uid 0: exited on signal 11 (core dumped)
    
    

    Seems to be happening around the Snort update check..



  • Bump…



  • Is Google down for you??  ;D

    A core dump means the kernel had a major spasm for some reason and dumped its stack & process list to a file for debugging.  This is not a good thing.

    Caught term signal means that a process received a termination signal to quit.



  • @KOM:

    Is Google down for you??  ;D

    A core dump means the kernel had a major spasm for some reason and dumped its stack & process list to a file for debugging.  This is not a good thing.

    Caught term signal means that a process received a termination signal to quit.

    No I googled it first like I always do but didn't find anything as it relates to pfSense. Thanks for the explanation. I'll watch it and see if it continues..



  • Hi

    I had this today and I am wondering if this is a bug.

    snort 10786 *** Caught Term-Signal

    Is there an issue for this?



  • Actually the explanation above is wrong and misleading. A kernel crash would show a very specific message on the primary console that the kernel couldn't continue its execution with some explanation like "Fatal trap 12: page fault while in kernel mode" and drop you to the kernel debugger on the primary console. This is not what is happening when you encounter a "core dumped" message. This is when a userspace process does something that the kernel doesn't like and gets killed by the kernel. For example the process  tries to divide by zero or it tries to access part of the process memory space that hasn't been yet allocated for it by the kernel. The reasons for "core dumped" vary, sometimes it's a programming error, sometimes it could be a hardware error as well but most of the time those errors happen as a result of programming errors or misconfiguration of the software.