uid 0: exited on signal 6 (core dumped)

[gearhead]

I get the following message should I be concerned:

freenas kernel: <6>pid 1694 (syslog-ng), uid 0: exited on signal 6 (core dumped)

 

[Ericloewe]

It's much easier to provide meaningful advice if you give us a lot more details.

 

[DrKK]

I get the following message should I be concerned:

freenas kernel: <6>pid 1694 (syslog-ng), uid 0: exited on signal 6 (core dumped)

So, I've started seeing this myself, on several FreeNAS systems in the 9.3 series.

I don't know what's causing it, but there appears to be no problem with the syslog-ng on any of the systems once they boot up. I have been ignoring this message for several months, will no ill effects.

I once mentioned it to Jordan, he asked me to verify that the syslog-ng was working correctly, which I did, then he said: "meh". So yeah, I think you can safely ignore it.

 

[kknas]

There's a bug report for that: https://bugs.pcbsd.org/issues/7391 . I get the same issue on each boot, but can't see any effects.

 

[benamira]

After updating to the last STABLE version, i get this error.
An also something is broken in the reporting TAB, as it seems to have lost all the historical and some values are not shown. :-(

 

[BigDave]

My machine has been ending with that after every reboot/update for some time, I thought it was
normal...

 

[DrKK]

Yeah, whatever the deal is on this, it's got to be pretty screwy. I remotely administer three nearly identical FreeNAS boxes, in addition to my own box. They are nearly identical---literally the same hardware throughout. Almost identical, modest, configurations. Yet, two of the boxes give this scary-sounding (but ultimately apparently harmless) error after every single boot, and two of the boxes NEVER give this error.

I can't make heads or tails of it.

 

[Chris Moore]

I thought that I would contribute my two cents as it might help to figure out where the problem is.

I have two units NAS1 and NAS2. I have NAS1 doing an rsync to NAS2 every night at midnight and that is the only reason that I could come up with for the following entries:

Code:

Jun 16 00:00:00 T3500_NAS1 syslog-ng[4668]: Configuration reload request received, reloading configuration;
Jun 17 00:00:00 T3500_NAS1 syslog-ng[4668]: Configuration reload request received, reloading configuration;
Jun 18 00:00:00 T3500_NAS1 syslog-ng[4668]: Configuration reload request received, reloading configuration;
Jun 19 00:00:00 T3500_NAS1 syslog-ng[4668]: Configuration reload request received, reloading configuration;
Jun 20 00:00:01 T3500_NAS1 syslog-ng[1714]: Configuration reload request received, reloading configuration;

However, I noticed this entry on the 19th and it concerned me. Perhaps they are related?

Code:

Jun 19 06:09:15 T3500_NAS1 syslog-ng[28888]: syslog-ng starting up; version='3.5.6'
Jun 19 06:09:15 T3500_NAS1 kernel: pid 4668 (syslog-ng), uid 0: exited on signal 6 (core dumped)

The target system for the rsync had this in it's log a few minutes after the error on NAS1 and nothing further until midnight when the next rsync started.

Code:

Jun 19 06:13:00 T3500_NAS2 collectd[2784]: plugin_load: Could not find plugin "zfs_arc_v2" in /usr/local/lib/collectd
Jun 19 06:13:14 T3500_NAS2 syslog-ng[3971]: syslog-ng starting up; version='3.5.6'
Jun 19 06:13:14 T3500_NAS2 kernel: pid 1682 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Jun 20 00:00:00 T3500_NAS2 syslog-ng[3971]: Configuration reload request received, reloading configuration;

I know what happened (for me at least) at 6 am on the 19th is when I loaded the most recent system update.

 

[BigDave]

I have two units NAS1 and NAS2. I have NAS1 doing an rsync to NAS2 every night at midnight and that is the only reason that I could come up with for the following entries:

My Freenas server log has this reading (shown below) at midnight every day. The machine is not sync'd or otherwise "backed up" to any other machine.

Code:

Jun 16 00:00:00 freenas syslog-ng[1866]: Configuration reload request received, reloading configuration;

IDK if this helps or not... Just thought I'd throw that out there.

 

[DrKK]

yeah, every freeNAS box in existence shows that message at midnight.

 

[Chris Moore]

yeah, every freeNAS box in existence shows that message at midnight.

Good to know.