[OpenSIPS-Users] How to start OpenSIPS 3.0 server
Tekin, Arda
arda.tekin at afiniti.com
Wed Feb 19 09:58:53 EST 2020
Hi Liviu,
Thank you very much for all your answers.
I had built and installed opensips from the source code on CentOS 7
It seems that service startup scripts and permissions need to be handled for CentOS. I have applied following commands (as root) and now the service works successfully.
Copy init script:
cp /root/src/opensips-3.0/packaging/redhat_fedora/opensips.init /etc/init.d/opensips
chmod 755 /etc/init.d/opensips
Edit the first section of script according to build prefix path. Mine looks like this
---
prog=opensips
opensips=/usr/local/sbin/$prog
cfgdir="/usr/local/etc/$prog"
pidfile="/var/run/$prog.pid"
lockfile="/var/lock/subsys/$prog"
configfile="$cfgdir/$prog.cfg"
m4configfile="$cfgdir/$prog.m4"
m4archivedir="$cfgdir/archive"
OPTIONS=""
S_MEMORY=32
P_MEMORY=32
RETVAL=0
...
---
Install service:
chkconfig --add opensips
chkconfig opensips on
Copy configuration file:
cp /root/src/opensips-3.0/packaging/redhat_fedora/opensips.sysconfig /etc/sysconfig/opensips
Add user for OpenSIPS:
adduser --system --user-group --shell /sbin/nologin --comment "OpenSIPS" --home-dir /var/run/opensips opensips
mkdir /var/run/opensips
chmod 755 /var/run/opensips
chown opensips:opensips /var/run/opensips
Start OpenSIPS 3.0
service opensips start
Regards,
Arda
-----Original Message-----
From: Users <users-bounces at lists.opensips.org> On Behalf Of Liviu Chircu
Sent: Thursday, February 13, 2020 7:51 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>; Callum Guy <callum.guy at x-on.co.uk>
Subject: Re: [OpenSIPS-Users] How to start OpenSIPS 3.0 server
Attention: This email was sent from someone outside of Afiniti. Always use caution when opening attachments, clicking links from unknown senders or when receiving unexpected emails.
On 13.02.2020 18:41, Callum Guy wrote:
> shows a resource limit error "Starting opensips (via systemctl): Job
> for opensips.service failed because a configured resource limit was
> exceeded."
>
IMO, that is a typical systemd error, since it attempts to start your service in some insane "while (!started) { start_service() }" type of loop until it realizes that it did so many quick attempts that it ran out of resource X (cycles, memory, disk, etc.) and needs to throttle things down...
--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
www.opensips.org/events
OpenSIPS Bootcamp, Miami, March 2020
www.opensips.org/training
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
More information about the Users
mailing list