After Freepbx upgrade from 13 to 14, GUI works but says "Cannot connect to asterisk" SOLVED

FreePBX
1

Upgraded from 13 to 14, GUI says can’t connect to asterisks.

When I run fwconsole start:
fwconsole start
Asterisk already running
Running FreePBX startup…
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions…
Setting base permissions…Done
Setting specific permissions…
59264 [============================]
Finished setting permissions
Unable to run Pre-Asterisk hooks, because Asterisk is already running on PID 8122 and has been running for 19 minutes, 37 seconds
Running Asterisk post from Core module
Running Asterisk post from Dahdiconfig module
Running Asterisk post from Endpoint module
Running Asterisk post from Pagingpro module
Running Asterisk post from Restapps module
Starting RestApps Server…
[>---------------------------] 1 sec
Started RestApps Server. PID is 15938
Running Asterisk post from Ucp module
Starting UCP Node Server…
[>---------------------------] 1 sec
Started UCP Node Server. PID is 16010
Running Asterisk post from Vqplus module
Queues Pro is not licensed.
Running Asterisk post from Xmpp module
Starting Chat Server…
[>---------------------------] 1 sec
Started Chat Server. PID is 16225
Running Asterisk post from Zulu module
This product is not licensed

I also get an error that rmsadmin module is broken? I cannot uninstall or install it. Tried in GUI and fwconsole ma

2

Try “fwconsole restart” instead of just ‘start’.

If that gives you an error, reboot the server and start it up again.

On the restart, if you still have trouble, rerun the restart program and post the output.

3

Also, IIRC, rmsadmin is no longer a thing. I think “fwconsole ma uninstall rmsadmin” is the right command.

4

Thanks, rebooting now.

I tried fwconsole ma uninstall rmsadmin, it said uninstall scripts were not found.

5

fwconsole restart
Asterisk not currently running
Running FreePBX shutdown…

Core FastAGI Server is not running
RestApps Server is not running
UCP Node Server is not running
Chat Server is not running
Zulu Server is not running

Stopping Wanrouter for Sangoma Cards
Wanrouter Stopped
Stopping DAHDi for Digium Cards
DAHDi Stopped
Queue Callback Server is not running
Asterisk already running
Running FreePBX startup…
Unable to run Pre-Asterisk hooks, because Asterisk is already running on PID 6031 and has been running for ERROR
Running Asterisk post from Core module
Running Asterisk post from Dahdiconfig module
Running Asterisk post from Endpoint module
Running Asterisk post from Pagingpro module
Running Asterisk post from Restapps module
Starting RestApps Server…
[>---------------------------] 1 sec
Started RestApps Server. PID is 6526
Running Asterisk post from Ucp module
Starting UCP Node Server…
[>---------------------------] 1 sec
Started UCP Node Server. PID is 6607
Running Asterisk post from Vqplus module
Queues Pro is not licensed.
Running Asterisk post from Xmpp module
Starting Chat Server…
[>---------------------------] 1 sec
Started Chat Server. PID is 6936
Running Asterisk post from Zulu module
This product is not licensed

6

No errors, still says it cannot connect. I’m lost.

7

RMSadmin is gone after reboot…

asterisk -r is unable to connect.

8

That is a standard error that is displayed for almost every module. I’ve posted about it before here. Never saw a response.

9

Regardless of error, it’s gone. I still don’t have error messages on why asterisk won’t start…

10

Try “ps auxp 6031” and see what it says.

If your system is starting Asterisk before the fwconsole program starts it, that could cause this problem. Also, the program running owned by ‘root’ could do the same thing.

11

This is output from fwconsole restart:

fwconsole start
Running FreePBX startup…
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions…
Setting base permissions…Done
Setting specific permissions…
59258 [============================]
Finished setting permissions
Running Asterisk pre from Dahdiconfig module
Writing out default Sangoma conf
Starting Wanrouter for Sangoma Cards
Wanrouter Started
DAHDi: Already started
Running Asterisk pre from Firewall module
Running Asterisk pre from Sysadmin module
Running Sysadmin Hooks
Restarting fail2ban
fail2ban Restarted
Updating License Information for 12238780
Checking Vpn server
Starting Asterisk…
[--------------->------------] 2 mins
In Start.class.php line 187:

Unable to connect to Asterisk. Did it start?

start [–pre] [–post] [–skipchown] [–] []…

12

Your post shows it is running. Just apparently not correctly.

ps aux | grep asterisk

Get the PID and kill it.

kill 15 PID

Then fwconsole chown
Then fwconsole restart

13

Obviously not a restart…

14

Browse to Advanced settings and submit the page.

15

I’ve submitted the page but still have the red “Can not connect to asterisk” in the upper right.

16

After submitted the advanced settings page and then refreshing it looks like it’s back up and running!

Thank you.

17

What’s the magic here?

18

Defense against the Dark Arts 101: [FREEPBX-20233] Reinstalling freepbx rpm writes invalid AMI credentials - Sangoma Issue Tracker

2 Likes
19

So I got asterisk connected, thought everything was good. Users can call each other and outbound, however all inbound calls are answered with “Sorry, an error has occurred”.

We are use DHADI with analog lines. Any ideas on what to check?

20

Saw some invalid destinations in the IVR. Fixing them to see if this resolves the issue.