Freeswitch fails on new fusionpbx install on to ct lxc debian11 on proxmox 7.2.3

[lawson]

Installation appears to complete successfully after using a valid token from signalwire and correct repos. Correct locale is set.

The environment is using a clean install of proxmox 7.2.3 and CT template debian-11-standard_11.3-1_amd64.tar.zst onto a dell intel x64 server. The lxc ct container is an unprivileged container with 4cores, 8gb ram, 80gb disk, and has keyctl and nesting options enabled in proxmox.

Inside the lxc debian container I successfully follow the Installing Freeswitch From Debian Packages instructions here https://freeswitch.org/confluence/display/FREESWITCH/Debian

And next I successfully follow the Debian Install instruction found here
https://www.fusionpbx.com/download


However after installation freeswitch.service fails to start and after hours of troubleshooting I cannot find what to do or try next to resolve this issue.

Anyone have suggestions? Thanks

Log info pasted below:




# journalctl -u freeswitch.service
-- Journal begins at Sat 2022-05-21 22:32:58 UTC, ends at Sun 2022-05-22 08:15:01 UTC. --
May 22 03:14:35 deb11ffreeswitch systemd[1]: Starting freeswitch...
May 22 03:14:35 deb11ffreeswitch systemd[122776]: freeswitch.service: Failed to set up CPU scheduling: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[122776]: freeswitch.service: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Control process exited, code=exited, status=214/SETSCHEDULER
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Failed with result 'exit-code'.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Failed to start freeswitch.
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Scheduled restart job, restart counter is at 1.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Stopped freeswitch.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Starting freeswitch...
May 22 03:14:35 deb11ffreeswitch systemd[122787]: freeswitch.service: Failed to set up CPU scheduling: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[122787]: freeswitch.service: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Control process exited, code=exited, status=214/SETSCHEDULER
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Failed with result 'exit-code'.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Failed to start freeswitch.
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Scheduled restart job, restart counter is at 2.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Stopped freeswitch.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Starting freeswitch...
May 22 03:14:35 deb11ffreeswitch systemd[122794]: freeswitch.service: Failed to set up CPU scheduling: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[122794]: freeswitch.service: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Control process exited, code=exited, status=214/SETSCHEDULER
May 22 03:14:35 deb11ffreeswitch systemd[1]: freeswitch.service: Failed with result 'exit-code'.
May 22 03:14:35 deb11ffreeswitch systemd[1]: Failed to start freeswitch.
May 22 03:14:36 deb11ffreeswitch systemd[1]: freeswitch.service: Scheduled restart job, restart counter is at 3.

----------


# systemctl list-units
* sys-kernel-config.mount loaded failed failed Kernel Configuration File System
* fail2ban.service loaded failed failed Fail2Ban Service
* freeswitch.service loaded failed failed freeswitch
* networking.service loaded failed failed Raise network interfaces
* systemd-journald-audit.socket loaded failed failed Journal Audit Socket

--------

#systemctl status freeswitch.service
* freeswitch.service - freeswitch
Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-05-22 07:56:54 UTC; 15min ago
Process: 130162 ExecStartPre=/bin/mkdir -p /var/run/freeswitch (code=exited, status=214/SETSCHEDULER)
CPU: 799us

May 22 07:56:54 deb11ffreeswitch systemd[1]: freeswitch.service: Scheduled restart job, restart counter is at 5.
May 22 07:56:54 deb11ffreeswitch systemd[1]: Stopped freeswitch.
May 22 07:56:54 deb11ffreeswitch systemd[1]: freeswitch.service: Start request repeated too quickly.
May 22 07:56:54 deb11ffreeswitch systemd[1]: freeswitch.service: Failed with result 'exit-code'.
May 22 07:56:54 deb11ffreeswitch systemd[1]: Failed to start freeswitch.


-------------

#journalctl -xe
--
-- The job identifier is 3697 and the job result is done.
May 22 07:56:54 deb11ffreeswitch systemd[1]: freeswitch.service: Start request repeated too quickly.
May 22 07:56:54 deb11ffreeswitch systemd[1]: freeswitch.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit freeswitch.service has entered the 'failed' state with result 'exit-code'.
May 22 07:56:54 deb11ffreeswitch systemd[1]: Failed to start freeswitch.
-- Subject: A start job for unit freeswitch.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit freeswitch.service has finished with a failure.
--
-- The job identifier is 3697 and the job result is failed.
May 22 08:05:01 deb11ffreeswitch CRON[130192]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 22 08:05:01 deb11ffreeswitch CRON[130193]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 22 08:05:01 deb11ffreeswitch CRON[130192]: pam_unix(cron:session): session closed for user root
May 22 08:09:01 deb11ffreeswitch CRON[130207]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 22 08:09:01 deb11ffreeswitch CRON[130208]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
May 22 08:09:01 deb11ffreeswitch CRON[130207]: pam_unix(cron:session): session closed for user root
May 22 08:09:01 deb11ffreeswitch systemd[1]: Starting Clean php session files...
-- Subject: A start job for unit phpsessionclean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has begun execution.
--
-- The job identifier is 3756.
May 22 08:09:01 deb11ffreeswitch systemd[1]: phpsessionclean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit phpsessionclean.service has successfully entered the 'dead' state.
May 22 08:09:01 deb11ffreeswitch systemd[1]: Finished Clean php session files.
-- Subject: A start job for unit phpsessionclean.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has finished successfully.
--
-- The job identifier is 3756.

 

[lawson]

The problem appears to be caused by the unprivileged lxc container.

Does anyone know any method of configuring the container to remain unprivileged but also to have access to cpu scheduling?

I found a workaround to start unprivileged freeswitch and not get these errors is by changing IOSchedulingClass=realtime


What problems could be caused by commenting out these lines from /lib/systemd/system/freeswitch.service which will then allow freeswitch to start unprivileged? How severe of a performance penalty does this cost in order for freeswitch to run in an unprivileged container?
#IOSchedulingClass=realtime
#IOSchedulingPriority=2
#CPUSchedulingPolicy=rr

Otherwise, is there any performance penalty or only security concerns with running the container as privileged and keeping the above lines intact?


Has anyone been able to successfully run freeswitch in an lxc ct unprivileged container without disabling IOSchedulingClass=realtime?