Hi all,

just because this issue hit my just in a new container:
the container running freeswitch has to be privileged. Running an unprivileged container (in my case, it's with proxmox) won't have the necessary permissions to set the required CPU scheduler.
Making the container privileged solved the problem and freeswitch starts as expected.

Starting freeswitch manually worked before, because the scheduler is set by systemd (defined in the unit file).
Hope that helps if anyone else finds that message via your favorite search engine ;)

Regards
Nico


On 11/17/15 19:32, pgoergler@gmail.com wrote:

# tail /var/log/syslog

Nov 17 16:50:15 freeswitch systemd[20020]: Failed at step SETSCHEDULER spawning /usr/bin/freeswitch: Operation not permitted

Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service: control process exited, code=exited status=214

Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch.

Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered failed state.

Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service holdoff time over, scheduling restart.

Nov 17 16:50:15 freeswitch systemd[1]: Stopping freeswitch...

Nov 17 16:50:15 freeswitch systemd[1]: Starting freeswitch...

Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service start request repeated too quickly, refusing to start.

Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch.

Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered failed state.