Downloaded 10.13.66-64bit. Did a clean install on brand new hardware. Install completed successfully. Rebooted, logged in as root, and got this:
** CRITICAL SYSTEM ERROR **
Unable to generate MOTD.
The /usr/sbin/fwconsole file is not accessible
You are likely to experience significant system issues.
Sure enough, /usr/sbin/fwconsole does not exist.
# locate fwconsole
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory
The amportal binary is just as “not there” as the fwconsole binary. I see no way that a clean install would put things in the wrong place. Something is badly wrong with the install.
According to http://wiki.freepbx.org/display/PPS/Installing+FreePBX+Official+Distro , following the installation, the machine should reboot and then install a few additional packages (step 11). This never happens; it just restarts and goes straight to the login prompt. This is a completely clean install, the installer wipes the HD and uses all space.
I’m in the process of re-downloading & re-burning the installer image. Hopefully that will fix the problem…though it’s disturbing that the installer never threw an error of any sort, yet the installed system obviously doesn’t work.
It seems to me that we’ve seen this before - there was a similar incident where the installer quietly failed on a download (??? I’m trying to remember) and the system proceeded on as if it knew what it was doing.
When I use dd or rufus to burn the USB image to a USB thumb drive, the machine won’t boot to it–no OS found. When I use rufus to burn the ISO image to the same thumb drive, it boots fine, runs the install with no errors, but results in a corrupt install.
The file /usr/sbin/fwconsole is a symlink to /var/lib/asterisk/bin/fwconsole. You could try manually creating the symlink, but there may be other things missing that are not so obvious.
# updatedb
# locate fwconsole
/usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole
/usr/src/freepbx-13.0.151/amp_conf/htdocs/admin/modules/framework/amp_conf/bin/fwconsole
# /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole chown
PHP Warning: include_once(/etc/asterisk/freepbx.conf): failed to open stream: No such file or directory in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 13
PHP Warning: include_once(): Failed opening '/etc/asterisk/freepbx.conf' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 13
PHP Warning: include(/var/www/html/admin/libraries/FWApplication.class.php): failed to open stream: No such file or directory in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 68
PHP Warning: include(): Failed opening '/var/www/html/admin/libraries/FWApplication.class.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 68
PHP Warning: include(/var/www/html/admin/libraries/FWHelper.class.php): failed to open stream: No such file or directory in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 69
PHP Warning: include(): Failed opening '/var/www/html/admin/libraries/FWHelper.class.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 69
PHP Warning: include(/var/www/html/admin/libraries/FWList.class.php): failed to open stream: No such file or directory in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 70
PHP Warning: include(): Failed opening '/var/www/html/admin/libraries/FWList.class.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 70
PHP Fatal error: Class 'FreePBX' not found in /usr/src/freepbx-13.0.151/amp_conf/bin/fwconsole on line 77
OK…“same thumb drive” triggered the thought, why don’t I try a different thumb drive. Working on that now, hopefully this will work.
Nope. Same issue. The USB image still results in a non-bootable thumb drive. Not sure what to make of it.
So, since I apparently have a relatively working install of the CentOS underpinnings, is there a magic command I can run to kick off a proper FreePBX install on top of it?
So…I’ve burned the USB .img to a couple different USB sticks, four different ways (Rufus and Win32DiskImager on Win 10, dd and Etcher on macOS), and I have yet to obtain a bootable USB stick.
Now, if I burn the .iso file instead, either stick is bootable, but I end up with a half-baked system.
I even tried the FreePBX beta .iso, since it says it’ll work on pretty much any installation media. That image will boot to the grub prompt, but then it can’t find the kernel.
I’m already running FreePBX on another machine, an old piece of crap, but I’m trying to install it on brand new hardware so we can have a nice snappy system. I’ve installed all kinds of OSen on all sorts of hardware using all types of install media, but apparently I’ve now met my match.
It’s not a network issue, that’s all there. What I’m running into is this:
Burning the .img image to USB results in a non-bootable USB drive. The BIOS doesn’t see any bootable partition at all.
Burning the .iso image to USB boots & installs with no errors, but results in a horked system.
Maybe it’s the brand-new Lenovo 90BG hardware that’s the real problem, I don’t know. But I’ve tried every combination of USB-burning tool and trick I can think of, and nothing works. The “horked” system is running just fine, as far as the base OS is concerned:
# uname -a
Linux cq-pbx 2.6.32-642.6.2.el6.x86_64 #1 SMP Wed Oct 26 06:52:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I can ssh into it, network’s fine, everything’s hunky dory–but no FreePBX.
This is looks exactly the same as the upgrade bug that caused some systems to update partway from FreePBX 12 to FreePBX 13 if you had automatic updates set to yes.
Pretty sure this is an issue with UEFI vs. legacy BIOS, maybe on this particular Lenovo hardware. If I disable UEFI, I can boot off of the .iso image (burned to USB using Rufus), but it gets to a blue screen and hangs. If I enable UEFI (which is how it’s been configured so far), I get the results described above. The base OS appears to be fully functional, and apparently FreePBX is on the drive but not configured, because Asterisk seems to be completely missing.
UEFI doesn’t work all that well on our CentOS 6 distro. It sounds like you’ll have to use our SNG7 distro, or, boot from a physical DVD and not let it use UEFI.
Finally got it running on the Lenovo hardware. Lessons learned:
Don’t even try using UEFI. Turn it off, force the BIOS into legacy mode. Linuxen still prefer yesterday’s hardware.
Don’t even try installing off of a USB stick. Burn a DVD. Even the SNG7 distro doesn’t really like USB.
Yeah, I know, there are ways around both issues, and that’s a great pursuit for folks who aren’t time constrained to get FreePBX running and operational. If you’re like me, though, learn from my mistakes and save yourself the grief!
