[OpenSIPS-Users] OpenSIPs crashed
Răzvan Crainea
razvan at opensips.org
Mon Jan 16 03:49:37 EST 2017
Hi, Ahmed!
Can you tell us exactly what revision of OpenSIPS you are using? Please
provide the output of the following commands:
opensips -V
opensipsctl ps
Also, during startup, is there a process who's "eating" a lot of CPU? If
so, can you pinpoint the PID to see what type of process is that?
Regarding the avp_db_query() issue, did you define a db_url parameter
for it? Also I am not sure you can do something like $var(res) =
avp_db_query(...). But anyways, this is something completely different,
so please open a different topic for it.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 01/14/2017 12:24 AM, Ahmed Munir wrote:
> Hi,
>
> I've just installed new version of opensips 2.2.2 on the test box and
> updated by routing script, the issue currently I'm seeing alot warning
> messages while starting opensips service below;
>
> /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job
> <tm-utimer> has a 2830000 us delay in execution
>
> Number of children running on that server is 8 as it is 8 core processor.
>
> I would like to know what steps do I need to take to fix this issue.
> Btw, warnings only occurred during the time of starting opensips
> service but not during calls.
>
>
> Further added, a issue I face using avp_db_query () function i.e. when
> using it as
>
> $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM
> Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse),
> $avp(trunkid)");
>
> failed to start opensips service due to errors below;
>
> ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by
> this function
> ERROR:core:fix_actions: fixing failed (code=-6) at
> //etc/opensips/opensips.cfg:207
> CRITICAL:core:fix_expr: fix_actions error
> ERROR:core:main: failed to fix configuration with err code -6
>
>
> If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db
> query, opensips service starts successfully.
>
> Please advise the steps do I need to take to fix above issues.
>
>
>
> From: Răzvan Crainea <razvan at opensips.org
> <mailto:razvan at opensips.org>>
> To: users at lists.opensips.org <mailto:users at lists.opensips.org>
> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed
> Message-ID: <40f6dada-e121-a2da-b283-69dff891cd11 at opensips.org
> <mailto:40f6dada-e121-a2da-b283-69dff891cd11 at opensips.org>>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi, Ahmed!
>
> OpenSIPS 1.6.3 is no longer supported (since 2013), so there's not
> much
> we can do right now. Try upgrading your install to the latest 1.6.4
> version and see if your problem is solved. Otherwise, upgrade to a
> newer, supported version, preferably the latest stable release, 2.2.2.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutions
> www.opensips-solutions.com <http://www.opensips-solutions.com>
>
> On 01/12/2017 11:55 PM, Ahmed Munir wrote:
> > Found coredump on one of the server, see some partial message below
> > while taking the back trace;
> >
> >
> >
> > Core was generated by `/usr/sbin/opensips -P
> /var/run/opensips.pid -m
> > 64 -u opensips -g opensips'.
> >
> > Program terminated with signal 11, Segmentation fault.
> >
> > #0 0x00007f650687a069 in sip_msg_cloner () from
> > /usr/lib64/opensips/modules/tm.so
> >
> > Missing separate debuginfos, use: debuginfo-install
> > opensips-1.6.3-notls.x86_64
> >
> >
> >
> > Please advise what might be the reason causing opensips to crash.
> >
> > --
> > Regards,
> >
> > Ahmed Munir Chohan
> >
> >
> >
> >
> > --
> > Regards,
> >
> > Ahmed Munir Chohan
> >
>
>
>
>
> --
> Regards,
>
> Ahmed Munir Chohan
>
>
>
> _______________________________________________
> 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/20170116/0e8cacc9/attachment.html>
More information about the Users
mailing list