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?
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?)
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.
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.
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 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')
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?