[OpenSIPS-Users] Restart=always and After=mysql.service

Sun Sep 20 21:19:07 CEST 2015

Does it start in the usual way with “opensipsctl start”? If not, try to fix that method of starting, check /etc/opensips/opensipsctrl. 

Some things you might want to check.
With systemd , opensips cannot normally create files in /tmp or /var/run. for your pid file directory, create /var/run/opensips from /etc/rc.d/rc.local on each boot as /var/run is cleaned on shutdown.

From: Nabeel 
Sent: Sunday, September 20, 2015 1:11 AM
To: Podrigal, Aron ; OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Restart=always and After=mysql.service

No, I just compiled and installed OpenSIPS in the normal manner while logged in as root.

On 20 September 2015 at 06:00, Podrigal, Aron <aronp at guaranteedplus.com> wrote:

  Are you running this on a container / chrooted env?

  On Sun, Sep 20, 2015 at 12:39 AM, Nabeel <nabeelshikder at gmail.com> wrote:

    This is what it says:

      Sep 20 05:21:45 server1.sipdomain.com systemd[1]: Starting OpenSIPS is a very fast and flexible SIP (RFC3261) server...
      -- Subject: Unit opensips.service has begun with start-up
      -- Defined-By: systemd
      -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- Unit opensips.service has begun starting up.
      Sep 20 05:21:45 server1.sipdomain.com systemd[4022]: Failed at step EXEC spawning /usr/sbin/opensips: Permission denied
      -- Subject: Process /usr/sbin/opensips could not be executed
      -- Defined-By: systemd
      -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- The process /usr/sbin/opensips could not be executed and failed.
      --
      -- The error number returned while executing this process is 13.
      Sep 20 05:21:45 server1.sipdomain.com systemd[1]: opensips.service: control process exited, code=exited status=203
      Sep 20 05:21:45 server1.sipdomain.com systemd[1]: Failed to start OpenSIPS is a very fast and flexible SIP (RFC3261) server.
      -- 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.
      Sep 20 05:21:45 server1.sipdomain.com systemd[1]: Unit opensips.service entered failed state.

    On 20 September 2015 at 05:12, Podrigal, Aron <aronp at guaranteedplus.com> wrote:

      Do you see anything informative in your journal after trying to start opensips? 

      sudo journalctl -xn 350

      On Sat, Sep 19, 2015 at 11:46 PM, Nabeel <nabeelshikder at gmail.com> wrote:

        Please see the strace output at these links: 

        http://pastebin.com/G1Uv5s1E

        http://pastebin.com/gnesw4tW

        On 20 September 2015 at 04:30, Podrigal, Aron <aronp at guaranteedplus.com> wrote:

          Can you post the strace output by running 

          sudo strace -ff -o /tmp/opensips_strace_output systemctl start opensips.service

          cat /tmp/opensips_strace_output*

          That will help see where the error occurs.

          On Sat, Sep 19, 2015 at 11:21 PM, Nabeel <nabeelshikder at gmail.com> wrote:

            Why can't the service file be automatically generated at the time of installation/compilation on the relevant OS?  
            It seems to be quite a basic feature missing.

            On 20 September 2015 at 04:16, Nabeel <nabeelshikder at gmail.com> wrote:

              Unfortunately, changing the user/group to 'root' did not work either. 

              The same error occurs and OpenSIPS fails to start:

                Failed at step EXEC spawning /usr/sbin/opensips: Permission denied

              Hasn't anyone else seen this on CentOS?

              On 18 September 2015 at 22:21, sevpal <sevpal at aol.com> wrote:

                If you change User= and Group= in the service file to root, you might not see such a message. To run as user opensips, then user opensips must exist on the system; in addition, ownership on files/folders that will be accessed by Opensips needs to be changed.
                From: Nabeel 
                Sent: Tuesday, September 15, 2015 9:47 PM
                To: OpenSIPS users mailling list 
                Subject: Re: [OpenSIPS-Users] Restart=always and After=mysql.service

                I tried that service file on CentOS 7 but got the following error when trying to start the service: 

                  Failed at step EXEC spawning /usr/sbin/opensips: Permission denied

                Changing permissions of that directory did not solve the problem:

                chmod +x /usr/sbin/opensips

                chmod -R 777 /usr/sbin/opensips 

                Does the service file need modification for CentOS?

                On 7 September 2015 at 19:14, Nabeel <nabeelshikder at gmail.com> wrote:

                  Hi, 

                  Most of my services have a .service file located at /usr/lib/systemd/system where I can set 'Restart=always' or 'After=mysql.service' / 'After=mariadb.service' to make sure the server starts at the appropriate times.

                  However, there is no such .service file for OpenSIPS.  Please advise how to create this .service file for OpenSIPS.  I heard about 'respawn' but don't know how exactly to use this and would prefer to use a .service file like other services.

----------------------------------------------------------------
                _______________________________________________
                Users mailing list
                Users at lists.opensips.org
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users

                _______________________________________________
                Users mailing list
                Users at lists.opensips.org
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users

            _______________________________________________
            Users mailing list
            Users at lists.opensips.org
            http://lists.opensips.org/cgi-bin/mailman/listinfo/users

          -- 

          Aron Podrigal 
          -
          '1000001', '1110010', '1101111', '1101110'   '1010000', '1101111', '1100100', '1110010', '1101001', '1100111', '1100001', '1101100'

          P: '2b', '31', '33', '34', '37', '34', '35', '38', '36', '30', '39', '39'

          _______________________________________________
          Users mailing list
          Users at lists.opensips.org
          http://lists.opensips.org/cgi-bin/mailman/listinfo/users

      -- 

      Aron Podrigal 
      -
      '1000001', '1110010', '1101111', '1101110'   '1010000', '1101111', '1100100', '1110010', '1101001', '1100111', '1100001', '1101100'

      P: '2b', '31', '33', '34', '37', '34', '35', '38', '36', '30', '39', '39'

  -- 

  Aron Podrigal 
  -
  '1000001', '1110010', '1101111', '1101110'   '1010000', '1101111', '1100100', '1110010', '1101001', '1100111', '1100001', '1101100'

  P: '2b', '31', '33', '34', '37', '34', '35', '38', '36', '30', '39', '39'

--------------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150920/ca1660fe/attachment-0001.htm>