Service Freeswitch wouldn't start

Status
Not open for further replies.
Lorena Watkins

Lorena Watkins

Member
Feb 5, 2021
52
4
8
55
Hi..I was trying to fix a 502 Bad Gateway error, and changed files /etc/nginx/nginx.conf and /etc/php/7.3/fpm/pool.d/www.conf by following this post:

https://www.pbxforums.com/threads/nginx-504-gateway-time-out.4383/#post-19554 without success.

I also tried changing in /etc/ngingx/fusionpbx file, the value unix:/var/run/php5-fpm.sock to unix:/var/run/php/php7.1-fpm.sock under fastcgi_pass section, also without success

I then stopped service freeswitch to see if this could fix the problem, and when I tried to start it woulnd't :eek:.

When I type service freeswitch start, I get:

Job for freeswitch.service failed. See 'systemctl status freeswitch.service' and 'journalctl -xn' for details.

This is the result of "systemctl status freeswitch.service":

freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled)
Active: failed (Result: start-limit) since Fri 2021-06-11 23:13:20 AST; 1min 58s ago
Process: 1676 ExecStart=/usr/bin/freeswitch -u www-data -g www-data -ncwait $DAEMON_OPTS (code=exited, status=203/EXEC)
Process: 1673 ExecStartPre=/bin/chown -R www-data:www-data /var/run/freeswitch/ (code=exited, status=0/SUCCESS)
Process: 1670 ExecStartPre=/bin/mkdir -p /var/run/freeswitch/ (code=exited, status=0/SUCCESS)

Jun 11 23:13:20 SERVER-NAME systemd[1]: Failed to start freeswitch.
Jun 11 23:13:20 SERVER-NAME systemd[1]: Unit freeswitch.service entered failed state.
Jun 11 23:13:20 SERVER-NAME systemd[1]: freeswitch.service holdoff time over, scheduling restart.
Jun 11 23:13:20 SERVER-NAME systemd[1]: Stopping freeswitch...
Jun 11 23:13:20 SERVER-NAME systemd[1]: Starting freeswitch...
Jun 11 23:13:20 SERVER-NAME systemd[1]: freeswitch.service start request repeated too quickly, refusing to start.
Jun 11 23:13:20 SERVER-NAME systemd[1]: Failed to start freeswitch.
Jun 11 23:13:20 SERVER-NAME systemd[1]: Unit freeswitch.service entered failed state.

This is the result of "journalctl -xn":

-- Logs begin at Sat 2021-06-12 20:31:03 AST, end at Fri 2021-06-11 23:17:01 AST. --
Jun 11 23:13:20 SERVER-NAME systemd[1]: Starting freeswitch...
-- Subject: Unit freeswitch.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit freeswitch.service has begun starting up.
Jun 11 23:13:20 SERVER-NAME systemd[1]: freeswitch.service start request repeated too quickly, refusing to start.
Jun 11 23:13:20 SERVER-NAME 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.
Jun 11 23:13:20 SERVER-NAME systemd[1]: Unit freeswitch.service entered failed state.
Jun 11 23:15:01 SERVER-NAME CRON[1678]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 11 23:15:01 SERVER-NAME CRON[1679]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun 11 23:15:01 SERVER-NAME CRON[1678]: pam_unix(cron:session): session closed for user root
Jun 11 23:17:01 SERVER-NAME CRON[1682]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 11 23:17:01 SERVER-NAME CRON[1683]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 11 23:17:01 SERVER-NAME CRON[1682]: pam_unix(cron:session): session closed for user root

I appreciate your help, thanks in advance
 
Lorena Watkins

Lorena Watkins

Member
Feb 5, 2021
52
4
8
55
1) I reverted all the changes I did to the files: /etc/nginx/nginx.conf and /etc/php/7.3/fpm/pool.d/www.conf

2) Then restarted nginx and php7.0-fpm services

And when I tried to restart freeswitch I get the same error.

Result of journalctl -xn command:

-- Logs begin at Sat 2021-06-12 20:31:03 AST, end at Sat 2021-06-12 10:57:48 AST

Jun 12 10:57:48 VOIP-SERVERsystemd[2897]: Failed at step EXEC spawning /usr/bin

-- 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 while executing this process is 2.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service: control process exit

Jun 12 10:57:48 VOIP-SERVERsystemd[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.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Unit freeswitch.service entered failed s

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service holdoff time over, sc

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Stopping freeswitch...

-- Subject: Unit freeswitch.service has begun shutting down

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit freeswitch.service has begun shutting down.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Starting freeswitch...

-- Subject: Unit freeswitch.service has begun with start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit freeswitch.service has begun starting up.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service start request repeate

Jun 12 10:57:48 VOIP-SERVERsystemd[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.

lines 1-39...skipping...

-- Logs begin at Sat 2021-06-12 20:31:03 AST, end at Sat 2021-06-12 10:57:48 AST. --

Jun 12 10:57:48 VOIP-SERVERsystemd[2897]: 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 while executing this process is 2.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service: control process exited, code=exited status=203

Jun 12 10:57:48 VOIP-SERVERsystemd[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.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Unit freeswitch.service entered failed state.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service holdoff time over, scheduling restart.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Stopping freeswitch...

-- Subject: Unit freeswitch.service has begun shutting down

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit freeswitch.service has begun shutting down.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Starting freeswitch...

-- Subject: Unit freeswitch.service has begun with start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit freeswitch.service has begun starting up.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: freeswitch.service start request repeated too quickly, refusing to start.

Jun 12 10:57:48 VOIP-SERVERsystemd[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.

Jun 12 10:57:48 VOIP-SERVERsystemd[1]: Unit freeswitch.service entered failed state.

~

I also notice the file /usr/bin/freeswitch doesn't exists
 
Status
Not open for further replies.
Top Bottom