[OpenSIPS-Users] How to start OpenSIPS 3.0 server

[Tekin, Arda]

It prints too many logs when I run below command manually
opensips –DD –E

I tried to share the output of command but mail server is blocking my mail. That’s my 3rd try

Let me share these notes,

Opensips binary is under standard prefix
[root at a3783871a39f ~]# which opensips
/usr/local/sbin/opensips


When I run opensips manually it works
[root at a3783871a39f init.d]# opensips
Listening on
             udp: 172.16.30.241 [172.16.30.241]:5060
Aliases:

Verified that it listens udp:5060
[root at a3783871a39f run]# netstat -anp | grep opensips
udp        0      0 172.16.30.241:5060      0.0.0.0:*                           31542/opensips
unix  2      [ ]         DGRAM                    21043523 31542/opensips
unix  2      [ ]         DGRAM                    21043526 31542/opensips

Opensips service start script  looks like this,
[root at a3783871a39f ~]# cat /etc/rc.d/init.d/opensips
…
…

# Source function library.
. /etc/rc.d/init.d/functions
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
…
…
-----------

systemctl start opensips
service opensips start
commands gives the same result.
Starting opensips (via systemctl):  Job for opensips.service failed because a configured resource limit was exceeded. See "systemctl status opensips.service" and "journalctl -xe" for details.
                                                           [FAILED]

Any idea?
Do you see any help document that explains how Opensips 3.0 should be started by a command/service script?

Regards,
Arda


From: Users <users-bounces at lists.opensips.org> On Behalf Of David Villasmil
Sent: Wednesday, February 12, 2020 4:55 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>
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.


That’s your problem. Make sure the path exists and opensips can create the pid file there.

Other test you can do is start manually, I.e: opensips -DD -E
Providing the proper config file; etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200213/21151c8e/attachment-0001.html>