I installed Freepbx 17 on a fpbx60 appliance and although everything seems to work I noticed that mongodb does not start.
systemctl status mongod
Jul 18 12:59:07 pbx systemd[1]: mongod.service: Failed with result ‘signal’.
root@pbx:/root# mongod
Illegal instruction
It seems that Mongodb 7 has requirements for modern CPUs. Would be nice to have a CPU check in the install script to warn you about this.
Unfortunately it does not appear that I can downgrade Mongo to version 4 on a Debian 12 install, too many dependencies missing. People trying to reuse old hardware will run into this problem.
Is Mongodb vital to Freepbx 17? I have been running a test server on a FPBX60 appliance for a few days and I do not see any errors even though Mongodb cannot run in that server due to lack of AVX support. I have several customers running Freepbx 16 on these appliances, some purchased the hardware a couple years ago, and they will scream at me if they cannot upgrade to 17 once 16 is obsolete without buying a new server.
Looking at the open source code the only non-commercial module that used mongo was xmpp. If you aren’t using xmpp and assuming no commercial modules require it you can probably go without.
So basically cannot use the chat for Zulu or Sangoma Connect which are commercial modules. I can certainly live with that. Thank you!
I honestly don’t remember the engine behind zulu and I wasn’t there for Sangoma connect so I don’t know if it uses mongo or not. This may be a good @kgupta question
Hi @cursor
The Sangoma Connect (Talk) and Desktop app chat are working fine on our FreePBX 60 hardware without running the mongod service. Additionally, XMPP and Zulu are not supported on FreePBX V17, so you can ignore the mongod error."
Perhaps mongod should be removed from the install script
Opened a report to evaluate dependencies.
Zulu is EOL and sng connect doesnt rely on mongo nor xmpp module.
So is it safe to just apt purge mongo* on all my FPBX17 servers?
Probably you can purge it - careful of other dependencies of your own however - as mongo is gone-o from the current v17 installer.