Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic test Failed after installation #13

Closed
manoj1919 opened this issue Jan 21, 2021 · 5 comments
Closed

Basic test Failed after installation #13

manoj1919 opened this issue Jan 21, 2021 · 5 comments

Comments

@manoj1919
Copy link

Hi,
I tried the earlier version of my5GRANtester a month ago and it used to work fine. Today I tried installing it in another computer and noticed there is an update to the code. However I am getting th efollowing error after installation, when I try running
./app ue

my5grantester.zip

manoj20@manoj20-Macmini:~/my5G-RANTester/cmd$ ./app ue
INFO[0000] my5G-RANTester version 0.1
INFO[0000] ---------------------------------------
INFO[0000] [TESTER] Starting test function: Testing an ue attached with configuration
INFO[0000] [TESTER][UE] Number of UEs: 1
INFO[0000] [TESTER][GNB] Control interface IP/Port: 127.0.0.1/9487
INFO[0000] [TESTER][GNB] Data interface IP/Port: 127.0.0.1/2152
INFO[0000] [TESTER][AMF] AMF IP/Port: 127.0.0.1/38412
INFO[0000] ---------------------------------------
INFO[0000] [GNB] SCTP/NGAP service is running
INFO[0000] [GNB] UNIX/NAS service is running
INFO[0000] [GNB][SCTP] Receive message in %d stream
0
panic: runtime error: invalid memory address or nil pointer dereference
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x6c5806]

goroutine 11 [running]:
my5G-RANTester/internal/control_test_engine/gnb/nas/service.gnbListen.func1(0x0, 0x0, 0xc000073a00)
/home/manoj20/my5G-RANTester/internal/control_test_engine/gnb/nas/service/service.go:43 +0x26
panic(0x87a040, 0xd50260)
/usr/local/go/src/runtime/panic.go:969 +0x166
my5G-RANTester/internal/control_test_engine/gnb/nas/service.gnbListen(0xc000073a00)
/home/manoj20/my5G-RANTester/internal/control_test_engine/gnb/nas/service/service.go:51 +0xeb
created by my5G-RANTester/internal/control_test_engine/gnb/nas/service.InitServer
/home/manoj20/my5G-RANTester/internal/control_test_engine/gnb/nas/service/service.go:33 +0x1d

@baleeiro17
Copy link
Collaborator

baleeiro17 commented Jan 21, 2021

Hi, thank you for your interest in project.
Please can you check the next steps:
1- Verify in /tmp in your host if contains a file with name gnb.sock. If yes delete this file and test again ./app ue.
2- If first step is not solved your problem. Please verify wiki(using containers) and testing with containers(environment more predictable)

@manoj1919
Copy link
Author

Hi,
Thank you for the response,
when I use docker version, i get the following error
g4u18@g4u18:~/my5G-RANTester-docker$ sudo docker-compose up -d
[sudo] password for g4u18:
[29799] Error loading Python lib '/tmp/_MEIu65ZIA/libpython3.9.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/_MEIu65ZIA/libpython3.9.so.1.0)
Thank you,
Manoj

@baleeiro17
Copy link
Collaborator

Hi,
Have you seen this topic docker/compose#8064? It seems to me that the problem is with your docker-compose.

@manoj1919
Copy link
Author

Hi,
Thank you for the response,
when I use docker version, i get the following error
g4u18@g4u18:~/my5G-RANTester-docker$ sudo docker-compose up -d
[sudo] password for g4u18:
[29799] Error loading Python lib '/tmp/_MEIu65ZIA/libpython3.9.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/_MEIu65ZIA/libpython3.9.so.1.0)
Thank you,
Manoj

@baleeiro17
Copy link
Collaborator

baleeiro17 commented Jan 25, 2021

Have you tried this ?

curl -L https://get.daocloud.io/docker/compose/releases/download/1.27.4/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

for more information check docker/compose#8064. The problem is in docker-compose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants