chirpstack / chirpstack-gateway-os Goto Github PK

OpenWrt based gateway images including ChirpStack components.

Makefile 42.72% Shell 57.28%

lorawan lora iot gateway openwrt chirpstack

chirpstack-gateway-os's Introduction

ChirpStack Gateway OS

ChirpStack Gateway OS is an open-source OpenWrt based embedded OS for LoRa^® gateways. It provides a web-interface for configuration and contains pre-defined configuration options for common LoRa hardware to make it easy to setup a LoRa gateway and optionally a ChirpStack-based LoRaWAN^® Network Server.

Note: If you are looking for the Yocto recipes of the previously Yocto based ChirpStack Gateway OS, please switch to the v4_yocto branch.

Documentation and binaries

Please refer to the ChirpStack Gateway OS documentation for documentation and pre-compiled images.

Building from source

Requirements

Building ChirpStack Gateway OS requires:

Docker

Initialize

To initialize the OpenWrt build environment, run the following command:

make init

This will:

Clone the OpenWrt code
Fetch all the OpenWrt feeds, including the ChirpStack OpenWrt Feed
Symlink configuration and files

Update

This step is not required after running make init, but allows you to update the OpenWrt source and feeds at a later point:

make update

Build

For building the ChirpStack Gateway OS, you must enter the Docker-based development environment first:

make devshell

Switch configuration

Each target and image has its own OpenWrt configuration file, files and patches. These can be found under the conf directory of this repository.

To switch to one of these configuration environments, you must execute:

make switch-env ENV=name-of-env

Fo example if you would like to switch to base_raspberrypi_bcm27xx_bcm2709, you execute:

make switch-env ENV=base_raspberrypi_bcm27xx_bcm2709

This will:

Undo all previously applied patches.
Update the symlinks for OpenWrt configuration and files.
Apply all patches.

Building image

Once the configuration has been set, run the following command to build the ChirpStack Gateway OS image:

make

Note that this can take a couple of hours depending on the selected configuration and will require a significant amount of disk-space.

Making configuration changes

Note: The commands listed below must be executed within the openwrt directory.

To make configuration changes (e.g. add additional packages), you can execute:

make menuconfig

As updates to OpenWrt packages can introduce new configuration options over time, you can run the following command to update the configuration:

make defconfig

Please refer also to the OpenWrt build system usage documentation.

chirpstack-gateway-os's People

Contributors

Stargazers

Watchers

chirpstack-gateway-os's Issues

Add chirpstack-udp-bridge support

Hi!!
Suggestion: the next Chirpstack-gateway-os release should support the chirpstack-udp-bridge feature (https://github.com/brocaar/chirpstack-udp-bridge) in order to have a gateway with multiple simultaneous packet-forwarder instances for different network servers (example: Chirpstack server and TTN server).

Build does not work on Ubuntu Desktop small version, use Full version

Probably not an issue with lora-gateway-os, but I'm unused to these things and wish to log it somewhere as it might help someone else. (Please close issue and I think it will still be searchable )

Installing a fresh Ubuntu 18.04 LTS or 19.04 Desktop version you are asked for a Full ( with office packages and everything ) or a Small ( with only webbrowser ) installation of Ubuntu. The Small version that ought to be enough fails the build in some openembedded nss-xxx.bb lib-files, that passes fine if built on the Full version (after adding git, docker and docker-composer to both). Very strange as the build system is running inside containers that should contain everything by themselves?!? but this is far beyond my understanding.

Conclusion - Build on Full Desktop version of Ubuntu and the instructions here really works - https://github.com/brocaar/lora-gateway-os/blob/master/README.md ( after applying the fix in #20 if having the WiringPi Error )

iC980a (915 MHz Version of iC880a) no 915 MHz Config available

Hi,
excellent work by the way, at this point I've tested the most simple things of the raspberry pi image, but with some problems at this point.
In the latest version of the code I recently checked there's no longer support for the 915 MHz of the packet forwarder. When I try to setup the gateway in the raspberry pi with the iC980a (the 915MHz version of the iC880a) it doesn't start the packet-forwarder, I checked the reset pin AND the global_config.json checking that there's everything fine in the config file. Nothing good after all because the monit status always response with a failure.
I downloaded and flashed the older version, the December 2018 version, and it has the 915 MHz profile and it worked perfectly.
Maybe I'm wrong and wasting your time or maybe it's something to improve, I appreciate your time and hope you can answer if there's any kind of new way to config the iC980a in the newest OS version or it's not supported at all and have to find another solution.
Thanks in advance.

UPDATE:
I make it work with the recent version, but keep looking for the configuration in the Concentrator Setup to have a US915 profile. Thanks.

UPDATE 2:
When you try to configurate a 915MHz iC980a with the LoRa Server OS image for raspberry, works fine BUT you must modify by your self the "loraserver.toml" file to configure the 915 Channels available in the concentrator. I think this step it's an important one because in other way the downlink doesn't work (I mean, I can't have downlink without this with the right setup).

Network Server Creation

context deadline exceeded (code: 2)

AS923 missing for RAK831

I have a RAK831 and I have used it on TTN with AS923. However, when I run gateway-config AS923 is not one of the options available.

Image version is lora-gateway-os-full-raspberrypi3--20190810092349.sdimg

Getting gateway added to vendor list?

Hi there,

What's the process to get our gateway added here - https://www.loraserver.io/lora-gateway-os/overview/

Thanks,
Aaron

Chirpstack OS building error

I already installed docker compose to ubuntu 18.04, however I follow the step of setting up I got the below error:

george@george-ThinkPad-X200:~$ make submodules

Command 'make' not found, but can be installed with:

sudo apt install make
sudo apt install make-guile

george@george-ThinkPad-X200:~$ make submodules

Command 'make' not found, but can be installed with:

sudo apt install make
sudo apt install make-guile

george@george-ThinkPad-X200:~$ docker-compose run --rm busybox
ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?

    Supported filenames: docker-compose.yml, docker-compose.yaml

george@george-ThinkPad-X200:~$

What other steps I need to do before I can run docker-compose run --rm busybox?

Mosquitto doesn't load the configuration file at startup

Hello!

I encountered the following problem (with Chirpstack Gateway OS full 3.1.0test1).

I prepared my own customized configuration file for the Mosquitto bridge that allows me to connect with my cloud service.
I placed this bridge.conf file in /etc/mosquitto/conf.d directory which I included to the main configuration file as include_dir /etc/mosquitto/conf.d.

When I reloaded the configuration for Mosquitto by command:

sudo /etc/init.d/mosquitto reload

and I restarted the Mosquitto daemon:

sudo /etc/init.d/mosquitto restart

the connection to the cloud service was established correctly (I was able to read the messages on selected topics on both sites - cloud and gateway).

But when I rebooted the system, the connection wasn't re-established (automatically) even though the configuration file wasn't changed.

I short investigated this problem and noticed that in /etc/init.d/mosquitto script, in case when it is called with start parameter, the configuration file isn't loaded as in the case of a call with the restart parameter:

if start-stop-daemon --start --quiet --oknodo --background --make-pidfile --pidfile ${PIDFILE} --exec ${DAEMON} -- -c /etc/mosquitto/mosquitto.conf ; then

So if I add -- -c /etc/mosquitto/mosquitto.conf flag also to the case of a call with the start parameter, connection with the cloud service is establishing correctly - even if I reboot the system.

So - is this a bug? Or did I do something incorrectly?

Pi4 LoraWan Question

Have You pi4 image?

Using systemd

Hi,
How can I use systemd?
I added the following to local.conf but get a yocto circular dependecy when building (due the the rootfs overlay)

# Enable systemd
DISTRO_FEATURES_append = " systemd "
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""

wifi won't connect if ethernet connection is present

tested version: Self compiled with sources from 04.04.2020

problem: If wifi is configured and the system boots while an ethernet connection is present, the ChirpstackOS won't connect to wifi.
The system booted without ethernet is going to connect to wifi and can be connected to ethernet after boot up. In this case booth connections are operational.

expected behaviour: Starting the system with connected ethernet and configured wifi should lead to two working network connections after boot.

Additionally: Using sudo gateway-config for wifi configuration always reboots the system. That should not be necessary.

drogon.net wiringpi repo is down

wiringpi_git.bb submodule should be updated

Redis database does not start on boot after power failure that corrupts append only file

I escalate this to a bug here at the github repo since I have now found two other people experience this on the user forums, and it is a real deal-breaker for the gateway-os. I.e gateway can not be used as it dies in the field..

https://forum.chirpstack.io/t/redis-error-after-gatewayos-reboot/5568 ( other peoples report on LorixOne and RAK2245 )

https://forum.chirpstack.io/t/redis-database-stopped-running-anyone-else-that-has-seen-this/7095 ( my report on Raspberry pi + RisingHF )

As seen in my bootlog, redis does start, but it is dead later on. My linuxskills is not that good so this is as far as I have come with the logs... an error in an append only file?

raspberrypi3:~$ sudo more /var/log/boot
Wed Jan  8 13:20:39 2020: Wed Jan  8 13:20:39 UTC 2020
Wed Jan  8 13:20:39 2020: INIT: Entering runlevel: 5
Wed Jan  8 13:20:39 2020: Configuring network interfaces... done.
Wed Jan  8 13:20:39 2020: Starting system message bus: dbus.
Wed Jan  8 13:20:39 2020: Starting Connection Manager
Wed Jan  8 13:20:39 2020: Starting Dropbear SSH server: dropbear.
Wed Jan  8 13:20:40 2020: Starting rpcbind daemon...done.
Wed Jan  8 13:20:40 2020: Starting advanced power management daemon: No APM support in kernel
Wed Jan  8 13:20:40 2020: (failed.)
Wed Jan  8 13:20:40 2020: Starting bluetooth: bluetoothd.
Wed Jan  8 13:20:40 2020: Starting lora-app-server
Wed Jan  8 13:20:40 2020: Starting lora-gateway-bridge
Wed Jan  8 13:20:40 2020: Resetting concentrator board using pin 7
Wed Jan  8 13:20:41 2020: Starting lora-packet-forwarder
Wed Jan  8 13:20:41 2020: Starting loraserver
Wed Jan  8 13:20:41 2020: mender is disabled, update /etc/default/mender
Wed Jan  8 13:20:41 2020: Starting ntpd: done
Wed Jan  8 13:20:42 2020: Starting postgresql-server service:  [ OK ]
Thu Jan  9 22:53:07 2020: Starting syslogd/klogd: done
Thu Jan  9 22:53:07 2020: wireguard is disabled, update /etc/default/wireguard
Thu Jan  9 22:53:07 2020:  * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
Thu Jan  9 22:53:07 2020:    ...done.
Thu Jan  9 22:53:07 2020: Starting Telephony daemon
Thu Jan  9 22:53:07 2020: Starting Mosquitto message broker mosquitto
Thu Jan  9 22:53:07 2020: Starting redis-server...
Thu Jan  9 22:53:07 2020: 414:C 09 Jan 22:53:07.709 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Thu Jan  9 22:53:07 2020: 414:C 09 Jan 22:53:07.709 # Redis version=4.0.8, bits=32, commit=00000000, modified=0, pid=414, just started
Thu Jan  9 22:53:07 2020: 414:C 09 Jan 22:53:07.709 # Configuration loaded
Thu Jan  9 22:53:07 2020: Starting MonitStarting Monit 5.26.0 daemon with http interface at [localhost]:2812
Thu Jan  9 22:53:07 2020: .
raspberrypi3:~$ sudo ps -aux | grep redis
admin     1465  0.0  0.0   2384   476 pts/0    S+   23:06   0:00 grep redis
raspberrypi3:~$

raspberrypi3:~$ sudo cat /var/log/messages | grep redis | more
Jan  9 22:53:07 raspberrypi3 user.warn redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Jan  9 22:53:07 raspberrypi3 user.warn redis-server: Redis version=4.0.8, bits=32, commit=00000000, modified=0, pid=414, just started
Jan  9 22:53:07 raspberrypi3 user.warn redis-server: Configuration loaded
Jan  9 22:53:07 raspberrypi3 local0.notice redis[415]: Increased maximum number of open files to 10032 (it was originally set to 1024).
Jan  9 22:53:07 raspberrypi3 local0.warn redis[415]: Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Jan  9 22:53:07 raspberrypi3 local0.notice redis[415]:                 _._                                                              _.-``__ ''-._                                                    _.-``    `.  `_.  ''-._           Redis 4.0.8 (00000000/0) 32 bit   .-`` .-`
Jan  9 22:53:07 raspberrypi3 local0.warn redis[415]: WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
Jan  9 22:53:07 raspberrypi3 local0.warn redis[415]: Server initialized
Jan  9 22:53:07 raspberrypi3 local0.warn redis[415]: WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memo
Jan  9 22:53:17 raspberrypi3 local0.warn redis[415]: Bad file format reading the append only file: make a backup of your AOF file, then use ./redis-check-aof --fix <filename>

Can not add network server with 'localhost:8000' but works with 127.0.0.1:8000

Edit note: initial Bugreport mixed up ports. I initally wrote port 8080 but it was port 8000 all along.

What happened:
On the Web-UI I wanted to add a NetworkServer. names "testns" and Network-server server "localhost:8080" without any TLS cert and no gateway discovery.
After quite some delay the WebUI itself shows a "context deadline exceeded (code: 2)" within a little overlay. But no Network-server was created
On the other hand, using Network-server server: "127.0.0.1:8080" works fine

What I expected:
that the 'localhost:8080' server works ;)

Additional:
[::1]:8080 also doesn't work

system:
Freshly installed gatewayOS full ( image: raspi3-20200127144146 )

Image will not build via Yocto because git.drogon.com is no longer available

When building a new image from Yocto for deployment via Mender, it currently fails with the following error:


ERROR: wiringpi-git-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export PATH="/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/lora-gateway-os/layers/openembedded/openembedded-core/scripts:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot/usr/bin/crossscripts:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot-native/usr/sbin:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot-native/usr/bin:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot-native/sbin:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/recipe-sysroot-native/bin:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/lora-gateway-os/bitbake/bin:/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/hosttools"; export HOME="/media/yocto/jenkins"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://git.drogon.net/wiringPi /media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/downloads/git2/git.drogon.net.wiringPi --progress failed with exit code 128, output:

Cloning into bare repository '/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/downloads/git2/git.drogon.net.wiringPi'...



fatal: unable to connect to git.drogon.net:

git.drogon.net[0: 188.246.205.22]: errno=Connection refused

git.drogon.net[1: 2a03:9800:10:7b::2]: errno=Network is unreachable





ERROR: wiringpi-git-r0 do_fetch: Fetcher failure for URL: 'git://git.drogon.net/wiringPi'. Unable to fetch URL from any source.

ERROR: wiringpi-git-r0 do_fetch: Function failed: base_do_fetch

ERROR: Logfile of failure stored in: /media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/wiringpi/git-r0/temp/log.do_fetch.22117

NOTE: recipe wiringpi-git-r0: task do_fetch: Failed

ERROR: Task (/media/yocto/jenkins/jenkins-meta/jenkins-meta/workspace/a-gateway-os_feature_auto_deploy/lora-gateway-os/layers/bsp/meta-raspberrypi/recipes-devtools/wiringpi/wiringpi_git.bb:do_fetch) failed with exit code '1'

Is there a reason this is being installed from Git rather than from the packages as recommended on the installation page at http://wiringpi.com/download-and-install/ ?

Currently, if you try and access git.drogon.com you get the following message:

git.drogon.net is temporarily unavailable. Please look for alternatives for wiringPi, etc. -Gordon

App server listens by default on IPv6 only

Running netstat -vatn on a brand new flashed device gives me the following:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:2812          0.0.0.0:*               LISTEN
tcp        0      0 :::111                  :::*                    LISTEN
tcp        0      0 :::8080                 :::*                    LISTEN
tcp        0      0 ::1:53                  :::*                    LISTEN
tcp        0      0 :::22                   :::*                    LISTEN
tcp        0      0 ::1:5432                :::*                    LISTEN
tcp        0      0 :::1883                 :::*                    LISTEN
tcp        0      0 :::8000                 :::*                    LISTEN
tcp        0      0 :::8001                 :::*                    LISTEN
tcp        0      0 :::8003                 :::*                    LISTEN

Based on this, it is clear that the app server is only running on IPv6.

It doesn't seem possible to disable IPv6 using sysctl (it just doesn't work) like this:

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

and if I disable ipv6 using the kernel command line argument ipv6.disable=1 then SSH doesn't listen properly anymore (actually, nothing does; I can ping the device but it otherwise shows up as having zero open ports using nmap).

Disabling IPv6 kills the HDMI output as well for some reason.

The image I am using is lora-gateway-os-full-raspberrypi3--20190810092349.sdimg

Implement regional configuration for AS923 MHz ISM Band.

Is this a bug or a feature request?

Neither of both. Contribution.

What did you expect?

Make chirpstack-gateway-os to have predefined AS923 MHz configuration files, so that can gateways using concentrador component can be able to work at aformentioned ISM band region.

What happened?

Currently chirpstack-gateway-os supports EU868, AU915, US915.

What version are your using?

v3.3.0-test.3

Being said that, my initial plan is to bring support to this region at concentrador component level and afterwards generate the corresponding configuration files on network-server and adding the how-to documentation on the oficial site.

This is something that I would be more than excited to contribute to. What are your thoughts?

GPIO 7 reset pin busy

Hi,
The chirpstack-gateway-os 3.3.3 has the chirpstack-concentratord v3.0.3 version, which implements the overwriting reset-pin for RPi shields.

However, some gateway boards have the reset pin allocated at GPIO 7 pin, which is also allocated to SPI0 CS1 on RPi versions (https://www.raspberrypi.org/documentation/hardware/raspberrypi/spi/README.md). When the chirpstack-concentradord tries to start it crashes with EBUSY error on this GPIO 7 pin.

In order to fix it, the chirpstack-gateway-os image should include the /boot/overlays/spi0-2cs.dtbo file in Yocto structure in order to enable the config parameter "dtoverlay=spi0-2cs,cs1_pin=<another free pin different from 7>" in /boot/config.txt. This will reallocate the SPI0 CS1 GPIO 7 pin to a different GPIO pin, and the concentratord will start correctly with GPIO 7 reset pin.

I hope this can help to improve Gateway OS.

gateway-os-base image missing /opt directory

It looks like there should be gateway-utils installed to /opt/libloragw-sx1301/gateway-utils/
However /opt directory is not in the gateway-os-base image

High wifi latency and very high jitter

ChirpstackOS-full is used, update 27.03.2020 was installed

Wifi latency and jitter is too high, sometimes exceeding 1000ms, which could be problematic if one needs to hit timed receiving windows of Class A/B devices.

screenshot:
on the left is the ChipstackOS and on the right side raspbian. Both devices are Model 3 Raspberries and are using the same wifi, placed within 30cm of the wifi access point.

--- 192.168.128.71 ping statistics ---
1325 packets transmitted, 1119 received, +139 errors, 15,5472% packet loss, time 1329944ms  
rtt min/avg/max/mdev = 1.473/317.005/1236.734/300.494 ms

-- 192.168.128.72 ping statistics ---
4945 packets transmitted, 4944 received, 0,0202224% packet loss, time 4949597ms
rtt min/avg/max/mdev = 0.804/4.940/166.763/6.950 ms

You can ignore the package losses, that was my doing (reboot of ChirpOS).

Concentratord Problem with Risinghf hat on Raspberry Pi 3

I’m using the full OS installation to try to get this system running.
I have a RPI 3 with a RHF0M301 hat.

When I go through the setup for the concentrator shield and select option 9 Risinghf RHF0M301 and select US915 and the first channel option and then yes to all the file write options, I am returned to the main menu.

At the top it says
Version 3.3.3
Gateway ID: not configured

When I look at the general configuration for Concentratord it shows
model=“generic_us915”

and at the end of the file it shows
reset_pin=0

When I exit to the command line and enter sudo monit summary it tells me everything is OK except the chirpstack-concentratord which has the status of “does not exist”.

About lora-gtaeway-os running hardware

How to run on other hardware except Raspberry Pi 3 and LORIX One?What do I need to do? What are requirements about the hardware?
thanks
sandy

Choosing a gateway leeds to empty page

Version: 13.02.2020
chirpstack-gateway-os-full-raspberrypi3-20200213123140.rootfs.wic.gz

Problem:
After rebooting choosing an existing gateway results in empty page and error message:
"context deadline exceeded (code: 2)"

click on "testgw" and I got:

It takes a while for the error message to pop up.

Edit:
Gateways -> Maps
The Gateway is still present on the map, status is "a few seconds ago"

Edit2
Problem disappears after a long time or after madly clicking arround.

/var/log/messages

Feb 24 13:17:04 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:04Z" level=info msg="finished unary call with code OK" ctx_id=5a15d627-51f5-4683-940f-1a9196d92a97 grpc.code=OK grpc.method=List grpc.service=api.GatewayService grpc.start_time
Feb 24 13:17:04 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:04Z" level=info msg="finished unary call with code OK" ctx_id=6c37d010-a691-47e0-b278-94168564da80 grpc.code=OK grpc.method=List grpc.service=api.GatewayService grpc.start_time
Feb 24 13:17:04 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:04Z" level=info msg="finished unary call with code OK" ctx_id=3860b6a3-a4ae-4ba0-93e6-99a19e09c33e grpc.code=OK grpc.method=GetStats grpc.service=api.GatewayService grpc.start_
Feb 24 13:17:06 raspberrypi3 user.warn chirpstack-application-server[338]: time="2020-02-24T13:17:06Z" level=warning msg="creating insecure network-server client" server="localhost:8000"
Feb 24 13:17:10 raspberrypi3 auth.err getty[1499]: tcgetattr: Input/output error^M
Feb 24 13:17:11 raspberrypi3 user.err chirpstack-application-server[338]: time="2020-02-24T13:17:11Z" level=error msg="finished unary call with code Unknown" ctx_id=1e039f37-d8f1-4716-93cc-8cb1cf22fa99 error="rpc error: code = Unknown desc = context deadline exceeded" grpc
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-concentratord-sx1301[517]: Publishing stats event, stats_id: a2ae067a-0a52-427a-a6a5-d34f5fef838d, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-gateway-bridge[473]: time="2020-02-24T13:17:16Z" level=info msg="backend/concentratord: stats event received" stats_id=a2ae067a-0a52-427a-a6a5-d34f5fef838d
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-gateway-bridge[473]: time="2020-02-24T13:17:16Z" level=info msg="integration/mqtt: publishing event" event=stats qos=0 stats_id=a2ae067a-0a52-427a-a6a5-d34f5fef838d topic=gateway/4223422342234223/event/stats
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-network-server[362]: time="2020-02-24T13:17:16Z" level=info msg="gateway/mqtt: gateway stats packet received" gateway_id=4223422342234223 stats_id=a2ae067a-0a52-427a-a6a5-d34f5fef838d
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-network-server[362]: time="2020-02-24T13:17:16Z" level=info msg="gateway updated" ctx_id=a2ae067a-0a52-427a-a6a5-d34f5fef838d gateway_id=4223422342234223
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:16Z" level=info msg="gateway updated" ctx_id=dd12a7e8-866d-4bdb-a39c-1ed5a865d016 id=4223422342234223 name=testgw
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:16Z" level=info msg="metrics saved" aggregation="[MINUTE HOUR DAY MONTH]" ctx_id=dd12a7e8-866d-4bdb-a39c-1ed5a865d016 name="gw:4223422342234223"
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-application-server[338]: time="2020-02-24T13:17:16Z" level=info msg="finished unary call with code OK" ctx_id=dd12a7e8-866d-4bdb-a39c-1ed5a865d016 grpc.code=OK grpc.method=HandleGatewayStats grpc.service=as.ApplicationServer
Feb 24 13:17:16 raspberrypi3 user.info chirpstack-network-server[362]: time="2020-02-24T13:17:16Z" level=info msg="finished client unary call" ctx_id=a2ae067a-0a52-427a-a6a5-d34f5fef838d grpc.code=OK grpc.ctx_id=dd12a7e8-866d-4bdb-a39c-1ed5a865d016 grpc.duration=16.41915ms```

How can I generate a image file ?

Hi brocaar,

This is my first time to build lora-gateway-os.
I could finish to compile all modules but can not create a image file.
Error messages are follows:

yocto@f9b041c46386:/build$ /lora-gateway-os/scripts/loraserver-prepare-deploy 
mkdir: cannot create directory ‘/lora-gateway-os/deploy’: Permission denied
find: ‘/build/tmp/raspberrypi/raspberrypi3-glibc/deploy/2.0.0test2/images’: No such file or directory
find: ‘/build/tmp/raspberrypi/raspberrypi3-glibc/deploy/2.0.0test2/images’: No such file or directory
cp: cannot stat '/build/tmp/raspberrypi/raspberrypi3-glibc/deploy/2.0.0test2/licenses': No such file or directory
mkdir: cannot create directory ‘/lora-gateway-os/deploy’: Permission denied
find: ‘/build/tmp/wifx/lorix-one-sd-glibc/deploy/2.0.0test2/images’: No such file or directory
find: ‘/build/tmp/wifx/lorix-one-sd-glibc/deploy/2.0.0test2/images’: No such file or directory
cp: cannot stat '/build/tmp/wifx/lorix-one-sd-glibc/deploy/2.0.0test2/licenses': No such file or directory
mkdir: cannot create directory ‘/lora-gateway-os/deploy’: Permission denied
find: ‘/build/tmp/wifx/lorix-one-512-sd-glibc/deploy/2.0.0test2/images’: No such file or directory
find: ‘/build/tmp/wifx/lorix-one-512-sd-glibc/deploy/2.0.0test2/images’: No such file or directory
cp: cannot stat '/build/tmp/wifx/lorix-one-512-sd-glibc/deploy/2.0.0test2/licenses': No such file or directory

Permission denied error : Owner of the /lora-gateway-os is 1000 but yocto is 999.
drwxrwxr-x 8 1000 1000 4096 Apr 16 01:54 lora-gateway-os
find error : 2.0.0test2 should be 2.0.0test3

So, I tried to change the script but yoct can not change it because permission is denied.
Are there any suggestion.

Sandbox Lorago Port doesn't work with latest release of chirpstack

The issue is present in the latest release.
I have searched the issues of this repository and believe that this is not a duplicate.

What happened?

The lorago shield doesn't work with latest version. No leds are blinking

What did you expect?

Steps to reproduce this issue

Steps:

Install and plug the sandbox lorago port shielf

Could you share your log output?

Your Environment

Raspberry pi 4

Component	Version
ChirpStack Gateway OS	v?.?.?

rpi 1 black screen on boot

Last v3.3.2 release is not booting on pi 1 and screen is black after bootloader.

Steps:

Flash image
start pi

Component	Version
ChirpStack Gateway OS	v3.3.2

Applications / testapp / Integrations / HTTP results in empty POST Messages

HTTP Post seems to be empty.
Config:

Target of HTTP Post is an Apache2 with PHP

if (isset($_POST)) {
    $text = var_export($_POST, true) . "\n\n";
    file_put_contents("dumb.txt", " " . $text, FILE_APPEND);
    echo print_r($_POST, true);
}

Result is dumb.txt containing an empty array:

 array (
)

Expected Behavior

Getting a POST with some data, preferable some json ;)

Support for LORIX One

Is support for LORIX One devices planned?
I mean the ability to build a custom image.

Change default Avahi configuration

I have searched the issues of this repository and believe that this is not a duplicate.

Summary

After system boot, the device shall appear in a bonjour browser in the _workstation._tcp group for easy access. Same shall be done for the _http._tcp group for ChirpStack OS full version.

What is the use-case?

The ChirpStack gateway device will show up as a workstation in bonjour browser and will allow the user to find it easily on the network.
Optionally the ChirpStack gateway will show up as an http Server in bonjour browser for the full edition.

Implementation description

To make device show up in _workstations._tcp group, a change in /etc/avahi/avahi-daemon.conf file, in [publish] section needs to be done: the workstation parameter shall be:
publish-workstation=yes

To add device as an http server in _http._tcp group, you need to add a new file in the /etc/avahi/services/ directory (i.e. /etc/avahi/services/http.service). This file shall contain the following lines:

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
<name replace-wildcards="yes">%h</name>
<service>
<type>_http._tcp</type>
<port>8080</port>
</service>
</service-group>

Can you implement this by yourself and make a pull request?

Unfortunately no. I haven't the skills in Go and in packaging environment.

Additional Software Packages

Please add htop to chirpstack os.

enabled_uplink_channels generated under wrong section in network server toml

Hi,

There is a bug in gateway-config. For RAK831 and RAK2245 shields on US915 band network-server enabled_uplink_channels is generated under [network_server.band], not under [network_server.network_settings]. The effect is that enabled_uplink_channels is not took into considerations and gateway transmits on all channels even if I specify channels in Gateway-Profile.

Now:

[general]
log_level=4

[postgresql]
dsn="postgres://chirpstack_ns:chirpstack_ns@localhost/chirpstack_ns?sslmode=disable"

[network_server]
net_id="000000"

  [network_server.band]
  name="US_902_928"
  enabled_uplink_channels=[48, 49, 50, 51, 52, 53, 54, 55]

Should be

[general]
log_level=4

[postgresql]
dsn="postgres://chirpstack_ns:chirpstack_ns@localhost/chirpstack_ns?sslmode=disable"

[network_server]
net_id="000000"

  [network_server.band]
  name="US_902_928"
  # ADD THIS LINE
  [network_server.network_settings]
  enabled_uplink_channels=[48, 49, 50, 51, 52, 53, 54, 55]

The content of chirpstack-hugo-theme cannot be downloaded

When I tried the first update of chirpstack-gateway-os submodules:

make submodules

there was a problem during cloning chirpstack-hugo-theme repository:

[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

The problem occurs even if I add RSA key to my known_hosts file. For other submodules/repositories I have not encountered this problem.
@brocaar

Install from lora-gateway-os-full-raspberrypi3--20190423151801.mender

Hi Orne,
Can you expain how to install lora-gateway-os-full on working Raspbian Stretch Lite (latest verion) ?

Thanks in advance
Mitek

Can't connect

Hi,

i download lora-gateway-os-full-raspberrypi3--20190423151801.sdimg.gz
Write it to SD card 8GB
Connect RPi 3 Model B Ver 1.2 via Ethernet cable to computer (192.168.1.2) and serial line (pin 15,16) to USB-Serial adapter. No RAK831 connected to RPi.
Add console=serial0,115200 to cmdline.txt
Insert SD to RPi.
No replay (ping/ssh) to 192.168.1.5
No login prompt on serial console
If i add init=/bash/sh than i see prompt on serial console and can see filesystem

Can you help or direction to resolve ?

Thanks in advance

putty.zip

IMST Lite Gateway shield config not working

I’m trying to get Gateway OS running on an IMST Lite Gateway with Raspberry PI 1.
The “chirpstack-concentratord” is crashing continuously.

Mar 12 20:33:31 raspberrypi user.err chirpstack-gateway-bridge[751]: time="2020-03-12T20:33:31Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co

GPS on Pi Zero W

I updated chirpstack-concentratord config with

[gateway]
gps_tty_path="/dev/ttyS0"

However still tries to use ttyAMA0

Feb 11 23:12:00 gw1 user.info chirpstack-concentratord-sx1301[522]: Starting GPS validation loop
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Starting stats loop, stats_interval: 30s
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Starting GPS loop
Feb 11 23:12:00 gw1 user.info chirpstack-concentratord-sx1301[522]: GPS TTY port opened for GPS synchronization, gps_tty_path: /dev/ttyAMA0
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Current concentrator count_us: 2576389
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Concentrator drift, drift_us: -12
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Enabling GPS mode for concentrator counter
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: Starting beacon loop
Feb 11 23:12:00 gw1 user.debug chirpstack-concentratord-sx1301[522]: No beacon frequencies configured, disabling beaconing
Feb 11 23:12:01 gw1 user.warn chirpstack-concentratord-sx1301[522]: GPS time reference is not valid, age: 1581462721.831991473s
Feb 11 23:12:02 gw1 user.warn chirpstack-concentratord-sx1301[522]: GPS time reference is not valid, age: 1581462722.832791572s

Framebuffer DT overlay is set twice

There is a issue with the device tree on the latest kernel for pi 1, somewhere a framebuffer is declared twice.
My issue that i created about it: agherzan/meta-raspberrypi#710

Steps to reproduce this issue

Steps:

Build the image for pi 1
boot

Log output

/var/log/dmesg

[    1.525659] simple-framebuffer 1e513000.framebuffer: framebuffer at 0x1e513000, 0x6d8c00 bytes, mapped to 0x(ptrval)
[    1.525749] simple-framebuffer 1e513000.framebuffer: format=a8r8g8b8, mode=1824x984x32, linelength=7296
[    1.561906] Console: switching to colour frame buffer device 228x61
[    1.594131] simple-framebuffer 1e513000.framebuffer: fb0: simplefb registered!
[    1.595147] sysfs: cannot create duplicate filename '/devices/platform/1e513000.framebuffer'
[    1.595492] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.72 #1
[    1.595707] Hardware name: BCM2835
[    1.595849] Backtrace:
[    1.596000] [<c0015860>] (dump_backtrace) from [<c0015bc4>] (show_stack+0x20/0x24)
[    1.596284]  r7:00000000 r6:cb5ded20 r5:cb522900 r4:cb4c3000
[    1.596510] [<c0015ba4>] (show_stack) from [<c080fd54>] (dump_stack+0x20/0x28)
[    1.596797] [<c080fd34>] (dump_stack) from [<c0266408>] (sysfs_warn_dup+0x60/0x74)
[    1.597086] [<c02663a8>] (sysfs_warn_dup) from [<c026655c>] (sysfs_create_dir_ns+0xec/0x10c)
[    1.597494]  r7:00000000 r6:cb522900 r5:ffffffef r4:cb5ecc10
[    1.597755] [<c0266470>] (sysfs_create_dir_ns) from [<c0815094>] (kobject_add_internal+0x90/0x308)
[    1.598084]  r6:c10633f0 r5:c10633f0 r4:cb5ecc10
[    1.598283] [<c0815004>] (kobject_add_internal) from [<c0815844>] (kobject_add+0x60/0xc4)
[    1.598582]  r9:c0b2e82c r8:c10a5000 r7:00000000 r6:c10633f0 r5:cb5ecc10 r4:00000000
[    1.598888] [<c08157e4>] (kobject_add) from [<c055d4a0>] (device_add+0x100/0x61c)
[    1.599161]  r3:00000000 r2:00000000
[    1.599315]  r6:c10633f0 r5:dbf62988 r4:cb5ecc10
[    1.599512] [<c055d3a0>] (device_add) from [<c0688f74>] (of_device_add+0x40/0x48)
[    1.599791]  r8:c10a5000 r7:00000000 r6:00000000 r5:dbf62988 r4:cb5ecc00
[    1.600048] [<c0688f34>] (of_device_add) from [<c06896fc>] (of_platform_device_create_pdata+0xb4/0xfc)
[    1.600388] [<c0689648>] (of_platform_device_create_pdata) from [<c0689764>] (of_platform_device_create+0x20/0x24)
[    1.600717]  r7:c0a25f90 r6:c114c09c r5:00000000 r4:dbf62988
[    1.600943] [<c0689744>] (of_platform_device_create) from [<c0b0f39c>] (simplefb_init+0x74/0x9c)
[    1.601244] [<c0b0f328>] (simplefb_init) from [<c000ade0>] (do_one_initcall+0x50/0x1d4)
[    1.601508]  r7:00000000 r6:c10a5000 r5:c0b2e84c r4:c0b0f328
[    1.612523] [<c000ad90>] (do_one_initcall) from [<c0add1c8>] (kernel_init_freeable+0x130/0x1f8)
[    1.623427]  r7:c0ad8e50 r6:c10a5000 r5:c0b2e84c r4:c0b5d1f8
[    1.634414] [<c0add098>] (kernel_init_freeable) from [<c08276c8>] (kernel_init+0x18/0x100)
[    1.645502]  r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c08276b0
[    1.656526]  r4:00000000
[    1.667524] [<c08276b0>] (kernel_init) from [<c00090ac>] (ret_from_fork+0x14/0x28)
[    1.678648] Exception stack(0xcb4cffb0 to 0xcb4cfff8)
[    1.689697] ffa0:                                     00000000 00000000 00000000 00000000
[    1.700961] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    1.712138] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    1.723113]  r5:c08276b0 r4:00000000
[    1.734144] kobject_add_internal failed for 1e513000.framebuffer with -EEXIST, don't try to register things with the same name in the same directory.

Your Environment

Component	Version
ChirpStack Gateway OS	v3.3.3

No IMAGE_CMD defined

In a fresh-cloned docker, bitbake is failing because of missing configuration.

~/git/lora-gateway-os$ docker-compose run --rm yocto bash
yocto@f7c1d562c3d4:/lora-gateway-os$ source oe-init-build-env /build/ /lora-gateway-os/bitbake/
yocto@f7c1d562c3d4:/build$ bitbake lora-gateway-os-base
ERROR: /lora-gateway-os/layers/bsp/meta-raspberrypi/recipes-core/images/rpi-test-image.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdimg' - possibly invalid type name or missing support class ETA: 0:01:47
ERROR: /lora-gateway-os/layers/bsp/meta-raspberrypi/recipes-core/images/rpi-hwup-image.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdimg' - possibly invalid type name or missing support class
ERROR: Failed to parse recipe: /lora-gateway-os/layers/bsp/meta-raspberrypi/recipes-core/images/rpi-test-image.bb
ERROR: /lora-gateway-os/layers/bsp/meta-raspberrypi/recipes-core/images/rpi-basic-image.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdimg' - possibly invalid type name or missing support class

Summary: There were 4 ERROR messages shown, returning a non-zero exit code.
yocto@f7c1d562c3d4:/build$

Support for raspberry pi 2

For the supported hardware, Lorix ONE and RPi 3 is on the list.
Is RPi 2 supported?

Image does not boot on RPI without HDMI attached

Hi,

I loaded this image onto the raspberry pi, but it doesn't seem to boot to ssh unless I have HDMI (or a HDMI dummy) attached to the PI.

There is also a reference to this on the forums: https://forum.loraserver.io/t/lora-gateway-os-not-booting-with-out-hdmi-or-keyboard/4126/3

bitbake lora-gateway-os-base error on master branch

lora-packet-forwarder_4.0.1.bb fails with the following errors:

yocto@37458b161cfb:/build$ bitbake lora-gateway-os-base
Loading cache: 100% |##################################################################################################################################################################| Time: 0:00:01
Loaded 3089 entries from dependency cache.
WARNING: /lora-gateway-os/layers/loraserver/meta-semtech/recipes-lora/lora-packet-forwarder/lora-packet-forwarder_4.0.1.bb: Unable to get checksum for lora-packet-forwarder SRC_URI entry global_conf.eu868.json: file could not be found
WARNING: /lora-gateway-os/layers/loraserver/meta-semtech/recipes-lora/lora-packet-forwarder/lora-packet-forwarder_4.0.1.bb: Unable to get checksum for lora-packet-forwarder SRC_URI entry global_conf.eu868.json.gps: file could not be found
WARNING: /lora-gateway-os/layers/loraserver/meta-semtech/recipes-lora/lora-packet-forwarder/lora-packet-forwarder_4.0.1.bb: Unable to get checksum for lora-packet-forwarder SRC_URI entry global_conf.us915.json: file could not be found
WARNING: /lora-gateway-os/layers/loraserver/meta-semtech/recipes-lora/lora-packet-forwarder/lora-packet-forwarder_4.0.1.bb: Unable to get checksum for lora-packet-forwarder SRC_URI entry global_conf.us915.json.gps: file could not be found
Parsing recipes: 100% |################################################################################################################################################################| Time: 0:02:06
Parsing of 2131 .bb files complete (0 cached, 2131 parsed). 3089 targets, 149 skipped, 0 masked, 0 errors.
ERROR: No recipes available for:
/lora-gateway-os/meta/recipes-mender/mender/mender_%.bbappend

Summary: There were 4 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Using ChirpStack layer on other Yocto Image

I've been trying to port ChirpStack into the example yocto image for Simatic IOT2000.
What I've done is:
Copy the following folders from layers to my building path
chirpstack-gateway-os/layers/meta-clang
chirpstack-gateway-os/layers/meta-rust-bin
chirpstack-gateway-os/layers/chirpstack

Add them to bblayers.conf
Add the corresponding packets to IMAGE_INSTALL_APPEND

Then while bitbakin i got these errors:
chirpstack-gateway-bridge-3.7.1-r1 do_package: QA Issue: File '/usr/bin/chirpstack-gateway-bridge' from chirpstack-gateway-bridge was already stripped, this will prevent future debugging! [already-stripped]

For every packet from chirpstack. No problem with other utilities.
Can I get some help?

Documentation of build environment ( Ubuntu version, RAM memory on build machine, etc )

[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Summary

Problem:
I set up a virtual machine running Ubuntu 20.04LTS ( released a few months back ). The 3.3.0 version of chirpstack does not build there (fails on "gettext") . If running on Ubuntu 18.04.05LTS it builds just fine.

Clang does not build on 18.04.05 with 16Gb of memory. When allocating 32 Gb of RAM on my virtual build machine it works fine.

The disk also needs to be bigger than 32 Gb to work ( 200 Gb is fine )

What is the use-case?

I run node-red on the full version of chirpstack-gateway-os and need to include it in the build. Thus I need to build the images myself.
We also use a lot of virtual machines for doing builds. Even though I use a physical Vmware ESXi server it is also possible to set up really powerful buildservers on Amazon AWS and just power them on ( and pay ) when doing builds. In order to do this, I need to know how big the disk should be, how much RAM is required, which operating system to use etc.

Implementation description

I hope for a comment in the readme.md under https://github.com/brocaar/chirpstack-gateway-os#building-images "The pre-built images was built on an Ubuntu 18.04.05 Linux with 32 Gbyte of Ram and 512 gb of disk. A complete build took 4 hours."

Can you implement this by yourself and make a pull request?

Yes. I'll try.

tcpdump missing from chirpstack-gateway-os-base

I changed MACHINE to raspberrypi0-wifi, build seems successful, cannot see any errors.
I did have to manually copy image to deploy folder. However I am missing tcpdump from the image. Concentratord and Gateway Bridge are running but I cannot troubleshoot connections.
I don't know where in the build process it;s going wrong.

master...mrbubble62:master

rootfs-overlay error during build

When i wan't to build the Image in the Docker container with the command bitbake chirpstack-gateway-os-base i get the flowing error:

ERROR: rootfs-overlay-initramfs-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed, details in /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/temp/log.do_rootfs
ERROR: rootfs-overlay-initramfs-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/temp/log.do_rootfs.20245
ERROR: Task (/chirpstack-gateway-os/meta/recipes-core/images/rootfs-overlay-initramfs.bb:do_rootfs) failed with exit code '1'

Full build log:

DEBUG: Executing python function extend_recipe_sysroot
NOTE: Direct dependencies are ['virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-extended/pbzip2/pbzip2_1.1.13.bb:do_populate_sysroot', '/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-extended/pigz/pigz_2.4.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.6.bb:do_populate_sysroot', '/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-core/glibc/cross-localedef-native_2.28.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', 'virtual:native:/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-devtools/opkg/opkg_0.3.6.bb:do_populate_sysroot', '/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', '/chirpstack-gateway-os/layers/openembedded/openembedded-core/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot']
NOTE: Installed into sysroot: []
NOTE: Skipping as already exists in sysroot: ['bmap-tools-native', 'pbzip2-native', 'qemuwrapper-cross', 'update-rc.d-native', 'pigz-native', 'pseudo-native', 'opkg-utils-native', 'cross-localedef-native', 'makedevs-native', 'opkg-native', 'depmodwrapper-cross', 'ldconfig-native', 'xz-native', 'python3-native', 'quilt-native', 'python3-setuptools-native', 'bzip2-native', 'qemu-native', 'zlib-native', 'autoconf-native', 'libtool-native', 'automake-native', 'gnu-config-native', 'openssl-native', 'debianutils-native', 'pkgconfig-native', 'libarchive-native', 'libsolv-native', 'kmod-native', 'gettext-minimal-native', 'sqlite3-native', 'readline-native', 'gdbm-native', 'unzip-native', 'pixman-native', 'glib-2.0-native', 'alsa-lib-native', 'dtc-native', 'm4-native', 'texinfo-dummy-native', 'lzo-native', 'e2fsprogs-native', 'rpm-native', 'cmake-native', 'ninja-native', 'expat-native', 'gtk-doc-native', 'ncurses-native', 'libpng-native', 'util-macros-native', 'util-linux-native', 'libffi-native', 'gettext-native', 'libpcre-native', 'flex-native', 'attr-native', 'elfutils-native', 'file-native', 'popt-native', 'nss-native', 'dbus-native', 'db-native', 'curl-native', 're2c-native', 'nspr-native']
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing python function do_rootfs
NOTE: Initializing intercept dir for /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs
DEBUG: Collected intercepts:
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/delay_to_first_boot
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/postinst_intercept
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_font_cache
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_gio_module_cache
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_gtk_immodules_cache
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_icon_cache
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_pixbuf_cache
  /chirpstack-gateway-os/layers/openembedded/openembedded-core/scripts/postinst-intercepts/update_udev_hwdb

NOTE: ###### Generate rootfs #######
NOTE: Executing '/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg-make-index -r /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/Packages -p /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/Packages -m /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4' ...
NOTE: Executing '/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg-make-index -r /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/raspberrypi3/Packages -p /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/raspberrypi3/Packages -m /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/raspberrypi3' ...
NOTE: Executing '/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg-make-index -r /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/all/Packages -p /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/all/Packages -m /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/all' ...
NOTE: Installing the following packages: base-passwd busybox initramfs-readonly-rootfs-overlay run-postinsts udev
NOTE: /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/opkg.conf -t /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/temp/ipktemp/ -o /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   install base-passwd busybox initramfs-readonly-rootfs-overlay run-postinsts udev
NOTE:  Removing any system startup links for run-postinsts ...
 Removing any system startup links for udev ...
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ash to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/cat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/chattr to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/chgrp to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/chmod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/chown to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/cp to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/cpio to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/date to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/dd to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/df to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/dmesg to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/dnsdomainname to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/dumpkmap to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/echo to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/egrep to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/false to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/fgrep to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/getopt to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/grep to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/gunzip to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/gzip to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/hostname to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/kill to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ln to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ls to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/mkdir to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/mknod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/mktemp to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/more to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/mount to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/mv to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/netstat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/pidof to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ps to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/pwd to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/rm to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/rmdir to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/run-parts to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/sed to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/sh to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/sleep to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/stat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/stty to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/sync to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/tar to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/touch to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/true to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/umount to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/uname to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/usleep to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/vi to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/watch to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/zcat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/blkid to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/depmod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/fdisk to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/fsck to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/fstrim to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/getty to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/hwclock to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/ifconfig to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/ifdown to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/ifup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/insmod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/ip to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/loadkmap to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/logread to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/losetup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/lsmod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/mkswap to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/modprobe to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/pivot_root to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/reboot to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/rmmod to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/route to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/setconsole to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/start-stop-daemon to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/sulogin to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/swapoff to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/swapon to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/switch_root to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/sysctl to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/sbin/udhcpc to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/[ to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/[[ to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/awk to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/basename to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/bunzip2 to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/bzcat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/chvt to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/clear to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/cmp to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/cut to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/dc to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/deallocvt to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/diff to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/dirname to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/du to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/dumpleases to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/env to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/expr to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/find to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/flock to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/free to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/fuser to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/groups to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/head to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/hexdump to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/id to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/killall to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/less to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/logger to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/logname to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/lzcat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/md5sum to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/mesg to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/microcom to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/mkfifo to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/nc to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/nohup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/nproc to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/nslookup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/od to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/openvt to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/patch to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/printf to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/readlink to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/realpath to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/renice to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/reset to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/resize to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/seq to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/sha1sum to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/sha256sum to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/shuf to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/sort to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/strings to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/tail to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/tee to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/telnet to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/test to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/tftp to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/time to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/top to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/tr to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/tty to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/uniq to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/unlink to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/unzip to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/uptime to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/users to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/wc to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/wget to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/which to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/who to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/whoami to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/xargs to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/xzcat to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/yes to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/addgroup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/adduser to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/chroot to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/delgroup to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/deluser to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/fbset to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/loadfont to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/rdate to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/rfkill to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/sbin/udhcpd to /bin/busybox.nosuid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/login to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ping to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/ping6 to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/bin/su to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/passwd to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/traceroute to /bin/busybox.suid
update-alternatives: Linking /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/bin/vlock to /bin/busybox.suid
 Adding system startup for /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/etc/init.d/udev.
 Adding system startup for /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/etc/init.d/run-postinsts.
Installing base-passwd (3.5.29) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/base-passwd_3.5.29-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing initramfs-readonly-rootfs-overlay (1.1.0) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/raspberrypi3/initramfs-readonly-rootfs-overlay_1.1.0-r3_raspberrypi3.ipk.
Installing libc6 (2.28) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/libc6_2.28-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing update-alternatives-opkg (0.3.6) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/update-alternatives-opkg_0.3.6-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing busybox-udhcpc (1.29.3) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/busybox-udhcpc_1.29.3-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing update-rc.d (0.8) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/all/update-rc.d_0.8-r0_all.ipk.
Installing libz1 (1.2.11) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/libz1_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing libuuid1 (2.32.1) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/libuuid1_2.32.1-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing busybox (1.29.3) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/busybox_1.29.3-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing run-postinsts (1.0) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/all/run-postinsts_1.0-r10_all.ipk.
Installing libkmod2 (25+git0+aca4eca103) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/libkmod2_25+git0+aca4eca103-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing libblkid1 (2.32.1) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/libblkid1_2.32.1-r0_cortexa7t2hf-neon-vfpv4.ipk.
Installing eudev (3.2.7) on root
Downloading file:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/oe-rootfs-repo/cortexa7t2hf-neon-vfpv4/eudev_3.2.7-r0_cortexa7t2hf-neon-vfpv4.ipk.
Configuring libc6.
Configuring update-alternatives-opkg.
Configuring busybox-udhcpc.
Configuring busybox.
Configuring libuuid1.
Configuring initramfs-readonly-rootfs-overlay.
Configuring libblkid1.
Configuring libz1.
Configuring libkmod2.
Configuring update-rc.d.
Configuring eudev.
Configuring base-passwd.
Configuring run-postinsts.

NOTE: Installing complementary packages ...
NOTE: Running ['oe-pkgdata-util', '-p', '/build/tmp/raspberrypi/raspberrypi3-glibc/pkgdata/raspberrypi3', 'glob', '/tmp/installed-pkgsl66aarm0', '']
NOTE: Running intercept scripts:
NOTE: > Executing update_gio_module_cache intercept ...
NOTE: Exit code 1. Output:
+ [ True = False ]
+ qemu-arm -r 3.2.0 -E LD_LIBRARY_PATH=/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/lib:/build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/lib -L /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/libexec/gio-querymodules /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/rootfs/usr/lib/gio/modules/

ERROR: The postinstall intercept hook 'update_gio_module_cache' failed, details in /build/tmp/raspberrypi/raspberrypi3-glibc/work/raspberrypi3-oe-linux-gnueabi/rootfs-overlay-initramfs/1.0-r0/temp/log.do_rootfs
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

Update dependencies

The Yocto layers you are referred to are slightly outdated.
Do you plan to make an update in the near future?

LoRa-Gateway-OS Full produces incomplete packet-forwarder global_conf.json for US915

The global_conf.json file produced has no table lookups for US915. I'm using a RAK831 Pilot Gateway, and I selected the RAK831 Development Kit for the Concentrator.

no ethernet with test4-image

want try out mender upgrade and so I flashed test2 to my raspberrypi3 b+. After upgrade it to test4 via a mender (URL: https://artifacts.loraserver.io/downloads/lora-gateway-os/raspberrypi/raspberrypi3/2.0.0test4/) and a reboot it lost the ethernet connection, back to test2 ethernet was there again.

Chirpstack concentratord building error

Hello,
I've encountered the problem with concentratord package during chirpstack-gateway-os-full build process. I was building the image on Ubuntu 18.04 LTS, all necessary packages and toolchain for Yocto Project already installed. It looks like some dependency error for rustc.

Chirpstack Gateway OS revision

The logs fragment regarding the issue:

|   running: "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/cc-native-wrapper.sh" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-O2" "-pipe" "-g" "-feliminate-unused-debug-types" "-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot=" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot-native=" "-o" "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-8b4570a569a949e1/out/src/os/unix/global_static.o" "-c" "src/os/unix/global_static.c"
|   cargo:warning=gcc: error: unrecognized command line option ‘-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1’
|   exit code: 1
| 
|   --- stderr
| 
| 
|   error occurred: Command "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/cc-native-wrapper.sh" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-O2" "-pipe" "-g" "-feliminate-unused-debug-types" "-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot=" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot-native=" "-o" "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-8b4570a569a949e1/out/src/os/unix/global_static.o" "-c" "src/os/unix/global_static.c" with args "cc-native-wrapper.sh" did not execute successfully (status code exit code: 1).
| 
| 
| warning: build failed, waiting for other jobs to finish...
| error: build failed
| WARNING: exit code 101 from a shell command.
| ERROR: Execution of '/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/temp/run.do_compile.22309' failed with exit code 101:
|        Fresh unicode-xid v0.2.0
|        Fresh cc v1.0.50
|        Fresh autocfg v1.0.0
|        Fresh cfg-if v0.1.10
|        Fresh version_check v0.1.5
|        Fresh either v1.5.3
|        Fresh glob v0.3.0
|        Fresh regex-syntax v0.6.14
|        Fresh lazy_static v1.4.0
|        Fresh bytes v0.5.4
|        Fresh pkg-config v0.3.17
|        Fresh toml v0.2.1
|        Fresh error-chain v0.10.0
|        Fresh termcolor v1.1.0
|        Fresh unicode-segmentation v1.6.0
|        Fresh rustc-hash v1.1.0
|        Fresh fixedbitset v0.2.0
|        Fresh peeking_take_while v0.1.2
|        Fresh shlex v0.1.1
|        Fresh remove_dir_all v0.5.2
|        Fresh lazycell v1.2.1
|        Fresh futures-core v0.3.4
|        Fresh multimap v0.8.0
|        Fresh pin-project-lite v0.1.4
|        Fresh fnv v1.0.6
|        Fresh itoa v0.4.5
|        Fresh ppv-lite86 v0.2.6
|        Fresh pin-utils v0.1.0-alpha.4
|        Fresh tower-service v0.3.0
|        Fresh futures-sink v0.3.4
|        Fresh futures-task v0.3.4
|        Fresh unicode-width v0.1.7
|        Fresh percent-encoding v1.0.1
|        Fresh void v1.0.2
|        Fresh vec_map v0.8.1
|        Fresh strsim v0.8.0
|        Fresh ansi_term v0.11.0
|        Fresh quick-error v1.2.3
|        Fresh arc-swap v0.4.5
|        Fresh hex v0.4.2
|        Fresh cmake v0.1.42
|        Fresh thread_local v1.0.1
|        Fresh itertools v0.8.2
|        Fresh tracing-core v0.1.9
|        Fresh metadeps v1.1.2
|        Fresh heck v0.3.1
|        Fresh http v0.2.0
|        Fresh tokio v0.2.11
|        Fresh c2-chacha v0.2.3
|        Fresh futures-util v0.3.4
|        Fresh textwrap v0.11.0
|        Fresh humantime v1.3.0
|        Fresh zeromq-src v0.1.8+4.3.2
|    Compiling libloading v0.5.2
|        Fresh libc v0.2.66
|        Fresh log v0.4.8
|      Running `/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-cb7b018aa809cc7e/build-script-build`
|        Fresh proc-macro2 v1.0.8
|        Fresh memchr v2.3.2
|        Fresh anyhow v1.0.26
|        Fresh bitflags v1.2.1
|    Compiling http-body v0.3.1
|        Fresh tower-make v0.3.0
|        Fresh byteorder v1.3.4
|    Compiling indexmap v1.3.2
|      Running `rustc --crate-name http_body --edition=2018 /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/github.com-1ecc6299db9ec823/http-body-0.3.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=8649422dfd444137 -C extra-filename=-8649422dfd444137 --out-dir /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps --target armv7-unknown-linux-gnueabihf -C linker=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/linker-wrapper.sh -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern bytes=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps/libbytes-5d2c809e61e64d9e.rmeta --extern http=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/armv7-unknown-linux-gnueabihf/release/deps/libhttp-54d33158dc617507.rmeta --cap-lints allow`
|    Compiling which v3.1.0
|      Running `rustc --crate-name indexmap /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/github.com-1ecc6299db9ec823/indexmap-1.3.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=8fb89b3b1dc68577 -C extra-filename=-8fb89b3b1dc68577 --out-dir /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps -C linker=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/linker-native-wrapper.sh -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --cap-lints allow --cfg has_std`
|    Compiling getrandom v0.1.14
|      Running `rustc --crate-name which /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/github.com-1ecc6299db9ec823/which-3.1.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=4c02c31949687ae1 -C extra-filename=-4c02c31949687ae1 --out-dir /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps -C linker=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/linker-native-wrapper.sh -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern libc=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps/liblibc-e67e84f46eecfe68.rmeta --cap-lints allow`
|    Compiling atty v0.2.14
|      Running `rustc --crate-name getrandom --edition=2018 /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/github.com-1ecc6299db9ec823/getrandom-0.1.14/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 --cfg 'feature="std"' -C metadata=794ed87a7ab195c5 -C extra-filename=-794ed87a7ab195c5 --out-dir /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps -C linker=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/linker-native-wrapper.sh -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern cfg_if=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps/libcfg_if-dfee4a32393c1242.rmeta --extern libc=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps/liblibc-e67e84f46eecfe68.rmeta --cap-lints allow`
|      Running `rustc --crate-name atty /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/cargo_home/registry/src/github.com-1ecc6299db9ec823/atty-0.2.14/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -Cembed-bitcode=no -C debuginfo=2 -C metadata=a055b837389f423a -C extra-filename=-a055b837389f423a --out-dir /Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps -C linker=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/linker-native-wrapper.sh -L dependency=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps --extern libc=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/deps/liblibc-e67e84f46eecfe68.rmeta --cap-lints allow`
| The following warnings were emitted during compilation:
| 
| warning: gcc: error: unrecognized command line option ‘-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1’
| 
| error: failed to run custom build command for `libloading v0.5.2`
| 
| Caused by:
|   process didn't exit successfully: `/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-cb7b018aa809cc7e/build-script-build` (exit code: 1)
|   --- stdout
|   cargo:rustc-link-lib=dl
|   TARGET = Some("x86_64-unknown-linux-gnu")
|   OPT_LEVEL = Some("3")
|   HOST = Some("x86_64-unknown-linux-gnu")
|   CC_x86_64-unknown-linux-gnu = None
|   CC_x86_64_unknown_linux_gnu = None
|   HOST_CC = None
|   CC = Some("/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/cc-native-wrapper.sh")
|   CFLAGS_x86_64-unknown-linux-gnu = None
|   CFLAGS_x86_64_unknown_linux_gnu = None
|   HOST_CFLAGS = None
|   CFLAGS = Some(" -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1                      -fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1                      -fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot=                      -fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot-native= ")
|   CRATE_CC_NO_DEFAULTS = None
|   DEBUG = Some("true")
|   CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
|   running: "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/cc-native-wrapper.sh" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-O2" "-pipe" "-g" "-feliminate-unused-debug-types" "-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot=" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot-native=" "-o" "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-8b4570a569a949e1/out/src/os/unix/global_static.o" "-c" "src/os/unix/global_static.c"
|   cargo:warning=gcc: error: unrecognized command line option ‘-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1’
|   exit code: 1
| 
|   --- stderr
| 
| 
|   error occurred: Command "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/wrappers/cc-native-wrapper.sh" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-O2" "-pipe" "-g" "-feliminate-unused-debug-types" "-fmacro-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1=/usr/src/debug/chirpstack-concentratord/3.0.2-r1" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot=" "-fdebug-prefix-map=/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/recipe-sysroot-native=" "-o" "/Projects/chirpstack-gateway-os/build/tmp/raspberrypi/raspberrypi3-glibc/work/cortexa7t2hf-neon-vfpv4-oe-linux-gnueabi/chirpstack-concentratord/3.0.2-r1/target/release/build/libloading-8b4570a569a949e1/out/src/os/unix/global_static.o" "-c" "src/os/unix/global_static.c" with args "cc-native-wrapper.sh" did not execute successfully (status code exit code: 1).
| 
| 
| warning: build failed, waiting for other jobs to finish...
| error: build failed
| WARNING: exit code 101 from a shell command.
| 
ERROR: Task (/Projects/chirpstack-gateway-os/layers/chirpstack/meta-chirpstack/recipes-chirpstack/chirpstack-concentratord/chirpstack-concentratord_3.0.2.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 642 tasks of which 641 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /Projects/chirpstack-gateway-os/layers/chirpstack/meta-chirpstack/recipes-chirpstack/chirpstack-concentratord/chirpstack-concentratord_3.0.2.bb:do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks

Support for Raspberry pi 4

Hi!

The current version is 3.0.0-test2 is support up to pi3.
Can you modify the image for the new raspberry pi 4?

Thank you!

chirpstack / chirpstack-gateway-os Goto Github PK

chirpstack-gateway-os's Introduction

ChirpStack Gateway OS

Documentation and binaries

Building from source

Requirements

Initialize

Update

Build

Switch configuration

Building image

Making configuration changes

Links

chirpstack-gateway-os's People

Contributors

Stargazers

Watchers

Forkers

chirpstack-gateway-os's Issues

Is this a bug or a feature request?

What did you expect?

What happened?

What version are your using?

What happened?

What did you expect?

Steps to reproduce this issue

Could you share your log output?

Your Environment

Summary

What is the use-case?

Implementation description

Can you implement this by yourself and make a pull request?

Steps to reproduce this issue

Log output

Your Environment

Summary

What is the use-case?

Implementation description

Can you implement this by yourself and make a pull request?

Recommend Projects

Recommend Topics

Recommend Org