Error with GtpUser on simulation multiMEC host
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- networking
Research direction
Reproduce the crash with the attached omnetpp.ini, .ned, demo.xml, and .json files, focusing on simu5g::GtpUser in MultiOperatorMultiMec.upf_A.gtp_user. Start from the reported check_and_cast() failure at about 7.1 seconds and determine why an inet::Indication is received where an inet::Packet is expected. Done means the 40-second multiMEC simulation completes without this runtime error.
Written by the indexing model from the issue text.
Description
I'm running a simulation a multiMEC scenario over a 40 s, but crush after few seconds 7-9s. The msg error show is:
A runtime error ocurred:
check_and_cast(): Cannot cast (inet::Indication*) ERROR to type 'inet::Packet*' -- in module (simu5g::GtpUser) MultiOperatorMultiMec.upf_A.gtp_user (id=217), at t=7.1020052264s, event #315291
Launch a debugger with the following command?
opp_ide omnetpp://dsp/debugger/attach?pid=55211
Attached the code file:
- omnetpp.ini
- .ned
- demo.xml
- .json
- Dominant language
- C++
- Stars
- 235
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Unipisa/Simu5G
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·