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

Error in mme deamon #40

Open
Gian-Michele opened this Issue Mar 19, 2018 · 13 comments

Comments

Projects
None yet
4 participants
@Gian-Michele

Gian-Michele commented Mar 19, 2018

Launching the command systemctl status nextepc-mmed, to see the status of the EPC I received the following information:

nextepc-mmed.service - NextEPC MME Daemon
Loaded: loaded (/lib/systemd/system/nextepc-mmed.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-03-19 10:46:03 CET; 20s ago
Process: 1797 ExecStart=/usr/bin/nextepc-mmed -f /etc/nextepc/mme.conf (code=exited, status=1/FAILURE)
Main PID: 1797 (code=exited, status=1/FAILURE)

How I can have more information? Do you know the typical reason of this problem

BR
Gian Michele

@acetcom

This comment has been minimized.

Show comment
Hide comment
@acetcom

acetcom Mar 19, 2018

Owner

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!

Owner

acetcom commented Mar 19, 2018

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!

@Gian-Michele

This comment has been minimized.

Show comment
Hide comment
@Gian-Michele

Gian-Michele Mar 19, 2018

/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

Gian-Michele commented Mar 19, 2018

/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

@acetcom

This comment has been minimized.

Show comment
Hide comment
@acetcom

acetcom Mar 19, 2018

Owner

On your shell, please just execute the following command.

/usr/bin/nextepc-mmed -f /etc/nextepc/mme.conf

What's the result?

Owner

acetcom commented Mar 19, 2018

On your shell, please just execute the following command.

/usr/bin/nextepc-mmed -f /etc/nextepc/mme.conf

What's the result?

@Gian-Michele

This comment has been minimized.

Show comment
Hide comment
@Gian-Michele

Gian-Michele Mar 19, 2018

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)

Gian-Michele commented Mar 19, 2018

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)

@acetcom

This comment has been minimized.

Show comment
Hide comment
@acetcom

acetcom Mar 19, 2018

Owner

Your configuration file has some problem.
Please, copy the attached mme.conf to the /etc/nextepc/mme.conf

mme.conf.tar.gz

If you have still problem, could you upload your configuration file?

Thanks!

Owner

acetcom commented Mar 19, 2018

Your configuration file has some problem.
Please, copy the attached mme.conf to the /etc/nextepc/mme.conf

mme.conf.tar.gz

If you have still problem, could you upload your configuration file?

Thanks!

@Gian-Michele

This comment has been minimized.

Show comment
Hide comment
@Gian-Michele

Gian-Michele Mar 19, 2018

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

Gian-Michele commented Mar 19, 2018

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

@Gian-Michele

This comment has been minimized.

Show comment
Hide comment
@Gian-Michele

Gian-Michele Mar 19, 2018

I found my error, thanks for the support. Now it work.
Do you have some tutorial for adding an user and a apn profile??

Gian-Michele commented Mar 19, 2018

I found my error, thanks for the support. Now it work.
Do you have some tutorial for adding an user and a apn profile??

@ArthourR

This comment has been minimized.

Show comment
Hide comment
@ArthourR

ArthourR Mar 19, 2018

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

ArthourR commented Mar 19, 2018

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

@Gian-Michele

This comment has been minimized.

Show comment
Hide comment
@Gian-Michele

Gian-Michele Mar 26, 2018

Gian-Michele commented Mar 26, 2018

@Raw1mage

This comment has been minimized.

Show comment
Hide comment
@Raw1mage

Raw1mage Jul 12, 2018

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.

Raw1mage commented Jul 12, 2018

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.

@acetcom

This comment has been minimized.

Show comment
Hide comment
@acetcom

acetcom Jul 12, 2018

Owner

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.

Owner

acetcom commented Jul 12, 2018

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.

@Raw1mage

This comment has been minimized.

Show comment
Hide comment
@Raw1mage

Raw1mage Jul 16, 2018

Thanks for the tips.
My only comment is that parser should be more friendly by telling which line is wrong with a reason.

Raw1mage commented Jul 16, 2018

Thanks for the tips.
My only comment is that parser should be more friendly by telling which line is wrong with a reason.

@acetcom

This comment has been minimized.

Show comment
Hide comment
@acetcom

acetcom Jul 23, 2018

Owner

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!

Owner

acetcom commented Jul 23, 2018

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment