[Spce-user] ngcp-mediator.service failing on reboot

[Andy Clark]

[Unit]
Description=NGCP Mediator
After=mariadb.service
After=redis-server.service
After=remote-fs.target
Wants=mariadb.service
Wants=redis-server.service

[Service]
Type=notify
ExecStart=/usr/bin/mediator

[Install]
WantedBy=multi-user.target
Alias=mediator.service


● ngcp-mediator.service - NGCP Mediator
   Loaded: loaded (/lib/systemd/system/ngcp-mediator.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-03-25 09:59:38 PDT;
2min 6s ago
  Process: 1356 ExecStart=/usr/bin/mediator (code=exited, status=255)


Mar 25 09:53:17 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:53:17 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:54:57 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:54:57 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:56:37 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:56:37 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:58:17 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:58:17 spce (warning) mediator[1806]: medmysql.c:1043 [<unknown>]:
Skipping duplicate IP '72.15.250.77'
Mar 25 09:58:17 spce (crit) mediator[1806]: medmysql.c:579 [<unknown>]: No
records found for callid '275265300_129868401 at 55.193.4.151'!
Mar 25 09:58:17 spce (info) mediator[1806]: mediator.c:424 [main]: Runtime
for loop processing 1 callids and generating 0 CDRs was 3852 us.
Mar 25 09:58:17 spce (info) mediator[1806]: mediator.c:425 [main]: Total
CDR creation rate 0.000000 CDR/sec
Mar 25 09:58:27 spce (crit) mediator[1806]: medmysql.c:579 [<unknown>]: No
records found for callid '275265300_129868401 at 55.193.4.151'!
Mar 25 09:58:27 spce (info) mediator[1806]: mediator.c:424 [main]: Runtime
for loop processing 1 callids and generating 0 CDRs was 1247 us.
Mar 25 09:58:27 spce (info) mediator[1806]: mediator.c:425 [main]: Total
CDR creation rate 0.000000 CDR/sec
Mar 25 09:58:37 spce (crit) mediator[1806]: medmysql.c:579 [<unknown>]: No
records found for callid '275265300_129868401 at 55.193.4.151'!
Mar 25 09:58:37 spce (info) mediator[1806]: mediator.c:424 [main]: Runtime
for loop processing 1 callids and generating 1 CDRs was 11627 us.
Mar 25 09:58:37 spce (info) mediator[1806]: mediator.c:425 [main]: Total
CDR creation rate 86.006709 CDR/sec
Mar 25 09:59:38 spce (notice) mediator[1356]: mediator.c:190 [main]:
Starting mediator
Mar 25 09:59:38 spce (info) mediator[1356]: mediator.c:221 [main]: ACC acc
database host='localhost', port='3306', user='kamailio', name='kamailio'
Mar 25 09:59:38 spce (info) mediator[1356]: mediator.c:223 [main]: CDR acc
database host='localhost', port='3306', user='mediator', name='accounting'
Mar 25 09:59:38 spce (info) mediator[1356]: mediator.c:225 [main]: PROV
database host='localhost', port='3306', user='mediator', name='provisioning'
Mar 25 09:59:38 spce (info) mediator[1356]: mediator.c:227 [main]: STATS
database host='localhost', port='3306', user='mediator', name='stats'
Mar 25 09:59:38 spce (info) mediator[1356]: mediator.c:231 [main]: REDIS
database host='localhost', port='6379', pass='<none>', id='21'
Mar 25 09:59:38 spce (err) mediator[1356]: medredis.c:420 [medredis_init]:
Failed to perform redis query 'PING': LOADING Redis is loading the dataset
in memory


what do you think the issue is?

On Mon, Mar 25, 2019 at 3:28 AM Alex Lutay <alutay at sipwise.com> wrote:

> Hi,
>
> AFAIK mediator has dependency on redis-server.service since
> the very beginning (mr6.2+):
>
> >> ~/git/mediator$ grep redis debian/ngcp-mediator.service
> > After=redis-server.service
> > Wants=redis-server.service
>
> I am afraid it is something else. Check /var/log/ngcp/cdr.log on errors.
> Also check systemd service status after boot:
>
> >> systemctl  | grep mediator
> > ngcp-mediator.service                                             loaded
> active running   NGCP Mediator
> >> systemctl status ngcp-mediator
>
> You can find some hints there about the real origin of your issue.
>
> Have fun!
>
> On 3/23/19 9:47 AM, Jon Bonilla (Manwe) wrote:
> > El Fri, 22 Mar 2019 18:05:05 -0700
> > Andy Clark <andyclark05251978 at gmail.com> escribió:
> >
> >> ngcp-mediator.service failing on reboot
> >> SPCE 6.5.3.1+0~mr6.5.3.1
> >> will startup manually without issues
> >
> > probably it needs redis to start first if you're using acc2redis.
> >
> > I think it will be solved in 6.5.4
> >
> >>
> >> what do  you need from me to help solve this?
> >
> > you can edit systemd startup and add redis dependency
>
> --
> Alex Lutay
> _______________________________________________
> 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/20190325/a772819d/attachment-0001.html>