Runtime issue in Nucleus MME

Namrata Ghodeswar

unread,

Feb 8, 2021, 4:40:09 AM2/8/21

to OMEC Developers

Getting following run time error in Nucleus MME. Running it using docker on ubuntu 18.04 version.

Start MME application

Program name set to ./bin/mme-app

Caught SIGSEGV: Segmentation Fault

sh: 1: addr2line: not found

error determining line # for: ./lib/libmonitor_config.so(posix_print_stack_trace+0x19) [0x7f4eb00d8849]

sh: 1: addr2line: not found

error determining line # for: ./lib/libmonitor_config.so(posix_signal_handler+0x47) [0x7f4eb00d8927]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7f4eb0dcb980]

Server listening on 0.0.0.0:50051

sh: 1: addr2line: not found

error determining line # for: ./bin/mme-app(+0xf7d28) [0x560a45c2ed28]

sh: 1: addr2line: not found

error determining line # for: ./bin/mme-app(+0xf7ead) [0x560a45c2eead]

sh: 1: addr2line: not found

error determining line # for: /usr/local/lib/libstdc++.so.6(+0xbd6df) [0x7f4eaec8b6df]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7f4eb0dc06db]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f4eae34871f]

Program name set to ./bin/s1ap-app

Namrata Ghodeswar

unread,

Feb 8, 2021, 8:14:10 AM2/8/21

to OMEC Developers, Namrata Ghodeswar

Kindly refer to the following log info in addition to the above error

init_logging hostbased
./bin/mme-app(12:12):DEBUG-timeoutManager.cpp:49:Timer created successfully
./bin/mme-app(12:14):DEBUG-timeoutManager.cpp:127:Run TimeoutManager
./bin/mme-app(12:12):ERROR-tipcSocket.cpp:64:Failed to bind TIPC socket. error: Bad file descriptor
./bin/mme-app(12:12):ERROR-interfaces/mmeIpcInterface.cpp:50:MmeIpcInterface Setup Failed!!!
./bin/mme-app(12:12):INFO-parse_config.cpp:250:Parsed plmn mcc - 315 mnc - 10
./bin/mme-app(12:12):INFO-parse_config.cpp:272:Configured plmn 13 5 1
./bin/mme-app(12:12):INFO-parse_config.cpp:250:Parsed plmn mcc - 208 mnc - 1
./bin/mme-app(12:12):INFO-parse_config.cpp:272:Configured plmn 2 8 10
./bin/mme-app(12:12):DEBUG-parse_config.cpp:34:alg_list : [EIA1, EIA2, EIA0]
./bin/mme-app(12:12):DEBUG-parse_config.cpp:36:substring : EIA1, EIA2, EIA0
./bin/mme-app(12:12):DEBUG-parse_config.cpp:49:algs : EIA1
./bin/mme-app(12:12):DEBUG-parse_config.cpp:49:algs : EIA2
./bin/mme-app(12:12):DEBUG-parse_config.cpp:49:algs : EIA0
./bin/mme-app(12:12):DEBUG-parse_config.cpp:84:alg_list : [EEA0, EEA1, EEA2]
./bin/mme-app(12:12):DEBUG-parse_config.cpp:86:substring : EEA0, EEA1, EEA2
./bin/mme-app(12:12):DEBUG-parse_config.cpp:98:algs : EEA0
./bin/mme-app(12:12):DEBUG-parse_config.cpp:98:algs : EEA1
./bin/mme-app(12:12):DEBUG-parse_config.cpp:98:algs : EEA2
./bin/mme-app(12:12):INFO-parse_config.cpp:320:Configured service apn name to ip addresss/service name mapping.
./bin/mme-app(12:12):INFO-parse_config.cpp:321:Configured apn comment
./bin/mme-app(12:12):INFO-parse_config.cpp:320:Configured service spgwc-headless
./bin/mme-app(12:12):INFO-parse_config.cpp:321:Configured apn internet
./bin/mme-app(12:12):INFO-parse_config.cpp:320:Configured service spgwc-headless
./bin/mme-app(12:12):INFO-parse_config.cpp:321:Configured apn apps
./bin/mme-app(12:12):DEBUG-parse_config.cpp:329:mme_name : vmmestandalone
./bin/mme-app(12:12):DEBUG-parse_config.cpp:330:mme_groupid : 1
./bin/mme-app(12:12):DEBUG-parse_config.cpp:331:mme_code : 1
./bin/mme-app(12:12):DEBUG-parse_config.cpp:332:logging :
./bin/mme-app(12:12):DEBUG-parse_config.cpp:333:MCC : 2 0 8
./bin/mme-app(12:12):DEBUG-parse_config.cpp:334:MNC : 0 1 -1
./bin/mme-app(12:12):ERROR-parse_config.cpp:392: apn name to ip addresss/service name mapping. - getaddr info failed Temporary failure in name resolution
./bin/mme-app(12:12):DEBUG-utils/mmeTimerUtils.cpp:45:Timer started. duration 10000./bin/mme-app(12:12):ERROR-parse_config.cpp:392:spgwc-headless - getaddr info failed Temporary failure in name resolution
./bin/mme-app(12:12):ERROR-parse_config.cpp:392:spgwc-headless - getaddr info failed Temporary failure in name resolution

Anjana Sreekumar

unread,

Feb 8, 2021, 8:41:43 AM2/8/21

to Namrata Ghodeswar, OMEC Developers

Hi,

Please execute ‘modprobe tipc’ to enable TIPC kernel module and try starting the mme-app again.

Thanks,

Anjana

From: omec...@opennetworking.org <omec...@opennetworking.org> On Behalf Of Namrata Ghodeswar
Sent: Monday, February 8, 2021 6:44 PM
To: OMEC Developers <omec...@opennetworking.org>
Cc: Namrata Ghodeswar <namrata....@gmail.com>
Subject: Re: Runtime issue in Nucleus MME

[**EXTERNAL EMAIL**]

--
You received this message because you are subscribed to the Google Groups "OMEC Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omec-dev+u...@opennetworking.org.
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/omec-dev/bfede91e-dbb9-4cfa-b92d-6ed41ad87f75n%40opennetworking.org.

Namrata Ghodeswar

unread,

Feb 9, 2021, 6:30:43 AM2/9/21

to OMEC Developers, Anjana Sreekumar, Namrata Ghodeswar

mme-app running successfully, now getting error in s1ap-app

Start MME application

Program name set to ./bin/mme-app

Server listening on 0.0.0.0:50051

Program name set to ./bin/s1ap-app

Path: Sig value: 11

Caught SIGSEGV: Segmentation Fault

trace size: 11

sh: 1: addr2line: not found

messages: ./lib/libmonitor_config.so(posix_print_stack_trace+0x19) [0x7fe99b681899] error determining line # for: ./lib/libmonitor_config.so(posix_print_stack_trace+0x19) [0x7fe99b681899]

sh: 1: addr2line: not found

error determining line # for: ./lib/libmonitor_config.so(posix_signal_handler+0x67) [0x7fe99b6819b7]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980) [0x7fe99c4b9980]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libc.so.6(+0x18e507) [0x7fe99b41d507]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x2143) [0x7fe99b2ec5d3]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libc.so.6(__printf_chk+0x11c) [0x7fe99b3c117c]

sh: 1: addr2line: not found

error determining line # for: ./lib/libjson.so(get_string_scalar+0x1d) [0x7fe99b886ded]

sh: 1: addr2line: not found

error determining line # for: ./bin/s1ap-app() [0x403167]

sh: 1: addr2line: not found

error determining line # for: ./bin/s1ap-app() [0x402067]

sh: 1: addr2line: not found

error determining line # for: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fe99b2b0bf7]

sh: 1: addr2line: not found

error determining line # for: ./bin/s1ap-app() [0x40221a]

Caught SIGSEGV: Segmentation Fault

sh: 1: addr2line: not found

root@09f77a5f459c:/openmme/target# Caught SIGSEGV: Segmentation Fault

sh: 1: addr2line: not found

Namrata Ghodeswar

unread,

Feb 10, 2021, 4:56:56 AM2/10/21

to OMEC Developers, Namrata Ghodeswar, Anjana Sreekumar

Steps to run Nucleus mme:

1. sudo make docker-build

2. sudo docker images

3. sudo docker run -it <nucleus image id>

4. ./run.sh

Do we need to run any other command apart from this?

Namrata Ghodeswar

unread,

Feb 10, 2021, 6:52:24 AM2/10/21

to OMEC Developers, Namrata Ghodeswar, Anjana Sreekumar

Configuration of ubuntu machine on which we are trying to run Nucleus MME:

Distributor ID: Ubuntu

Description: Ubuntu 18.04.5 LTS

Release: 18.04

Do we need multiple virtual machines to run mme?

Is there any hardware requirement to run mme?

Reply all

Reply to author

Forward