Project

General

Profile

Actions

Bug #6107

closed

Error when running osmo-msc on Raspberry Pi with sgs configuration

Added by herlesupreeth 7 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/21/2023
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

I am using osmomsc in the testbed (https://github.com/herlesupreeth/docker_open5gs) to send SMS over SGs interface. And, one of the users (discussion thread here - https://github.com/herlesupreeth/docker_open5gs/discussions/188. Its rather lengthy :P ) of the repo is facing an error when trying to do so on a Raspberry Pi running Ubuntu 22.04.

If the sgs section is commented out in the configuration file (https://github.com/herlesupreeth/docker_open5gs/blob/master/osmomsc/osmo-msc.cfg) the MSC is up and running but left uncommented leads to an error. I am not able to figure why figure out why its failing. I am attaching the output of strace and docker build log shared in that discussion here. Let me know if you need further information.

Appreciate all the help.


Files

build_strace.log.txt build_strace.log.txt 30 KB herlesupreeth, 07/21/2023 12:58 PM
osmomsc.strace.log osmomsc.strace.log 19 KB herlesupreeth, 07/21/2023 12:58 PM
Actions #1

Updated by laforge 7 months ago

Can you try using the binary package feed we provide? Just to exclude any build environments related topics? We di have nightly and latest feed for raspbian and debian on raspi. The debian one should work on ubuntu

Actions #2

Updated by herlesupreeth 7 months ago

I am using the binary packages as follows in the docker


RUN wget https://downloads.osmocom.org/packages/osmocom:/latest/xUbuntu_20.04/Release.key && \
    mv Release.key /etc/apt/trusted.gpg.d/osmocom-latest.asc && \
    echo "deb https://downloads.osmocom.org/packages/osmocom:/latest/xUbuntu_20.04/ ./" > /etc/apt/sources.list.d/osmocom-latest.list && \
    apt-get update && apt-get -y install osmo-msc

Actions #3

Updated by herlesupreeth 7 months ago

Also, I had to install libdbd-sqlite3 separately in order for osmo-msc to work (without sgs section). Or else it used to complain as follows

<0009> db.c:619 Failed to create database connection to sqlite3 db 'sms.db'; Is the sqlite3 database driver for libdbi installed on this system?
DB: Failed to init database: sms.db
Actions #4

Updated by laforge 7 months ago

  • Assignee set to osmith

osmith, please have a look.

Clearly the libdbd-sqlite3 package should be a mandatory dependency for the osmo-msc package.

Actions #5

Updated by laforge 7 months ago

At least as far as I can tell, in current master (corresponds to the nightly feed), osmo-msc has no optional dependencies or --enable compile flags regarding SGs. SGs is always there, and it cannot be disabled at build time. I also don't recall this ever having been different.

Quite mysterious.

Actions #6

Updated by laforge 7 months ago

Ah, you are installing the osmo-msc package from ubuntu itself, not from the osmocom package feeds:

#6 13.58 Get:14 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 osmo-msc arm64 1.2.0-3 [113 kB]

And ubuntu ships an ancient version (1.2.0 from 2018) while our latest tagged version is 1.10.0. The SGs was first introduced in 1.4.0

So whatever you're doing, your APT configuration seems to be set up in a way that it doesn't know of the osmocom repositorires, or tha the priority of an ubuntu package is higher than an osmocom package, even though it has a much lower pacakge version.

Actions #7

Updated by fixeria 7 months ago

laforge wrote in #note-4:

Clearly the libdbd-sqlite3 package should be a mandatory dependency for the osmo-msc package.

Not anymore for the recent packages (both nightly and latest), since osmo-msc is now using libsqlite3 directly.

Actions #8

Updated by laforge 7 months ago

  • Status changed from New to Feedback
  • Assignee changed from osmith to herlesupreeth

So all of th problems you are reporting are about the ubuntu distribution package of osmo-msc, and not the osmocom-released. Please address them to ubuntu.

The reason you are not using an osmocom package is also clear: We don't do ARM builds for Ubuntu, as in our experience that's a very unusual configuration, and we cannot support every distribution on every architecture. Also, in general, I think Ubuntu is departing more and more from what we know of as Linux distribution over the last 25+ years. It's insistence on moving away from dpkg towards its proprietary SNAP environment makes it a platform that is in my opinion becoming rather non-free.

You can see the distributions and architectures we build osmo-msc "latest" at
https://obs.osmocom.org/package/show/osmocom:latest/osmo-msc

This shows that only Debian 10/11 and Raspbian 10/11 are built on ARM.

Actions #9

Updated by herlesupreeth 7 months ago

Thanks a lot for taking a look at this. I didnt realize I was installing the osmo-msc package from ubuntu itself, not from the osmocom package.

We don't do ARM builds for Ubuntu, as in our experience that's a very unusual configuration, and we cannot support every distribution on every architecture. Also, in general, I think Ubuntu is departing more and more from what we know of as Linux distribution over the last 25+ years. It's insistence on moving away from dpkg towards its proprietary SNAP environment makes it a platform that is in my opinion becoming rather non-free.

Ah I see. Then, I will use Debian as base image in my repository then.

Is it okay if I keep this issue open until Monday so that the user can test on his RPi setup and see if he still faces issue or not?

Actions #10

Updated by herlesupreeth 7 months ago

Thank you laforge . Issue is resolved by using latest osmo-msc package. This issue can be closed.

Actions #11

Updated by laforge 7 months ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)