[Spce-user] mediator doesn't start after upgrade to mr3.4.2

[Daniel Grotti]

Hi,
you probably have a cdr with "call_type" empty.
That should cause the mediator error.

You should check you kamailio.acc (or kamailio.acc_backup) entries with


sip_reason: Unknown Faxserver caller

or

sip_reason: Relaying Denied



Anyway, this issue should be solved since mr3.4.2.
We need to check this.

Daniel








On 10/28/2014 02:54 PM, Marc Storck wrote:
> Hello Alexander,
>
> I always forget to mention the obvious, of course I tried to restart, stop;start, etc.
>
> Now I found some output in /var/log/ngcp/cdr.log:
>
> cdr.log:Oct 28 14:47:40 johndoe mediator[14852]: Error inserting cdrs: Data truncated for column 'call_type' at row 4
> cdr.log:Oct 28 14:47:40 johndoe mediator[14852]: Shutting down.
> cdr.log:Oct 28 14:47:40 johndoe mediator[14852]: Successfully shut down.
> cdr.log:Oct 28 14:47:40 johndoe mediator[14852]: Unlocking mediator.
>
> Now, I see that something is wrong with the SQL query during CDR insertion, but I have absolutely no idea how to fix this.
>
> Regards,
>
> Marc
>
> ________________________________________
> From: Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of Alex Lutay [alutay at sipwise.com]
> Sent: Tuesday, October 28, 2014 13:29
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] mediator doesn't start after upgrade to mr3.4.2
>
> Dear Marc,
>
> Try to start it manually:
>> /etc/init.d/mediator start
> Also you can "watch" all the logs to get more debug/details:
>> tail -n0 -f /var/log/ngcp/* -f /var/log/syslog
> and trigger mediator restart while you are watching all logs.
>
> I hope it will help you find the reason of your issue.
>
> On 28/10/14 11:34, Marc Storck wrote:
>> after an upgrade to mr3.4.2 the mediator doesn't keep running.
>>
>> The files /var/run/mediator.pid and /var/lock/mediator.lock are created.
>> The pid files contains a PID but when calling "ps faux|grep $pid"
>> (replace $pid with the pid value found in the .pid file), there is no
>> process with that PID.
>>
>> Furthermore the syslog contains no single line concerning the mediator,
>> so I don't have the slightest clue where to start looking.
>>
>> Could some please provide me some pointers where I could start digging?
>
> --
> Alexander Lutay
> Head of Quality Assurance
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)13012036
> Email: alutay at sipwise.com
> Website: http://www.sipwise.com
>
> Meet us @ AFRICACOM : Booth A17/A18
> 11-13 November 2014 : CTICC Cape Town, South Africa
> _______________________________________________
> 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