<html><head><style>body{font-family:Helvetica,Arial;font-size:15px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:15px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">But if it was an issue with the container, it will also appear when i try to launch freeswitch from cli ?</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:15px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:15px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">But <span style="color: rgb(245, 245, 245); font-family: Consolas; background-color: black;">/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp</span> seems to work fine, if i create manually the directory /run/freeswitch (go+w)</div> <div id="bloop_sign_1447849165349169920" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Paul GOERGLER</div></div> <br><p class="airmail_on">On 18 novembre 2015 at 16:18:11, Bote Man (<a href="mailto:bote_radio@botecomm.com">bote_radio@botecomm.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>FreeSWITCH needs to start as root in order to claim execution priority (and maybe other things), then it drops privileges to the user specified by the -u command line switch. That is why the systemd file has that switch on its Execute line.<br><br>I believe that Stanislav discovered the problem as not being able to claim the high-resolution clock inside the container. That would explain the SETSCHEDULER error message.<br><br>Bote<br><br><br>> -----Original Message-----<br>> From: covici@ccs.covici.com<br>> Sent: Wednesday, 18 November, 2015 06:10<br>> Subject: Re: [Freeswitch-users] Installation failed Debian : SETSCHEDULER<br>> <br>> For myself, I put the directory stuff in my /etc/tmpfiles.d I still use<br>> /var/run/freeswitdh so I have<br>> d /var/run/freeswitch 755 freeswitch apache -<br>> <br>> but you could change to suit -- I hope you are not running fs as root.<br>> <br>> Paul GOERGLER <pgoergler@gmail.com> wrote:<br>> <br>> > I add :<br>> > ExecStartPre=-/bin/chmod go+w /run<br>> > ExecStartPre=-/bin/mkdir -o /run/freeswitch<br>> > ExecStartPre=-/bin/chmod go+w /run/freeswitch<br>> ><br>> > But it produce :<br>> > Nov 18 08:21:21 freeswitch systemd[24718]: Failed at step SETSCHEDULER spawning /bin/chmod: Operation not permitted<br>> > Nov 18 08:21:21 freeswitch systemd[24721]: Failed at step SETSCHEDULER spawning /bin/mkdir: Operation not permitted<br>> > Nov 18 08:21:21 freeswitch systemd[24724]: Failed at step SETSCHEDULER spawning /bin/chmod: Operation not permitted<br>> ><br>> > --<br>> > Paul GOERGLER<br>> ><br>> > On 18 novembre 2015 at 10:41:58, covici@ccs.covici.com<br>> (covici@ccs.covici.com) wrote:<br>> ><br>> > put that command in your unit file as an ExecStartPre and see if it<br>> > works.<br>> ><br>> > Paul GOERGLER <pgoergler@gmail.com> wrote:<br>> ><br>> > ><br>> > > Indeed /usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp failed to start.<br>> > > After investigation, the directory /run/freeswitch is missing.<br>> > ><br>> > > For the test i chmod go+w /run and create /run/freeswitch (chmod go+w), and the command work fine.<br>> > ><br>> > > But when i try with systemctl it’s the same issue.<br>> > > Nov 18 06:30:55 freeswitch systemd[31324]: Failed at step SETSCHEDULER spawning /usr/bin/freeswitch: Operation not permitted<br>> > ><br>> > > --<br>> > > Paul GOERGLER<br>> > ><br>> > > On 18 novembre 2015 at 09:10:45, Bote Man<br>> (bote_radio@botecomm.com) wrote:<br>> > ><br>> > > It looks like you installed the package (not that there’s anything wrong<br>> with that) and I always compile the Master source code, so I can offer you<br>> troubleshooting advice since I have also had trouble with systemd.<br>> > ><br>> > ><br>> > ><br>> > > First, try running that exact same command line as systemd uses to start<br>> FS as user ‘root’:<br>> > ><br>> > ><br>> > ><br>> > > /usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp<br>> > ><br>> > ><br>> > > This will show you what systemd is seeing. You might find that<br>> FreeSWITCH can’t run for whatever reason that it reports in its own log. Fix<br>> that and everything might start to work.<br>> > ><br>> > ><br>> > ><br>> > > It’s possible that it can’t write its PID file in /run/freeswitch as that<br>> directory might not exist because it is destroyed on each boot; I’m not sure<br>> about that, though.<br>> > ><br>> > ><br>> > ><br>> > > There might also be permissions problems, although I doubt that as well,<br>> because the package should set up all that stuff for you, but it’s worth<br>> checking permissions and file ownership to be certain.<br>> > ><br>> > ><br>> > ><br>> > > During troubleshooting you might want to comment that Restart= line so<br>> that when FS fails to start, systemd won’t try to restart it needlessly.<br>> > ><br>> > ><br>> > ><br>> > > I know some of the guys have been working on this part of the package<br>> to get it perfect so I don’t know the current state of things there. The<br>> problems that I have seen with systemd and FS involved the PID file directory<br>> and the WorkingDirectory, as well as starting FS with a bare command line so<br>> it never drops privileges to the freeswitch user, resulting in permissions<br>> getting set for root; then when it is run with the –u switch it can’t access its<br>> logs and databases. I know the package uses different directory locations<br>> than the compiled source code installation, which is what gave me problems<br>> early on.<br>> > ><br>> > ><br>> > ><br>> > > I have never seen an error message relating to SETSCHEDULER before.<br>> > ><br>> > ><br>> > ><br>> > > Hope this helps.<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > ---<br>> > ><br>> > > Bote<br>> > ><br>> > ><br>> > ><br>> > > FreeSWITCH Docs Janitor<br>> > ><br>> > > http://freeswitch.org/confluence<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-<br>> users-bounces@lists.freeswitch.org] On Behalf Of pgoergler@gmail.com<br>> > > Sent: Tuesday, 17 November, 2015 13:33<br>> > > To: freeswitch-users@lists.freeswitch.org<br>> > > Subject: [Freeswitch-users] Installation failed Debian : SETSCHEDULER<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Hello,<br>> > ><br>> > ><br>> > ><br>> > > I try to install Freeswitch on a proxmox container with debian 8,<br>> following https://freeswitch.org/confluence/display/FREESWITCH/FreeSWIT<br>> CH+1.6+Video<br>> > ><br>> > > But it does not work<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Here what i did:<br>> > ><br>> > ><br>> > ><br>> > > # cat /etc/debian_version<br>> > > 8.2<br>> > ><br>> > ><br>> > > # cat /etc/apt/sources.list.d/99FreeSWITCH.test.list<br>> > > deb http://files.freeswitch.org/repo/deb/freeswitch-1.6/ jessie main<br>> > > # apt-get update<br>> > > [...]<br>> > > Hit http://files.freeswitch.org jessie InRelease<br>> > > Hit http://files.freeswitch.org jessie/main amd64 Packages<br>> > > Ign http://files.freeswitch.org jessie/main Translation-en<br>> > > Fetched 367 B in 1s (279 B/s)<br>> > > Reading package lists... Done<br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Now i follow the document and install freeswitch-all<br>> > ><br>> > > # apt-get install freeswitch-all<br>> > > [...]<br>> > > Job for freeswitch.service failed. See 'systemctl status freeswitch.service'<br>> and 'journalctl -xn' for details.<br>> > > invoke-rc.d: initscript freeswitch, action "start" failed.<br>> > > dpkg: error processing package freeswitch-all (--configure):<br>> > > subprocess installed post-installation script returned error exit status 1<br>> > > Setting up libmtp-runtime (1.1.8-1+b1) ...<br>> > > Setting up va-driver-all:amd64 (1.4.1-1) ...<br>> > > Processing triggers for libc-bin (2.19-18+deb8u1) ...<br>> > > Processing triggers for systemd (215-17+deb8u2) ...<br>> > > Processing triggers for python-support (1.0.15) ...<br>> > > Errors were encountered while processing:<br>> > > freeswitch-all<br>> > > E: Sub-process /usr/bin/dpkg returned an error code (1)<br>> > ><br>> > ><br>> > > # tail /var/log/syslog<br>> > > Nov 17 16:50:15 freeswitch systemd[20020]: Failed at step SETSCHEDULER<br>> spawning /usr/bin/freeswitch: Operation not permitted<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service: control<br>> process exited, code=exited status=214<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service holdoff time<br>> over, scheduling restart.<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Stopping freeswitch...<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Starting freeswitch...<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service start request<br>> repeated too quickly, refusing to start.<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Ok the document said it could happen, i have to replace<br>> /lib/systemd/system/freeswitch.service<br>> > ><br>> > > I did it<br>> > ><br>> > > # cat /lib/systemd/system/freeswitch.service<br>> > > [Unit]<br>> > > Description=freeswitch<br>> > > After=syslog.target network.target local-fs.target<br>> > ><br>> > > [Service]<br>> > > ; service<br>> > > Type=forking<br>> > > PIDFile=/run/freeswitch/freeswitch.pid<br>> > > PermissionsStartOnly=true<br>> > > ExecStart=/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat<br>> -rp<br>> > > TimeoutSec=45s<br>> > > Restart=on-failure<br>> > > ; exec<br>> > > WorkingDirectory=/usr/bin<br>> > > User=root<br>> > > Group=daemon<br>> > > LimitCORE=infinity<br>> > > LimitNOFILE=100000<br>> > > LimitNPROC=60000<br>> > > ;LimitSTACK=240<br>> > > LimitRTPRIO=infinity<br>> > > LimitRTTIME=7000000<br>> > > IOSchedulingClass=realtime<br>> > > IOSchedulingPriority=2<br>> > > CPUSchedulingPolicy=rr<br>> > > CPUSchedulingPriority=89<br>> > > UMask=0007<br>> > ><br>> > > [Install]<br>> > > WantedBy=multi-user.target<br>> > ><br>> > ><br>> > > # systemctl daemon-reload && systemctl start freeswitch<br>> > > Job for freeswitch.service failed. See 'systemctl status freeswitch.service'<br>> and 'journalctl -xn' for details.<br>> > ><br>> > ><br>> > > Hum still not working<br>> > ><br>> > ><br>> > ><br>> > > # systemctl status freeswitch.service<br>> > > * freeswitch.service - freeswitch<br>> > > Loaded: loaded (/lib/systemd/system/freeswitch.service; disabled)<br>> > > Active: failed (Result: start-limit) since Tue 2015-11-17 16:52:08 CET; 15s<br>> ago<br>> > > Process: 20069 ExecStart=/usr/bin/freeswitch -u freeswitch -g<br>> freeswitch -ncwait -nonat -rp (code=exited, status=214/SETSCHEDULER)<br>> > ><br>> > > Nov 17 16:52:07 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:52:07 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service holdoff time<br>> over, scheduling restart.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Stopping freeswitch...<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Starting freeswitch...<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service start request<br>> repeated too quickly, refusing to start.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > ><br>> > ><br>> > ><br>> > ><br>> > > And with the same error:<br>> > ><br>> > > # tail /var/log/syslog<br>> > > Nov 17 16:52:07 freeswitch systemd[20069]: Failed at step SETSCHEDULER<br>> spawning /usr/bin/freeswitch: Operation not permitted<br>> > > Nov 17 16:52:07 freeswitch systemd[1]: freeswitch.service: control<br>> process exited, code=exited status=214<br>> > > Nov 17 16:52:07 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:52:07 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service holdoff time<br>> over, scheduling restart.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Stopping freeswitch...<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Starting freeswitch...<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service start request<br>> repeated too quickly, refusing to start.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Failed to start freeswitch.<br>> > > Nov 17 16:52:08 freeswitch systemd[1]: Unit freeswitch.service entered<br>> failed state.<br>> > ><br>> > ><br>> > ><br>> > ><br>> > > What can i do to make it start correctly ?<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > Thanks,<br>> > ><br>> > > --<br>> > ><br>> > ><br>> __________________________________________________________<br>> _______________<br>> > > Professional FreeSWITCH Consulting Services:<br>> > > consulting@freeswitch.org<br>> > > http://www.freeswitchsolutions.com<br>> > ><br>> > > Official FreeSWITCH Sites<br>> > > http://www.freeswitch.org<br>> > > http://confluence.freeswitch.org<br>> > > http://www.cluecon.com<br>> > ><br>> > > FreeSWITCH-users mailing list<br>> > > FreeSWITCH-users@lists.freeswitch.org<br>> > > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> > > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-<br>> users<br>> > > http://www.freeswitch.org<br>> > > ----------------------------------------------------<br>> > > Alternatives:<br>> > ><br>> > > ----------------------------------------------------<br>> > ><br>> __________________________________________________________<br>> _______________<br>> > > Professional FreeSWITCH Consulting Services:<br>> > > consulting@freeswitch.org<br>> > > http://www.freeswitchsolutions.com<br>> > ><br>> > > Official FreeSWITCH Sites<br>> > > http://www.freeswitch.org<br>> > > http://confluence.freeswitch.org<br>> > > http://www.cluecon.com<br>> > ><br>> > > FreeSWITCH-users mailing list<br>> > > FreeSWITCH-users@lists.freeswitch.org<br>> > > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> > > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-<br>> users<br>> > > http://www.freeswitch.org<br>> > --<br>> > Your life is like a penny. You're going to lose it. The question is:<br>> > How do<br>> > you spend it?<br>> ><br>> > John Covici<br>> > covici@ccs.covici.com<br>> ><br>> ><br>> __________________________________________________________<br>> _______________<br>> > Professional FreeSWITCH Consulting Services:<br>> > consulting@freeswitch.org<br>> > http://www.freeswitchsolutions.com<br>> ><br>> > Official FreeSWITCH Sites<br>> > http://www.freeswitch.org<br>> > http://confluence.freeswitch.org<br>> > http://www.cluecon.com<br>> ><br>> > FreeSWITCH-users mailing list<br>> > FreeSWITCH-users@lists.freeswitch.org<br>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-<br>> users<br>> > http://www.freeswitch.org<br>> > ----------------------------------------------------<br>> > Alternatives:<br>> ><br>> > ----------------------------------------------------<br>> <br>> --<br>> Your life is like a penny. You're going to lose it. The question is:<br>> How do<br>> you spend it?<br>> <br>> John Covici<br>> covici@ccs.covici.com<br>> <br>> __________________________________________________________<br>> _______________<br>> Professional FreeSWITCH Consulting Services:<br>> consulting@freeswitch.org<br>> http://www.freeswitchsolutions.com<br>> <br>> Official FreeSWITCH Sites<br>> http://www.freeswitch.org<br>> http://confluence.freeswitch.org<br>> http://www.cluecon.com<br>> <br>> FreeSWITCH-users mailing list<br>> FreeSWITCH-users@lists.freeswitch.org<br>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>> http://www.freeswitch.org<br><br><br>_________________________________________________________________________<br>Professional FreeSWITCH Consulting Services: <br>consulting@freeswitch.org<br>http://www.freeswitchsolutions.com<br><br>Official FreeSWITCH Sites<br>http://www.freeswitch.org<br>http://confluence.freeswitch.org<br>http://www.cluecon.com<br><br>FreeSWITCH-users mailing list<br>FreeSWITCH-users@lists.freeswitch.org<br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org</div></div></span></blockquote></body></html>