hi
i noticed that after the upgrade a container (debian 8) that i had running freeswitch (fusionpbx) on stopped starting services.
i was able to replicate after spinning up latest debian 9 template and installing fusionpbx. rebooting container will not start freeswitch service.
Code:
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 2020-05-17 22:17:54 EDT; 16min ago
Process: 5968 ExecStartPre=/bin/mkdir -p /var/run/freeswitch/ (code=exited, status=214/SETSCHEDULER)
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Control process exited, code=exited status=214
May 17 22:17:54 siplxc systemd[1]: Failed to start freeswitch.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Unit entered failed state.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Failed with result 'exit-code'.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Service hold-off time over, scheduling restart.
May 17 22:17:54 siplxc systemd[1]: Stopped freeswitch.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Start request repeated too quickly.
May 17 22:17:54 siplxc systemd[1]: Failed to start freeswitch.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Unit entered failed state.
May 17 22:17:54 siplxc systemd[1]: freeswitch.service: Failed with result 'exit-code'.
i did the same exact install inside kvm and everything works and starts as expected. i started thread on
fusionpbx forum with not much feedback. any help is appreciated.