Comments (21)
Thanks for the tips.
My only comment is that parser should be more friendly by telling which line is wrong with a reason.
from open5gs.
Could you send a log & conf file?
The location is as below.
Log file : /var/log/nextepc/mme.log
Conf file : /etc/nextepc/mme.conf
Thanks!
from open5gs.
/etc/nextepc/mme.conf:
logger:
file: /var/log/nextepc/mme.log
trace:
app: 1
s1ap: 1
nas: 1
diameter: 1
gtpv2: 1
parameter:
mme:
freeDiameter: mme.conf
s1ap:
addr: 163.162.89.33
gtpc:
gummei:
plmn_id:
mcc: 001
mnc: 01
mme_gid: 2
mme_code: 1
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 1
security:
integrity_order : [ EIA1, EIA2, EIA0 ]
ciphering_order : [ EEA0, EEA1, EEA2 ]
network_name:
full: NextEPC
sgw:
gtpc:
addr: 127.0.0.2
pgw:
gtpc:
addr:
- 127.0.0.3
- ::1
in the /var/log/nextepc/mme.log i cannot seen any log information
from open5gs.
On your shell, please just execute the following command.
/usr/bin/nextepc-mmed -f /etc/nextepc/mme.conf
What's the result?
from open5gs.
the result after running the command is:
[03/19 14:36:22.014] WARN: pid file /var/run/nextepc-mmed/pid overwritten -- Unclean shutdown of previous NextEPC run? (init.c:112)
PID[2503] : '/var/run/nextepc-mmed/pid'
[03/19 14:36:22.015] FATL: Failed to parse configuration file '/etc/nextepc/mme.conf' (context.c:70)
[03/19 14:36:22.015] FATL: NextEPC initialization failed. Aborted (main.c:152)
from open5gs.
Your configuration file has some problem.
Please, copy the attached mme.conf
to the /etc/nextepc/mme.conf
If you have still problem, could you upload your configuration file?
Thanks!
from open5gs.
Now in the in the /var/log/nextepc/mme.log i found the following lines:
[03/19 15:22:37.906] MME try to initialize
[03/19 15:22:38.059] ERRR: Unrecognized text on line 3 col 1: 'logger'. (fd_init.c:116)
[03/19 15:22:38.059] ERRR: mme.conf:3.1-6 : An error occurred while parsing the configuration file (fd_init.c:116)
[03/19 15:22:38.060] ERRR: ERROR: in '((fddparse(fd_g_config)))' : Invalid argument (fd_init.c:116)
[03/19 15:22:38.060] ERRR: ERROR: in '((fd_conf_parse()))' : Invalid argument (fd_init.c:116)
[03/19 15:22:38.060] ERRR: ERROR: in '(fd_core_parseconf(conffile))' : Invalid argument (fd_init.c:116)
[03/19 15:22:38.060] freeDiameter[6]: Initiating freeDiameter shutdown sequence (1)
[03/19 15:22:38.067] ASSERT: !(ret == CORE_OK). (mme_fd_path.c:1100)
[03/19 15:22:38.067] ERRR: Failed to intialize MME (mme.c:30)
[03/19 15:22:38.067] FATL: NextEPC initialization failed. Aborted (main.c:152)
[03/19 15:22:38.067] MME try to terminate
[03/19 15:22:38.067] MME terminate...done
File Logging : '/var/log/nextepc/mme.log'
Configuration : '/etc/nextepc/mme.conf'
[03/19 15:25:11.998] MME try to initialize
[03/19 15:25:12.151] ERRR: Unrecognized text on line 3 col 1: 'logger'. (fd_init.c:116)
[03/19 15:25:12.151] ERRR: mme.conf:3.1-6 : An error occurred while parsing the configuration file (fd_init.c:116)
[03/19 15:25:12.152] ERRR: ERROR: in '((fddparse(fd_g_config)))' : Invalid argument (fd_init.c:116)
[03/19 15:25:12.152] ERRR: ERROR: in '((fd_conf_parse()))' : Invalid argument (fd_init.c:116)
[03/19 15:25:12.152] ERRR: ERROR: in '(fd_core_parseconf(conffile))' : Invalid argument (fd_init.c:116)
[03/19 15:25:12.152] freeDiameter[6]: Initiating freeDiameter shutdown sequence (1)
[03/19 15:25:12.153] ASSERT: !(ret == CORE_OK). (mme_fd_path.c:1100)
[03/19 15:25:12.153] ERRR: Failed to intialize MME (mme.c:30)
[03/19 15:25:12.153] FATL: NextEPC initialization failed. Aborted (main.c:152)
[03/19 15:25:12.153] MME try to terminate
[03/19 15:25:12.153] MME terminate...done
File Logging : '/var/log/nextepc/mme.log'
Configuration : '/etc/nextepc/mme.conf'
[03/19 15:28:42.211] MME try to initialize
[03/19 15:28:42.364] ERRR: Unrecognized text on line 3 col 1: 'logger'. (fd_init.c:116)
[03/19 15:28:42.365] ERRR: mme.conf:3.1-6 : An error occurred while parsing the configuration file (fd_init.c:116)
[03/19 15:28:42.365] ERRR: ERROR: in '((fddparse(fd_g_config)))' : Invalid argument (fd_init.c:116)
[03/19 15:28:42.365] ERRR: ERROR: in '((fd_conf_parse()))' : Invalid argument (fd_init.c:116)
[03/19 15:28:42.365] ERRR: ERROR: in '(fd_core_parseconf(conffile))' : Invalid argument (fd_init.c:116)
[03/19 15:28:42.365] freeDiameter[6]: Initiating freeDiameter shutdown sequence (1)
[03/19 15:28:42.366] ASSERT: !(ret == CORE_OK). (mme_fd_path.c:1100)
[03/19 15:28:42.366] ERRR: Failed to intialize MME (mme.c:30)
[03/19 15:28:42.366] FATL: NextEPC initialization failed. Aborted (main.c:152)
[03/19 15:28:42.366] MME try to terminate
[03/19 15:28:42.367] MME terminate...done
from open5gs.
I found my error, thanks for the support. Now it work.
Do you have some tutorial for adding an user and a apn profile??
from open5gs.
If you have installed nextepc through apt-get, you should have a web interface available at http://your-epc-ip:3000/
Default user : admin / pass : 1423 . Add a subscriber there
from open5gs.
from open5gs.
This sounds crazy, but it is real.
All the parsing errors are caused by tab spaces in the config files.
Replacing tabs by white spaces solved all the config parsing errors.
from open5gs.
YAML forbids tabs. You should use space instead of tab in NextEPC configuration file.
YAML FAQ: Why does YAML forbid tabs?
Tabs have been outlawed since they are treated differently by different editors and tools. And since indentation is so critical to proper interpretation of YAML, this issue is just too tricky to even attempt. Indeed Guido van Rossum of Python has acknowledged that allowing TABs in Python source is a headache for many people and that were he to design Python again, he would forbid them.
from open5gs.
We've added a reason string when YAML parser error is occurred.
Those who have difficulty in this situation can easily see why.
Thanks for your comments!
from open5gs.
hello acetcom,
i have the same challenge as posted above
● nextepc-mmed.service - NextEPC MME Daemon
Loaded: loaded (/lib/systemd/system/nextepc-mmed.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-11-14 11:40:19 WAT; 33min ago
Process: 1655 ExecStart=/usr/bin/nextepc-mmed -f /etc/nextepc/mme.conf (code=exited, status=1/FAILURE)
Main PID: 1655 (code=exited, status=1/FAILURE)
Nov 14 11:40:19 tizeti systemd[1]: Started NextEPC MME Daemon.
Nov 14 11:40:19 tizeti nextepc-mmed[1655]: NextEPC daemon v0.3.10 - May 21 2019 18:36:28
Nov 14 11:40:19 tizeti nextepc-mmed[1655]: PID[1655] : '/var/run/nextepc-mmed/pid'
Nov 14 11:40:19 tizeti nextepc-mmed[1655]: [11/14 11:40:19.839] FATL: Failed to parse configuration file '/etc/nextepc/mme.conf' (context.c:92)
Nov 14 11:40:19 tizeti nextepc-mmed[1655]: [11/14 11:40:19.839] ERRR: Scanner error - mapping values are not allowed in this context at line 21, column 12 (context.c:11
Nov 14 11:40:19 tizeti nextepc-mmed[1655]: [11/14 11:40:19.839] FATL: NextEPC initialization failed. Aborted (main.c:172)
Nov 14 11:40:19 tizeti systemd[1]: nextepc-mmed.service: Main process exited, code=exited, status=1/FAILURE
Nov 14 11:40:19 tizeti systemd[1]: nextepc-mmed.service: Failed with result 'exit-code'.
~
Please how can i resolve this
from open5gs.
Hi @amintgan
I cannot find the above problem if you do not upload your configuration file.
Perhaps, there is a problem in your configuration file.
BTW, your version (v0.3.10) is old.
Use the latest version with the package repository at the following link:
https://open5gs.org/open5gs/docs/guide/01-quickstart/
Thanks!
from open5gs.
HI @acetcom
my eNB isnot connecting with NextEPC but got connected with aircent epc. Also, nothing was logged in the /var/log/open5gs/mme.log file. I will appreciate your assitance
here is my mme.conf file .
/etc/open5gs/mme.yaml
logger:
file: /var/log/open5gs/mme.log
parameter:
mme:
freeDiameter: /etc/freeDiameter/mme.conf
s1ap:
addr: 10.1.5.23
gtpc:
addr: 10.1.5.23
gummei:
plmn_id:20001
mcc: 200
mnc: 01
mme_gid: 2
mme_code: 1
tai:
plmn_id: 20001
mcc: 200
mnc: 01
tac: 12594
security:
integrity_order : [ EIA1, EIA2, EIA0 ]
ciphering_order : [ EEA0, EEA1, EEA2 ]
network_name:
full: Open5GS
sgw:
gtpc:
addr: 127.0.0.2
pgw:
gtpc:
addr:
- 127.0.0.3
- ::1
from open5gs.
If you just paste the content of your configuration, I cannot find your problem. Please attach your configuration file.
Thanks!
from open5gs.
mme_open5gs.txt
@acetcom please find attcahed.
thanks
from open5gs.
Your configuration file is not correct. See the below
0a1
> [1/4] /etc/open5gs/mme.yaml
13c14
< plmn_id:
---
> plmn_id:20001
19c20
< plmn_id:
---
> plmn_id: 20001
43c44
<
---
>
\ No newline at end of file
So the result is like the followings.
mme_open5gs.txt
Good luck with you!
from open5gs.
Thanks a lot @acetcom I will check the config file to see my mistakes. Although I eventual got it connected with baicells eNB with the help of @nickvsnetworking
Thank you everyone for helping a clueless girl out. You guys rock.
from open5gs.
I found my error, thanks for the support. Now it work.
Do you have some tutorial for adding an user and a apn profile??
Hi Michele
You said you found your error and fixed it, can you plz share the solution here? I'm kind of facing the same exact issue
#40 (comment)
from open5gs.
Related Issues (20)
- Could not finish setup request. Deallocating dedicatedInfoNAS PDU
- UE not getting data connection on Ericsson gNB HOT 2
- incorrect behavior of the SGsAP HOT 18
- open5gs-smfd crashes when starting
- [Bug]: open5gs-*d fails to connect
- open5gs is not compatible with standards in handover HOT 1
- [Bug]: mongoc version not checked correctly HOT 1
- [Bug]: Open5gs not working in AWS EC2 Ubuntu Jammy environment// AMF Daemon
- Install open5gs on Raspberry Pi 5
- [Bug]: SMF crashes when multiple UE attachment attempts fail due to possible memory leak HOT 2
- Crash when deleting gtpc section of smf.yaml for 5G use HOT 4
- Passwords of Private Keys
- Some metrics of Open5GS/Prometheus are not being collected HOT 2
- smf,upf, sgwu Assertion Error
- [Bug]: sgwc is crashing if the call is being answered from FreeSWITCH HOT 6
- Regarding the issue of ue connecting to the core network
- Not Internet Access Cost UE NORD CE 5G Unknown PCO ID:(0x23) (../src/smf/context.c:3011)
- [Bug]: The AMF deletes AMF_UE_NGAP_ID when receives NAS messages in an invalid state. HOT 1
- [Bug]: SMF crashes when handle malformed PDU Session Modification Request message HOT 2
- Can we use latest kamailio(git) with open5gs HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from open5gs.