SOLVED Install failed fwconsole not found (2020/16-15 & 13)

[pilot]

I've been running these remarkable systems for more than a decade...

I'm stumped now, and need help -

a new thinkserver and 20 failed installs... Every time I install incrediblepbx, the install proceeds but at the end asterisk doesn't install. "fwconsole: command not found"

I've tried min. centos6 w/13, min. centos7 w/15, and centos7 w/2020.
Same outcome everytime. each time i wipe the drive and install clean centos...and then run the install scripts as described on nerd vittles

Does anyone have an idea of what could be wrong? I'm dead in the water.

 

[tbrummell]

When you install CentOS I'm assuming you do a yum update and insure I'net access is working just fine? Also, is this on hardware (sounds like it) or in a VM? Any chance you can install ESXi and then install a VM? If on hardware, what is the interface name within CentOS? There used to be a problem when the interface wasn't named "eth0", not sure if that's still an issue. Also, the install is logged, it would be helpful to know what fails, and why.

 

[pilot]

Appreciate the reply -

Being installed on local hardware - I have 4 pots lines that will end up in a sangoma card (a royal PITA by itself)

I've followed the recipe per the nerdvittles howto for incrediblepbx2020 on a min. centos7 (v.1908). this starts with yum updates... everything is fine. no errors, everything updates. the ./Incrediblepbx2020.sh script runs, reboots, and then gets run again. In the log files it is evident that on the second pass, when the script calls for fwconsole commands towards the end, they fail. i'll try and pull the logs when i run it again this pm.

i'm going to try now on a new hp box i picked up this morning. maybe there is something wonky with the thinkserver setup (although this machine WAS running a incrediblepbx 13 install... so this is just fanciful thinking on my part. I don't know how to tease out the issue...

I don't know how to answer " If on hardware, what is the interface name within CentOS " - pls. advise, and thank you

 

[wardmundy]

@pilot: You're following this tutorial and starting with a CentOS 7 minimal install. Correct? Install logs are in /root and should tell you what happened.

I'm running a test install on Vultr just to be sure nothing has come unglued. Will report back in about 30 minutes.

 

[pilot]

Hi Ward - appreciate you taking the time this afternoon.
yes... that's the tutorial.
I'm installing again, after renaming to eth0 - will upload logs in 30

 

[wardmundy]

@pilot: We got a successful install on Vultr so it would appear to be a problem with either your hardware or your network connection. The name of the Ethernet interface no longer matters, by the way.

 

[pilot]

Hi Ward -
yes... that's the tutorial.
I'm installing again, after renaming to eth0 - will upload logs in 30

 

[pilot]

@pilot: We got a successful install on Vultr so it would appear to be a problem with either your hardware or your network connection. The name of the Ethernet interface no longer matters, by the way.

appreciate you trying -
i'm going to install on vultr and skip the local hardware i guess....

 

[pilot]

ugh.... it did it again.... another failure... attempt 14....

so i drove home and tried from my home network. i'll be damned - it worked. I have no idea....

thank everyone for helping - i still have no idea what the problem would have been on the network at the office. but we're back up and running... now to configure the sangoma cards

thank you!!

 

[billtech]

Asterisk does not start
Followed Ward's guide http://nerdvittles.com/?p=31290
Tried for both 2020.1 and 2020.2 - same result.

Installed CentOS minimal. Parent is Server 2019 HyperV, child is Gen 2/UEFI, boot from CentOS ISO.
On CentOS install, it shows Eth0. I set it to DHCP.
ifconfig shows Eth0

After install, did yum -y update
cat /etc/*release* shows CentOS 7.7.1908

ran Phase I and then Phase II -- takes about an hour
On login, the update process goes out and gets updates-- seems OK. But Asterisk does not start.

Log file attached

locate fwconsole
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory

 

[wardmundy]

@billtech: There were errors downloading some of the required Asterisk components. I'd suggest you try another platform. Microsoft's Hyper-V reportedly has serious networking issues. VirtualBox runs fine on Microsoft platforms.

Lots of message threads in this forum on hyperv if you're interested.

 

[billtech]

@ward Excellent. I am on network behind Sonicwall. I will exclude the PBX IP from Sonicwall blocking (GAV, CFS, IPS) and re-install I2020. My guess is Sonicwall blocked some of the asterisk code downloads, resulting in incomplete install.

 

[billtech]

Hi Ward, thanks for more ideas. I set static IP on CentOS install. I excluded that IP from our Sonicwall filters. Sonicwall logs don't show any blocks. The installation seems to proceed, but FWconsole (and other?) files are missing. locate fwconsole shows /usr/src/freepbx/amp_conf/bin/fwconsole. fwconsole restart - command not found. Attached is install log.

What is unique: I loaded I2020 in late December and it ran fine. With the Sangoma key revoke, I figured best to just get new source - so started over and went with the newer build 2020.1 -- and I cannot get this one to successfully install. I started looking at the log file, but it is a lot to review as to where the download is failing.

thanks for ideas

 

[wardmundy]

@ward Excellent. I am on network behind Sonicwall. I will exclude the PBX IP from Sonicwall blocking (GAV, CFS, IPS) and re-install I2020. My guess is Sonicwall blocked some of the asterisk code downloads, resulting in incomplete install.

Sorry to say, the only VoIP component with a track record worse than Hyper-V would be SonicWall. Doesn't mean it won't work, but the difficulties are considerable.

 

[billtech]

OK, thanks for info. I will try on different platform/network.