Bug #4837
closedcan't start osmo-msc: Assert failed multiple command.c:413
0%
Description
If I try my old osmo-msc.cfg, -c /dev/null or the default from osmo-msc/doc/examples/osmo-msc/osmo-msc.cfg I get the following error:
I am using osmo-msc 1.6.3 on a rpi B I think, from
deb https://download.opensuse.org/repositories/network:/osmocom:/latest/Raspbian_10/
root@nitb:~# osmo-msc -e 1 <0013> rate_ctr.c:88 validating counter group 0x77ab8(msc) with 29 counters Assert failed multiple command.c:413 backtrace() returned 0 addresses Aborted
a backtrace from gdb:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x76a87230 in __GI_abort () at abort.c:79 #2 0x76eeabb8 in osmo_panic () from /usr/lib/arm-linux-gnueabihf/libosmocore.so.16 #3 0x76f983a0 in install_element () from /usr/lib/arm-linux-gnueabihf/libosmovty.so.4 #4 0x76f984c8 in install_element_ve () from /usr/lib/arm-linux-gnueabihf/libosmovty.so.4 #5 0x0001db70 in msc_vty_init (msc_network=0xdaa58) at msc_vty.c:2016 #6 0x00017590 in main (argc=<optimized out>, argv=0x7efff7a4) at msc_main.c:555
sample config slightly modified for my environment (ip addr for line vty and mgw remote-ip):
/etc/osmocom/osmo-msc.cfg ! ! OsmoMSC configuration saved from vty ! line vty bind 192.168.1.118 ! network network country code 1 mobile network code 1 short name OsmoMSC long name OsmoMSC encryption a5 0 rrlp mode none mm info 1 msc mgw remote-ip 192.168.1.118 mgw remote-port 2427 mgw local-port 2728 assign-tmsi auth-tuple-max-reuse-count 3 auth-tuple-reuse-on-error 1 log stderr logging filter all 1 logging print extended-timestamp 1 logging print category 1 logging print category-hex 0 logging print level 1 logging print file basename last logging level set-all info
Updated by laforge over 2 years ago
- Status changed from New to Feedback
- Assignee set to unrznbl
to me it looks like you have some kind of incompatible binaries installed. Please make sure you always only use all osmocom packages either from the nightly or from the latest feed. Don't mix between those two, and particularly don't mix with any packages provided by distributions.
Updated by unrznbl over 2 years ago
You were right. I had incorrect versions for osmo vty and osmo ctrl. Updated those and things work now. Thanks!