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
wrote:
> Are you running this on a container / chrooted env?
>
> On Sun, Sep 20, 2015 at 12:39 AM, Nabeel wrote:
>
>> This is what it says:
>>
>>
>>> Sep 20 05:
Are you running this on a container / chrooted env?
On Sun, Sep 20, 2015 at 12:39 AM, Nabeel 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 b
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/system
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 wrote:
> Please see the strace output at these links:
>
> http://pastebin.com/G1Uv5s1E
>
> http://pastebin.com/gnesw4tW
>
> On 20 September 2015 at 04
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
wrote:
> Can you post the strace output by running
>
> sudo strace -ff -o /tmp/opensips_strace_output systemctl start
> opensips.service
> cat /t
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 wrote:
> Why can't the service file be automatically ge
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 wrote:
> Unfortunately, changing the user/group to 'root' did not work either.
>
> The same error
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 wrote:
> If you change U
I checked the logs and they have the following information
[Sat Sep 19 14:53:13.915427 2015] [:error] [pid 1928] [client
127.0.0.1:47528] PHP Warning: Creating default object from empty value in
/var/www/opensips-cp/config/db.inc.php on line 25, referer:
http://127.0.0.1/opensips-cp/web/
[Sat Se
Hello,
See the instructions at
http://www.opensips.org/html/docs/modules/1.11.x/db_cachedb#id249688
Basically, in your script you have to set
db_version_table="my_version_table"
and then in your MongoDB database go ahead and manually insert the
record for the ACC table version , like :
10 matches
Mail list logo