{SOLVED} Weird! (Strange Things)

Ok, need some help please… for the last couple of weeks, my pbx will just go offline, I can still use the website to manage it, but ALL the phones show “No Service” no calls in or out. not even ext to ext. “Fast busy” I looked in the log files and the only message I could see for the time frame was “Asterisk uncleanly ending” I’m not sure what info I can post to start this thread so I’ll start with the basics…

PBX Firmware:10.13.66-13
PBX Service Pack:1.0.0.0

I restart my PBX every morning using cron job. so it’s not like it is been up too long, I also do these every morning just to make sure everything should be "fresh"
0 5 * * * /sbin/shutdown -r now
30 5 * * * chmod 755 /var/lib/asterisk/bin/fwconsole
35 5 * * * /var/lib/asterisk/bin/fwconsole chown
01 6 * * * /var/lib/asterisk/bin/fwconsole reload

these events are happening at random times so far, once at 12:30 PM or so, once at 1:35 PM and this morning at 8:00 AM, anyone else having anything similar?

Asterisk version?

1 Like

There is never a reason to do that, this is not Windows.

It sounds like Asterisk is crashing, which you can fix with ‘fwconsole start’ - but it should automatically restart after a crash ANYWAY.

Can we have some more details of your machine, as well as your asterisk version please? (Eg, is it a VM, or real hardware, anything unusual about it, etc?)

Current Asterisk Version: 13.9.1

I agree, but at the same time, does it hurt it? I just figured as long as it isn’t hurting it, the daily reboot was a good thing? It is a VM, and I know that isn’t exactly approved, but so was the last one and it didn’t have this issue.

I would upgrade Asterisk to 13.10, which you will get if you upgrade everything to 10.13.66-15.

ok, Is that now under system admin?

ok that’s done, I’ll let you know if it happens again! :slight_smile: thank you Lorne and Rob for your input!

1 Like

happened today as well.

here are the last few lines in the FULL log before the restart, any of this help?

[2016-09-01 10:53:57] WARNING[23712][C-000005d0] channel.c: Exceptionally long voice queue length queuing to Local/[email protected];2
[2016-09-01 10:53:58] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 10:53:58] WARNING[23712][C-000005d0] channel.c: Exceptionally long voice queue length queuing to Local/[email protected];2
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] bridge_channel.c: Channel SIP/sip0000001_baseamx-000013e4 left ‘simple_bridge’ basic-bridge <059dc210-2390-4439-b589-cf144e385adf>
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Spawn extension (ext-queues, 1111, 40) exited non-zero on ‘SIP/sip0000001_baseamx-000013e4’
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Executing [[email protected]:1] Macro(“SIP/sip0000001_baseamx-000013e4”, “hangupcall,”) in new stack
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Executing [[email protected]:1] GotoIf(“SIP/sip0000001_baseamx-000013e4”, “1?theend”) in new stack
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2016-09-01 10:53:58] VERBOSE[23712][C-000005d0] bridge_channel.c: Channel Local/[email protected];1 left ‘simple_bridge’ basic-bridge <059dc210-2390-4439-b589-cf144e385adf>
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Executing [[email protected]:3] ExecIf(“SIP/sip0000001_baseamx-000013e4”, “0?Set(CDR(recordingfile)=)”) in new stack
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Executing [[email protected]:4] Hangup(“SIP/sip0000001_baseamx-000013e4”, “”) in new stack
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] app_macro.c: Spawn extension (macro-hangupcall, s, 4) exited non-zero on ‘SIP/sip0000001_baseamx-000013e4’ in macro ‘hangupcall’
[2016-09-01 10:53:58] VERBOSE[23673][C-000005d0] pbx.c: Spawn extension (ext-queues, h, 1) exited non-zero on ‘SIP/sip0000001_baseamx-000013e4’
[2016-09-01 10:53:59] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 10:54:00] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 10:54:02] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 10:54:02] WARNING[2231] chan_sip.c: Autodestruct on dialog ‘[email protected]:5060’ with owner SIP/228-00001401 in place (Method: BYE). Rescheduling destruction for 10000 ms
[2016-09-01 10:54:02] VERBOSE[2231][C-000005de] netsock2.c: Using SIP RTP CoS mark 5
[2016-09-01 10:54:03] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 10:54:04] WARNING[24129][C-000005da] channel.c: Exceptionally long voice queue length queuing to Local/FMGL-7141505#@from-internal-000003e8;2
[2016-09-01 11:03:02] VERBOSE[2020] asterisk.c: Remote UNIX connection
[2016-09-01 11:03:02] VERBOSE[25864] asterisk.c: Remote UNIX connection disconnected
[2016-09-01 11:03:02] VERBOSE[2020] asterisk.c: Remote UNIX connection
[2016-09-01 11:03:02] VERBOSE[25866] asterisk.c: Remote UNIX connection disconnected
[2016-09-01 11:05:28] VERBOSE[2014] asterisk.c: Asterisk uncleanly ending (0).

Seems worse today, already had to restart the server twice… UGH!!!

This is a network error. It’s possibly because your DNS server is playing up. Make sure that your DNS points to 127.0.0.1 first (which is a local, superfast, DNS cache) - this is configured in Sysadmin.

127.0.0.1 is the first one…

Well, that error means that Asterisk hasn’t had a chance to process any traffic for a (relatively) long period of time, and there’s a lot of traffic that’s backed up.

Normally that’s a DNS issue, as doing a DNS lookup can lock up asterisk while it waits for a timeout. It can also be a hardware issue, OR virtual machine issue. You’re going to have to do some in-depth investigating.

The easiest way to solve it is to just do a backup, build a new machine, and restore the backup to the new machine. Whatever is broken on the other machine hopefully won’t follow it 8)

127.0.0.1 is the first one…

You can also validate it’s not DNS by making sure that’s the ONLY one.

I made it the ONLY one, and I’ll see if it gets better, Thanks Rob for the info… still wet behind the ears with this… :slight_smile:

1 Like

I think you’ll need to restart asterisk after that change, just to make sure it’s picked it up. (log into the machine and run asterisk -rx 'core restart now')

I’ll have to wait until it dies again before I restart. production server… :frowning:

with the 127.0.0.1 as the only DNS server my SIP trunks would not register, so this may have been the cause of the issue? I put back my real DNS servers in there, and took out the 127.0.0.1, obviously the local DNS isn’t working?

Just an update, haven’t seen the issue since the DNS change. Is there a setup to get local DNS working? mine apparently isn’t?