The --parallel option is already the default with debhelper >= 10, but
that does not apply to any overrides we use, which means we were not
honoring parallel builds there.
Change-Id: I3b50098aaf1461d3591989b2779b157562a23c97
It is unnecessary as '--parallel' should be the default with debhelper compat 10+
Thank you, Michael Prokop and Guillem Jover for noticing and pointing!
This reverts commit 937e2379ff.
Change-Id: I0aea58004e7b87966b642ccc993106b3c9594cc0
'*' - matches 0 or more characters
'?' - matches any one character
for more info, refer to <fnmatch.h>
Change-Id: Icbe450b7921d541fed089a1bb00c180e416c34ae
- "-E" which is enables debug mode, removed from unit files.
- not daemonize will be reached by changing sems config file options
Change-Id: I0778aa2b15c08cd9a85739283fb2355046f64d78
If an SDP UPDATE is received after the 183, but before the 200,
SEMS fails when it receive the final ACK. In fact SEMS tries to
find the SDP content inside the ACK message itself.
The solution is copied from sems-pbx module where the issue
doesn't happen.
Change-Id: Ib9402071c44afa032a45f97e2acd30629e7bc89b
The current problem is massive services restart on: systemctl restart glusterd.service
which is not really necessary on NGCP.
Use 'Wants' instead of 'Requires' so dependent services aren't
restarted on restart of remote-fs.target.
Change-Id: I512fdc7ae83efb10cc442da12e72d4b902dba96c
Is service B "Requires" service A to be started before B
and B does NOT require B restart on A restart, B should use "Wants=A".
Convert Wants=network-online.target to After=network-online.target
to be identical for all other NGCP services. IMHO sems should be
restarted if networking got restarted (listen new IP's, etc).
Also sort them alphabetically.
Change-Id: I2e239eec2c33a90f150fe2773566f671cbd2483a
Otherwise it refuses to stop, until it reaches the timeout.
Confirmed that it's OK to kill in this way, and waiting for implementation
changes so this is not necessary.
Change-Id: I34fc0b017b17779e8a15e031bf78960bbca2ada7
This service requires write access to redis, and relies on redis-master
to setup Redis in that mode. If we switch the redis master/slave roles
while SEMS is still running, or while we are trying to shut it down,
it gets very confused and takes very long to realize and shutdown.
So we should always make sure that redis-master is running before we
start sems, and stop sems before we stop redis-master.
Change-Id: Iaa43186230df6ab8365c94585192fbb6db2652cc
The default is 90s, so when it fails for some reason, it takes (unnecessarily)
too long to recover.
This happens when calling twice "ngcp-service ngcp-sems restart", or "systemctl
restart ngcp-sems", while having debugging enabled. The processes apparently
get blocked, until they get killed after 90s of default timeout.
Perhaps it is still necessary (and better) to fix it in other ways, like finding
the root cause of the blockage (racing conditions during initialisation?).
Waiting for ~1s between restarts almost completely solves the problem, which
points to some problem of that sort.
However, given the current problem and the fact that 10s should be enough to for
this service to stop, it's probably a good idea to change from the default to
10s, so if finding similar problems for other reasons, they have less impact and
the timeouts are more acceptable.
Change-Id: I5487493bee5c9147972d9fa6e063176a8d9ca4fd
With the previous change (b106d5bb0e), the file
was not processed correctly by dh_installinit because of an extra -s in the
filename.
Change-Id: Ie78bcfbb9565e520c395fc26e1551ecfe961dd46
According to Guillem (thanks to him) in a comment to another package:
"Actually dh_installinit already handles these files in stretch you just need
to name it debian/pkgname.tmpfile."
Change-Id: I43f23be57fb4c19adaeebb9f4e522d24816ca018
It breaks some tests, that could be changed, but maybe there are some other
unintended consequences, and it's not important to change to /run right now (in
fact, it might be undesired for consistency reasons with respect to the other
sems-service variant, etc.)
User: sems: home: doesn't match, expect: [{"or":["/var/run/ngcp-sems","/var/run/sems"]}] found: ["/run/ngcp-sems"]
Change-Id: I2038e0d90b46dc12eeecf4bcc7ad4e249688ad20
One reason to have full systemd support is to increase consistency when bringing
up and shutting down the system, or when restarting services, to have more
integration with the init system as a whole.
But apart from that reason, the original reason is that it has been noticed as
part of TT#31163 (service action tests) that the autogenerated unit file in
/run/systemd/generator.late/ngcp-sems.service does not properly depend on
MariaDB/MySQL (it had "After=mysql.service", but not Wants or Requires).
Unlike with sysvinit, with systemd the services are started in parallel, so
starting "after" another doesn't mean that the former is finished and fully
working by the time that the latter is ready.
Under these tests, this service sometimes fails to start, so it might be because
the DB is not ready (or at least it can be one of the reasons contributing to
the failure). In any case, if it should start after "mysql" in sysvinit (or
"mariadb.service", as we're renaming it under systemd), SEMS probably assumes
that "mariadb.service" would be fully working, so the additional annotation
"Requires" is more correct than having only "After=mariadb.service".
As part of this change and since we are revamping the init support, we also
remove sysvinit support (including /etc/default/ngcp-sems) and delete or modify
some maintainer scripts referencing old sysvinit support.
Change-Id: I46b0b7b92fc6b13b467aafbb38e9383e88d0ad65
Unset Sems internal Session Timers in case B leg doesn't support it
(no Timer in Supported header of 200OK message).
Change-Id: I21fd1de2a088ab71042cbee54bd00cd1ea9f5a0b
These override any of our global settings set in sysctl.d for example.
Which can be very confusing. Only set process specific settings to not
disturb the whole system.
Change-Id: I131d273804b530b1a5326fec82f44517676d4b40
This helper does not work properly when we specify a private directory
on the command-line, so we need to run it twice.
Change-Id: I67498cbd6d1db20c95ce7c1dbba989eea2d2c9c2
This has become an opaque struct in latest versions, use instead the
accessor that is available already in Debian jessie.
Change-Id: I2a5e17f91707871343b0b358fd195db507d7e43b
Sipwise Jenkins Builder
Guillem Jover
Alexander Lutay
Kirill Solomko
Roman Romanchenko
Andrew Pogrebennyk
Marco Capetta
Mykola Malkov
Manuel Montecelo
Richard Fuchs
Jozef Kenyeres