Is this an issue? syslog-ng uid 0 exited on signal 6 (core dumped)

[adamgoldberg]

On a new installation, running for a two days, I got an email this morning that included this:

Code:

> epair0b: Ethernet address: 02:e3:b8:00:09:0b
> pid 2202 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> arp: 192.168.55.26 moved from 00:0d:c5:bd:ee:56 to 00:0d:c5:bd:ee:55 on epair0b

Is this normal, that syslog-ng exited with a core dump? Or indicative of some problem somewhere?

Show : Full text of email from "security run output"

freenas.local kernel log messages:
> Copyright (c) 1992-2014 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.3-RELEASE-p31 #0 r288272+33bb475: Wed Feb 3 02:19:35 PST 2016
> root@build3.ixsystems.com:/tank/home/stable-builds/FN/objs/os-base/amd64/tank/home/stable-builds/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
> gcc version 4.2.1 20070831 patched [FreeBSD]
> CPU: Intel(R) Xeon(R) CPU E31230 @ 3.20GHz (3200.10-MHz K8-class CPU)
> Origin = "GenuineIntel" Id = 0x206a7 Family = 0x6 Model = 0x2a Stepping = 7
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> Features2=0x1dbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,OSXSAVE,AVX>
> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
> AMD Features2=0x1<LAHF>
> TSC: P-state invariant, performance statistics
> real memory = 17985175552 (17152 MB)
> avail memory = 16489590784 (15725 MB)
> Event timer "LAPIC" quality 600
> ACPI APIC Table: <SUPERM SMCI--MB>
> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
> FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> cpu2 (AP): APIC ID: 2
> cpu3 (AP): APIC ID: 3
> cpu4 (AP): APIC ID: 4
> cpu5 (AP): APIC ID: 5
> cpu6 (AP): APIC ID: 6
> cpu7 (AP): APIC ID: 7
> WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
> ACPI Warning: FADT (revision 5) is longer than ACPI 5.0 version, truncating length 268 to 256 (20111123/tbfadt-325)
> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> kbd1 at kbdmux0
> cryptosoft0: <software crypto> on motherboard
> aesni0: No AESNI support.
> padlock0: No ACE support.
> acpi0: <SUPERM SMCI--MB> on motherboard
> acpi0: Power Button (fixed)
> acpi0: reservation of 67, 1 (4) failed
> cpu0: <ACPI CPU> on acpi0
> cpu1: <ACPI CPU> on acpi0
> cpu2: <ACPI CPU> on acpi0
> cpu3: <ACPI CPU> on acpi0
> cpu4: <ACPI CPU> on acpi0
> cpu5: <ACPI CPU> on acpi0
> cpu6: <ACPI CPU> on acpi0
> cpu7: <ACPI CPU> on acpi0
> hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
> Timecounter "HPET" frequency 14318180 Hz quality 950
> Event timer "HPET" frequency 14318180 Hz quality 550
> atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
> atrtc0: Warning: Couldn't map I/O.
> Event timer "RTC" frequency 32768 Hz quality 0
> attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
> ugen1.3: <Kingston> at usbus1
> umass0: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 3> on usbus1
> umass0: SCSI over Bulk-Only; quirks = 0x4000
> umass0:7:0:-1: Attached to scbus7
> ums0: error reading report description
> device_attach: ums0 attach returned 12
> da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
> ada0: <ST2000DM001-1CH164 CC24> ATA-8 SATA 3.x device
> cd0 at ahcich5 bus 0 scbus5 target 0 lun 0
> cd0: <TSSTcorp CDDVDW SN-208BB SB00> Removable CD-ROM SCSI-0 device
> cd0: Serial Number R8FH6GLB819259
> cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
> cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #3 Launched!
> Timecounter "TSC-low" frequency 1600047916 Hz quality 1000
> vboxdrv: fAsync=0 offMin=0x316 offMax=0xe2f
> epair0a: Ethernet address: 02:e3:b8:00:08:0a
> epair0b: Ethernet address: 02:e3:b8:00:09:0b
> pid 2202 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> arp: 192.168.55.26 moved from 00:0d:c5:bd:ee:56 to 00:0d:c5:bd:ee:55 on epair0b

freenas.local login failures:
Feb 9 11:33:40 freenas sshd[8799]: Failed password for root from 192.168.55.47 port 63944 ssh2

-- End of security output --

 

[dlavigne]

Known bug being investigated: https://bugs.freenas.org/issues/11213.

 

[adamgoldberg]

I get a 403 - You are not authorized to access this page on that link, and if I look at the list of open bugs for FreeNAS 9, that issue number doesn't show up on the list.

 

[dlavigne]

Bummer. It looks like it is marked private as the original submitter uploaded their debug (which may contain private info). Here is the latest status on that ticket:

So updating syslog-ng ended up not fixing anything. I have been able to determine that:
It's caused by writes to /var/log/messages after the system boots, when the dmesg output is dumped to the logger. It's almost certainly related to our size bump of the dmesg buffer. It's also mostly harmless, as it's just the worker thread for /var/log/messages, which is instantly restarted by the main process.

 

[adamgoldberg]

Ok, yea, I figured it was some sort of innocuous bug where the process is restarted automatically, but thanks for the info.