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.

On Wed, 12 Feb 2020 at 05:23, Tekin, Arda <arda.te...@afiniti.com> wrote:

> Hi David
>
>
>
> I just see this log entry when I call “journalctl -xe”
>
>
>
> -- Unit opensips.service has begun starting up.
>
> Feb 12 10:04:24 a3783871a39f opensips[15922]: Starting opensips: [FAILED]
>
> Feb 12 10:04:24 a3783871a39f systemd[1]: Can't open PID file
> /var/run/opensips.pid (yet?) after start: No such file or directory
>
> Feb 12 10:04:24 a3783871a39f systemd[1]: Failed to start LSB: start, stop
> OpenSIPS.
>
> -- Subject: Unit opensips.service has failed
>
> -- Defined-By: systemd
>
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
> --
>
> -- Unit opensips.service has failed.
>
> --
>
> -- The result is failed.
>
> Feb 12 10:04:24 a3783871a39f systemd[1]: Unit opensips.service entered
> failed state.
>
> Feb 12 10:04:24 a3783871a39f systemd[1]: opensips.service failed.
>
>
>
>
>
> *From:* Users <users-boun...@lists.opensips.org> *On Behalf Of *David
> Villasmil
> *Sent:* Wednesday, February 12, 2020 2:22 AM
> *To:* OpenSIPS users mailling list <users@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.*
>
>
>
> And the output of
>
>
>
> journalctl -xe
>
>
>
> ?
>
>
>
> On Tue, 11 Feb 2020 at 17:20, Tekin, Arda <arda.te...@afiniti.com> wrote:
>
> How can I run OpenSIPS 3.0?
>
>
>
> Previously we are running `opensipsctl start` command.
>
>
>
> How to set and use db connection configuration before starting OpenSIPS?
>
>
>
> I have compiled latest source code on CentOS 7 successfully. Copied init
> script
>
> cp /root/src/opensips-3.0/packaging/redhat_fedora/opensips.init
> /etc/rc.d/init.d/.
>
>
>
> Edited the init file
>
> 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
>
>
>
>
>
> When I run init script I get this error.
>
> 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]
>
>
>
> Where is doc page explaining how OpenSIPS 3 starts?
>
>
>
> Kind Regards,
>
> Arda
>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> --
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.w...@gmail.com
>
> phone: +34669448337
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to