A classic issue which bit me a few weeks ago was that the permissions on the core dump directory changed, preventing asterisk from creating a file?
Also, check the contents of the kernel sysctl that specifies the filename of core dumps - If it contains an absolute path, it will override asterisk's settings. # cat /proc/sys/kernel/core_pattern core.%e Worth a check? Steve On Fri, 22 Jul 2016 at 14:27 Joshua Colp <[email protected]> wrote: > Ross Beer wrote: > > Hi Joshua, > > > > > > There was one instance of this being reported on a ticket I read last > > week. It just strange that on Fedora 23 that this has suddenly stopped > > happening. > > You may have been thinking of ASTERISK-26219[1] which is CentOS 6.8. > > > The previous example shows that the dump was attempted but no files > > created. They were being created for previous versions. > > I've checked the code responsible for setting the parameter when the -g > option or dump_core is set and it hasn't changed. Ultimately it's the > system that creates the core dump, we just change the parameter to raise > the limit on the core dump size. I also did a quick look over the > changes and nothing stood out. > > [1] https://issues.asterisk.org/jira/browse/ASTERISK-26219 > > -- > Joshua Colp > Digium, Inc. | Senior Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - US > Check us out at: www.digium.com & www.asterisk.org > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
