[Spce-user] mediator fails

[qabane me]

Hi

The problem of connecting to redis was resolved by a restart of redis so
that part is working again.

Now back to mediator and redis.

root at spce:~# redis-cli -n 21 hgetall
acc:cid::011cd8e3-220b-1237-d9a8-a6958035e26f
(error) WRONGTYPE Operation against a key holding the wrong kind of value

is the result.

All that I did was apply hotfixes to deal with the known issue of mediator
crashing. As soon as that was done this error appeared but it is possible
of course that it was there but because mediator never got to that part
before the hotfix it did not appear yet. To be clear, the manual restart I
did of redis was only just now to get kamailio to connect again, the error
appeared after that.

Hope that helps?

On Thu, Aug 30, 2018 at 10:30 AM Andreas Granig <agranig at sipwise.com> wrote:

> Hi,
>
> What’s the actual content of the redis key
> “acc:cid::011cd8e3-220b-1237-d9a8-a6958035e26f”? Fetch it via
>
> redis-cli -n 21 hgetall acc:cid::011cd8e3-220b-1237-d9a8-a6958035e26f
>
> According to the code, your sip_code column value in redis is NULL, which
> should actually never happen, unless you have some corrupted data, and
> according to your kamailio logs, you had some redis issues during this
> time. Can you please elaborate what you believe happend with the server
> during this time? Kamailio complained about not being able to connect to
> redis. Anything special you did on the server or that happened on the
> server at that point, like a manual restart of redis or some applying of
> configs or reboot or crash?
>
> Andreas
>
> > On 30.08.2018, at 08:53, qabane me <qabaneitsolutions at gmail.com> wrote:
> >
> > Hi
> >
> > It didn't work for me. The error we had went away indeed but now I get:
> > Aug 30 08:52:28 spce (err) mediator[2271]: medredis.c:60
> [medredis_reply_to_entry]: Received Redis reply type 4 instead of 1
> (string) for element 0
> > Aug 30 08:52:28 spce (err) mediator[2271]: medredis.c:641
> [medredis_fetch_records]: Failed to convert redis reply to entry (cid
> '011cd8e3-220b-1237-d9a8-a6958035e26f')
> > Aug 30 08:52:28 spce (info) mediator[2271]: mediator.c:391 [main]:
> Shutting down.
> > Aug 30 08:52:28 spce (info) mediator[2271]: mediator.c:397 [main]:
> Successfully shut down.
> >
> > So it looks like that's something else?
> >
> > On Wed, Aug 29, 2018 at 1:45 PM Marcos Pytel <
> marcos.pytel at cotesma.com.ar> wrote:
> > Hi,
> >
> > Work for me!
> >
> > Thanks.
> >
> > Marcos.
> >
> > -----Mensaje original-----
> > De: Spce-user <spce-user-bounces at lists.sipwise.com> En nombre de Alex
> Lutay
> > Enviado el: miércoles 29 de agosto del 2018 06:17
> > Para: spce-user at lists.sipwise.com
> > Asunto: Re: [Spce-user] Fwd: mediator fails
> >
> > Hi,
> >
> > I see the problem, please upgrade to the latest hotfixes for mr6.4.1,
> the new ngcp-mediator (6.4.1.2+0~mr6.4.1.2) has just been released.
> >
> > Please share the results with new fixes.
> > P.S. Tnx for reporting it here!
> >
> > On 08/28/2018 10:31 PM, qabane me wrote:
> > > A backtrace of this gives me the below. I have already applied
> > > hotfixes
> > >
> > > #0  __GI_____strtod_l_internal (nptr=0x0, endptr=endptr at entry=0x0,
> > > group=group at entry=0, loc=0x7f90685ab400 <_nl_global_locale>) at
> > > strtod_l.c:583
> > ...
> >
> > --
> > Alex Lutay
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > https://lists.sipwise.com/listinfo/spce-user
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > https://lists.sipwise.com/listinfo/spce-user
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180830/d84da3b8/attachment-0001.html>