Help please, Asterisk segfaults repeatedly

Dear Allstar Community,

I’m having a huge problem with a fairly recent node install. It’s on one of my remote repeater sites and I’m having continual segfaults from Asterisk. I was hoping perhaps someone could give a little (or a lot) of help with this cos I’m stuck!

The system is running on a mini PC with 2 nodes via USB devices connected.

Here is the text of the error from messages file in /var/log/:

Aug 16 07:25:13 Dundry kernel: [34759.999283] asterisk[32339]: segfault at 4 ip 080b6d97 sp b4afd150 error 4 in asterisk[8048000+12b000]
Aug 16 07:26:32 Dundry kernel: [34839.061366] asterisk[32425]: segfault at 4 ip 080b6d97 sp b4aee150 error 4 in asterisk[8048000+12b000]
Aug 16 07:28:37 Dundry kernel: [34963.251953] asterisk[32562]: segfault at 4 ip 080b6d97 sp b4a68150 error 4 in asterisk[8048000+12b000]
Aug 16 07:32:08 Dundry kernel: [35174.976156] asterisk[32740]: segfault at 4 ip 080b6d97 sp b4a6e150 error 4 in asterisk[8048000+12b000]

You can see the timestamps are fairly close, this is because there was a QSO on the repeater at this time. Activity from repeater users seems to cause this problem. !! This repeater is permanently linked to others, one hosted on the same node and a couple of others that are on other sites, linked by the internet. One of these has a static IP and is in the nodes list of both nodes.

The segfault causes asterisk to restart (succesfully) but of course, all the links are dropped (they are in the startup macro to re-link so do get re-established after a few seconds).

Also, on occasions, the node with the segfault issue will “get stuck” with all the linked repeaters transmitting continuously. A manual restart of asterisk cures this but in the hot weather here in the UK recently, this caused the death of one of the TX PA’s on the repeater!

I’d be really grateful for any help in tracking this issue down, as I have run out of talent and my only option is to re-build from scratch which is a last resort really!

Thanks in advance for any assistance received!

73,
Matt G4RKY
Frys Hill Repeater Group.

Matt,
I suggest you post the following information:
Host hardware (Pi? PC?)
RAM
Storage and type
OS Version
Version of asterisk

Hi and thanks for the reply, sorry for missing the info off my request!

Host hardware is a Lenovo PC
4Gb RAM
Storage is an 80Gb HDD
OS Version is Debian version 6.3 (built from the standard Allstarlink image)
AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version 004b9dd

73,
Matt G4RKY

Matt,
Since you have other servers running I have to assume there is nothing different in the software. ASL 1.01 is around 4 years old, you might want to consider moving to a newer version. ASL 2.x beta is available and can be run on newer version of the OS. I know this could be painful, but ASL 1.01 is or should be at end of life. IMHO

Hi there,

Many thanks for your replies, today I have installed the 2.0 Beta.

Keeping my fingers crossed that the segfault issue is gone, so far its looking good.

I’ve an issue with courtesy tones with the beta which is really strange but I’ll start a new thread about that as its a totally different issue.

Thanks again,

73,
Matt
G4RKY

I have the same issue and I using de Beta 2, that’s only happen in AMD version
Jan 22 09:24:24 repeater kernel: [ 2822.929712] asterisk[15602]: segfault at c8 ip 00007fa26680d118 sp 00007fa26428b2a0 error 4 in app_rpt.so[7fa266800000+39000]
Jan 22 09:24:24 repeater kernel: [ 2822.929722] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 39 ff ff 48 89 df e8 b2 31 ff ff e8 0d 31 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 a9 14 03 00 48 8d 0d 4a 48 03 00
Jan 22 09:24:26 repeater kernel: [ 2825.234788] asterisk[15617]: segfault at c8 ip 00007fa26680d118 sp 00007fa26428b2a0 error 4 in app_rpt.so[7fa266800000+39000]
Jan 22 09:24:26 repeater kernel: [ 2825.234798] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 39 ff ff 48 89 df e8 b2 31 ff ff e8 0d 31 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 a9 14 03 00 48 8d 0d 4a 48 03 00

In raspberry don’t

Yep, the Beta2 does that every time it stat posts. One option is to comment the statpost_url= line in rpt.conf. Or use this installer AWIA: Another way to install ASL2 Beta

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.