Freeswitch fails to start in debian 8 lxc container
Hello, I have the following error in a debian 8 container. Any idea how to fix this? Jan 06 15:33:08 jessie systemd[2329]: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted -- Subject: Process /bin/mkdir could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /bin/mkdir could not be executed and failed. -- -- The error number returned while executing this process is 1. Jan 06 15:33:08 jessie systemd[1]: freeswitch.service: control process exited, code=exited status=214 Jan 06 15:33:08 jessie 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. Thanks
Maybe permissions. run journalctl -xe or systemctl status freeswitch.service On 1/6/2018 7:34 AM, Rajil Saraswat wrote:
Hello,
I have the following error in a debian 8 container. Any idea how to fix this?
Jan 06 15:33:08 jessie systemd[2329]: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted -- Subject: Process /bin/mkdir could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 01/06/2018 09:43 AM, Madovsky wrote:
Maybe permissions.
run journalctl -xe or systemctl status freeswitch.service
# systemctl status freeswitch.service ● freeswitch.service - freeswitch Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled) Active: failed (Result: start-limit) since Sat 2018-01-06 15:49:55 UTC; 23s ago Process: 2419 ExecStartPre=/bin/mkdir -p /var/run/freeswitch/ (code=exited, status=214/SETSCHEDULER) Jan 06 15:49:55 jessie systemd[1]: Failed to start freeswitch. Jan 06 15:49:55 jessie systemd[1]: Unit freeswitch.service entered failed state. Jan 06 15:49:55 jessie systemd[1]: freeswitch.service holdoff time over, scheduling restart. Jan 06 15:49:55 jessie systemd[1]: Stopping freeswitch... Jan 06 15:49:55 jessie systemd[1]: Starting freeswitch... Jan 06 15:49:55 jessie systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Jan 06 15:49:55 jessie systemd[1]: Failed to start freeswitch. Jan 06 15:49:55 jessie systemd[1]: Unit freeswitch.service entered failed state. #journalctl -xe Jan 06 15:49:55 jessie 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. Jan 06 15:49:55 jessie systemd[2419]: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted -- Subject: Process /bin/mkdir could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /bin/mkdir could not be executed and failed. -- -- The error number returned while executing this process is 1. Jan 06 15:49:55 jessie systemd[1]: freeswitch.service: control process exited, code=exited status=214 Jan 06 15:49:55 jessie 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.
So, read carefully what is written, "operation not permitted" change your permission on mkdir On 1/6/2018 7:51 AM, Rajil Saraswat wrote:
On 01/06/2018 09:43 AM, Madovsky wrote:
Maybe permissions.
run journalctl -xe or systemctl status freeswitch.service # systemctl status freeswitch.service ● freeswitch.service - freeswitch Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled) Active: failed (Result: start-limit) since Sat 2018-01-06 15:49:55 UTC; 23s ago Process: 2419 ExecStartPre=/bin/mkdir -p /var/run/freeswitch/ (code=exited, status=214/SETSCHEDULER)
Jan 06 15:49:55 jessie systemd[1]: Failed to start freeswitch. Jan 06 15:49:55 jessie systemd[1]: Unit freeswitch.service entered failed state. Jan 06 15:49:55 jessie systemd[1]: freeswitch.service holdoff time over, scheduling restart. Jan 06 15:49:55 jessie systemd[1]: Stopping freeswitch... Jan 06 15:49:55 jessie systemd[1]: Starting freeswitch... Jan 06 15:49:55 jessie systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Jan 06 15:49:55 jessie systemd[1]: Failed to start freeswitch. Jan 06 15:49:55 jessie systemd[1]: Unit freeswitch.service entered failed state.
#journalctl -xe
Jan 06 15:49:55 jessie 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
On 01/06/2018 10:38 AM, Madovsky wrote:
So, read carefully what is written, "operation not permitted"
change your permission on mkdir
The execute permission is correctly, # ls -la /bin/mkdir -rwxr-xr-x 1 root root 80744 Mar 14 2015 /bin/mkdir
You probably don’t have permissions to CREATE the /var/run/freeswitch dir, not that you cannot execute the mkdir binary... On Sat, Jan 6, 2018 at 09:47 Rajil Saraswat <rajil.s@gmail.com> wrote:
On 01/06/2018 10:38 AM, Madovsky wrote:
So, read carefully what is written, "operation not permitted"
change your permission on mkdir
The execute permission is correctly,
# ls -la /bin/mkdir -rwxr-xr-x 1 root root 80744 Mar 14 2015 /bin/mkdir
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On 01/06/2018 04:25 PM, Joel Serrano wrote:
You probably don’t have permissions to CREATE the /var/run/freeswitch dir, not that you cannot execute the mkdir binary...
Commented out the following in /lib/systemd/system/freeswitch.service #IOSchedulingClass=realtime #IOSchedulingPriority=2 #CPUSchedulingPolicy=rr and Freeswitch service is working fine. Solved.
I think just IOSchedulingClass=realtime was gulity On 1/7/2018 9:33 PM, Rajil Saraswat wrote:
On 01/06/2018 04:25 PM, Joel Serrano wrote:
You probably don’t have permissions to CREATE the /var/run/freeswitch dir, not that you cannot execute the mkdir binary...
Commented out the following in /lib/systemd/system/freeswitch.service
#IOSchedulingClass=realtime #IOSchedulingPriority=2 #CPUSchedulingPolicy=rr
and Freeswitch service is working fine.
Solved.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Joel Serrano
-
Madovsky
-
Rajil Saraswat