Freeswitch service does not start

[alaamrim]

Hello everyone, running into strange issue, fresh installation of Fusionpbx for centos 7, its required to use this OS, fusionpbx script installs everything including Freeswtch
However, FreeSwitch does not start, Here are the details:

root@ip-172-31-47-80 centos]# systemctl status freeswitch.service
● freeswitch.service - freeswitch
Loaded: loaded (/etc/systemd/system/freeswitch.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2023-03-15 01:35:09 UTC; 53s ago
Process: 18366 ExecStart=/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait $DAEMON_OPTS (code=exited, status=203/E XEC)
Process: 18365 ExecStartPre=/bin/chown -R freeswitch:daemon /usr/local/freeswitch (code=exited, status=0/SUCCESS)

Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service: control process exited, c...203
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Failed to start freeswitch.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Unit freeswitch.service entered failed state.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service failed.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service holdoff time over, schedul...rt.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Stopped freeswitch.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: start request repeated too quickly for freesw...ice
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Failed to start freeswitch.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Unit freeswitch.service entered failed state.
Mar 15 01:35:09 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service failed.
Hint: Some lines were ellipsized, use -l to show in full.



[root@ip-172-31-47-80 centos]# journalctl -xe
--
-- The result is failed.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Unit freeswitch.service entered failed state.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service failed.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service holdoff time over, scheduling restart.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Stopped freeswitch.
-- Subject: Unit freeswitch.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has finished shutting down.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Starting freeswitch...
-- Subject: Unit freeswitch.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has begun starting up.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[18490]: Failed at step EXEC spawning /usr/bin/freeswitch: No such file or directory
-- Subject: Process /usr/bin/freeswitch could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/freeswitch could not be executed and failed.
--
-- The error number returned by this process is 2.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service: control process exited, code=exited status=203
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Failed to start freeswitch.
-- Subject: Unit freeswitch.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has failed.
--
-- The result is failed.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Unit freeswitch.service entered failed state.
Mar 15 01:38:22 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service failed.
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service holdoff time over, scheduling restart.
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Stopped freeswitch.
-- Subject: Unit freeswitch.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has finished shutting down.
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: start request repeated too quickly for freeswitch.service
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Failed to start freeswitch.
-- Subject: Unit freeswitch.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has failed.
--
-- The result is failed.
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: Unit freeswitch.service entered failed state.
Mar 15 01:38:23 ip-172-31-47-80.us-east-2.compute.internal systemd[1]: freeswitch.service failed.
Mar 15 01:38:26 ip-172-31-47-80.us-east-2.compute.internal dhclient[2810]: XMT: Solicit on eth0, interval 125500ms.


I feel like I am missing something, any help will be appreciated. thanks in advance.

 

[alaamrim]

I noticed the following
User www-data was not created
directory /usr/local/freeswitch/ was not created.

I installed it following the steps on the fusionpbx website:

yum install wget

wget -O - https://raw.githubusercontent.com/fusionpbx/fusionpbx-install.sh/master/centos/pre-install.sh | sh

cd /usr/src/fusionpbx-install.sh/centos && ./install.sh

 

[junction1153]

CentOS is dead. Use Debian 11

 

[alaamrim]

@junction1153 Thanks for your answer, but the requirement I have is to use CentOS. Is the issue related to the OS here?

 

[junction1153]

My best guess is that the install script is not properly installing the components for you. Possibly a bunch of dead CentOS repos causing this. But that’s just a guess.

 

[TimGuyUK]

I never got freeswitch running on Centos 7. At the time Centos 7 was my distro of choice and it just wouldn't work, changed to Debian 9 as was then and it worked out the box with no messing.

 

[alaamrim]

Thanks everyone for taking the time to reply, eventually I convinced the client to stop using Centos and as you guys mentioned all went fine. Thanks everyone will consider this solved