My experience with this is bad ram. If you can find and run ‘memtest86’ or ‘memtest64’, I’d start there. If you find the one from the NetBSD website, it’s a bootable image that you can run that just runs the test.
I’ve only ever had two systems that would randomly restart like this - the first had a bad RAM stick in upper RAM (and would only crash after 30+ hours running) and the second was a config file error in one of my Chan-SCCP-B implementations.
The first one was fixed by replacing the RAM - the system hasn’t auto-restarted in two years.
The second one included a message from the author of the channel driver that basically said “How did you set that - it’s impossible to do that.”
Since this is a new install, I’d recommend a memtest first.
I found the data in the release notes for Asterisk 13.10.
Here’s what I was seeing on the system: Every couple of days I would get reports of lots of people losing calls all at once. When I would check FULL log, I would see that asterisk had restarted itself.
I also started finding core dump files that corresponded to the times when calls dropped.
By way of an update, installing asterisk 13.10 handled the issue.
Here’s what I was seeing on the system: Every couple of days I would get reports of lots of people losing calls all at once. When I would check FULL log, I would see that asterisk had restarted itself.
I also started finding core dump files that corresponded to the times when calls dropped.
Hello Robert. I have the same issue since a couple of weeks ago. (I am using our current version which is 13.9). However, i was cheching the changelog and release version and I cannot see this fix. Can you give me the reference of this issue and how they solved it? Thanks.