Drop the dependency and more modules. I don't feel like packaging
Types::Serialiser and then their dependencies and so on. The pure
perl based encoding does work and we don't want to run this code
every milli second.
Depend on two more modules to have the following code
emit something:
#use JSON::XS;
use JSON;
my %rec_hash = ('a' => 1, 'b' => 2, 'c' => 3, 'd' => 4, 'e' => 5);
my $json = encode_json \%rec_hash;
print "$json\n";
Besides DBI we need the JSON module. As far as I can see
JSON can use JSON:XS as a fast encoder/decoder. This is
why both libraries need to be provided.
We need DBI and the sqlite3 backend support for a small
monitoring application. Make it available. The files were
taken from meta-perl as of yesterday.
Add the new task to task-sysmocom-feed so it is being built by
default in our CI infrastructure.
make iputils available as well for people wanting to use a real
ping/traceroute/arping.
Related: SYS#1190
Rather than parsing the existing XML or standard output of the nfacct
utility, and then piping that into a perl/python script for formatting
to JSON, we teach nfacct to generate JSON directly. This seems like
the proper way to do it. The patches will be submitted mainline.
[hfreyther: I asked henning to move forward and not test this. We
do not have dhcp/dynamic config in /etc/network/interfaces and the
link will always be up on the idu due it being connected to a switch.
ifplugd is not doing anything useful in this context]
Fixes: SYS#1535
In SYS#659 we wanted that "file" will always log to a persistent
/var/log. After I changed the /etc/default/volatiles/00_core for
the IDU and made journald persistent we still ended up having the
symlink. It appears to be caused by this script.
* When "buffer" is used we don't need to care about /var/log as
it is not being used at all.
* When "file" is set we make sure that /var/log is not a symlink.
In case of the IDU the journald should now be persistent.
Related: SYS#659
The log is spammed with:
May 03 06:24:58 kernel[221]: Loading kernel module for a netw....
May 03 06:24:59 kernel: Loading kernel module for a network ...d.
this is because of an ioctl for an invalid device which leads
to the kernel trying to load a module. This occurs many times
a minute.
I have cherry-picked 1910454fe00cce8b815b1abc0a18a04d3d387ccf which
merged without conflicts. It has not been compile tested.
Related: SYS#1610
For the IDU we currently want to have persistent log files. We
need to fork the volatiles script (installed as 00_core) and it
is already different between dora and current master of poky.
We are missing an sob-idu-qa check that verifies that /var/log
is not a symlink and that /etc/systemd/system/journald.conf is
set to persistent too.
Related: SYS#659
Similar to the T-ODU we would like to keep a persistent log.
This commit is completely untested, rushed and not the final
one (/etc/default/volatiles/00_core most likely needs patching
and we want to limit the size of the log as well).
Related: SYS#659
* add interface for connection to Inmarsat
* remove 'br0' and work directly with 'eth2' instead, to avoid bridges
in vlans of bridges
* bridge the video LAN also into the backbone (for later break-out)
linux-sysmocom_git.bb is used for the BTS, BSC and IDU. Let's
really use 3.10.76 (from 3.10.50 just rebased and not tested
on the device yet). This should fix the Yocto-Master build
tonight.
* the oe udhcpc calls /usr/share/udhcpc/default.script which
calls run-parts -a "$1" /etc/udhcpc.d, so we can install
our script as 60ntp
* using /etc/default/udhcpc-ntp to have the possibility
to disable it on the target, its enabled per default
Related: SYS#1180
9610e792ffde7fb2599d19ca6d2a03230f2043c6 can not be found
in the linux-3.10.76 branch. Just avoid this branch game.
ERROR: Fetcher failure: Unable to find revision 9610e792ffde7fb2599d19ca6d2a03230f2043c6 in branch linux-3.10.76 even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://git.sysmocom.de/sysmo-bts/linux.git;protocol=git;branch=linux-3.10.76'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/builder/jenkins/workspace/Yocto-Master/label/OE/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/linux-sysmocom/3.10.76+gitAUTOINC+9610e792ff-r43/temp/log.do_fetch.16350
NOTE: recipe linux-sysmocom-3.10.76+gitAUTOINC+9610e792ff-r43: task do_fetch: Failed
ERROR: Task 126 (/home/builder/jenkins/workspace/Yocto-Master/label/OE/meta-sysmocom-bsp/recipes-bsp/linux/linux-sysmocom_git.bb, do_fetch) failed with exit code '1
pkg.m4 has been packaged in the main package for a long
while. We certainly don't need this in master anymore.
ERROR: No recipes available for:
/ws/meta-sysmocom-bsp/yocto-master/pkgconfig_0.28.bbappend
It seems like the kernel/package/upgrade/... proceess doesn't deal well
with the fact that some options used to be modules, which are now
built-in. Let's keep it as modules for the time being.
Harald Welte
Holger Hans Peter Freyther
Henning Heinold
Jan Luebbe
Daniel Willmann