[Spce-user] Mediator not starting after upgrade

[Alex Lutay]

One more point here...

Just in case, since the topic was about mediator init script initially.

mr6.3 is sysmted based, you should remove SysV init file
/etc/init.d/mediator completely, otherwise systemd might use it
(should not, but your system is kind of special due to the age).

It is expected dpkg removes old init file during upgrade on mr6.2+

On 08/23/2018 02:27 PM, Alex Lutay wrote:
> Hi,
> 
> also... due to:
> 
>> failed (Result: core-dump)
> 
> You can check /var/log/syslog there can be useful information about
> crash. And you should have core file in /var/lib/systemd/coredump/
> 
> We need a backtrace for the crash here. Do you know how to share it?
> 
> On 08/23/2018 01:48 PM, Marcos Pytel wrote:
>> Hi!
>>
>> I updated to 6.3.1 and also mediator is not working, the Service does not start.
>> Wich file log have the mediator log?
>>
>> root at sipwise:~# ngcp-service mediator status
>> ● ngcp-mediator.service - NGCP Mediator
>>    Loaded: loaded (/lib/systemd/system/ngcp-mediator.service; enabled; vendor preset: enabled)
>>    Active: failed (Result: core-dump) since Wed 2018-08-22 13:14:13 -03; 19h ago
>>   Process: 11108 ExecStart=/usr/bin/mediator (code=dumped, signal=SEGV)
>>  Main PID: 11108 (code=dumped, signal=SEGV)
>>
>> Thanks in advance!
>>
>> Marcos.
>>
>> -----Mensaje original-----
>> De: Spce-user <spce-user-bounces at lists.sipwise.com> En nombre de Alex Lutay
>> Enviado el: jueves 23 de agosto del 2018 08:24
>> Para: spce-user at lists.sipwise.com
>> Asunto: Re: [Spce-user] Mediator not starting after upgrade
>>
>> Hi,
>>
>> From what I see, you have really antique system :-D I suspect for some reason locally modified init file was not replaced on upgrade. Probably some garbage in dpkg local database from the Middle Ages on your system (there were fixes in ~2012 for mediator package).
>>
>> As a fix, yes, please use the init file from the package.
>> Just copy new one over the old one.
>>
>> I have tested the issue locally using 2.8->mr3.8 upgrade, so far is it not reproducible here.
>>
>> Unfortunately Sipwise has no 2.6 vagrant systems to recreate your situation.
>>
>> As a summary, consider to upgrade mr4.5/mr5.5 and enjoy NGCP!
>>
>> On 08/22/2018 12:20 PM, qabane me wrote:
>>> dpkg-query -W -f='${Conffiles}' ngcp-mediator
>>>  /etc/init.d/mediator 883f464f9af862c171dd09e58ae39360
>>>  /etc/default/mediator
>>> 65ebeb2266ba26f6672f759f50d6a6c4root at sipwise:/var/backup/ngcp-mr3.8.13
>>> /ngcp-config/templates/etc#
>>>
>>>  cat /etc/ngcp_version
>>> mr3.8.13
>>>  
>>>
>>> System installed. NGCP version 2.6 on 2013-02-11 System installed. 
>>> NGCP version 2.8 - upgraded on 2013-04-13 System installed. NGCP 
>>> version mr3.8.13 - upgraded on 2018-08-08 01:48:43
>>>
>>> I suppose a simple replacement of the /etc/init.d/mediator will do? If 
>>> I am wrong assuming that, please let me know :-)
>>
>> --
>> Alex Lutay
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
> 

-- 
Alex 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: https://www.sipwise.com