Hi rafael,

See as below. (Referred from 
https://open5gs.org/open5gs/docs/guide/04-troubleshooting/)

Thanks!


You can modify the configuration file to record more logs.

diff -u /etc/open5gs/mme.yaml.old /etc/open5gs/mme.yaml
--- mme.yaml.old	2018-04-15 18:28:31.000000000 +0900
+++ mme.yaml	2018-04-15 19:53:10.000000000 +0900
@@ -2,6 +2,7 @@

 logger:
     file: /var/log/open5gs/mme.log
+    level: debug

 parameter:

After changing conf files, please restart Open5GS daemons.

$ sudo systemctl restart open5gs-mmed
$ sudo systemctl restart open5gs-sgwd



2020년 2월 29일 (토) 오전 2:53, Rafael Diniz <rafael@rhizomatica.org>님이 작성:
Thanks Spencer!

I'm willing if I should use the "-e", "-m", "-d" and "-t" in the systemd
open5gs-* service files for a more verbose output.

juba

On 2/28/20 1:40 PM, Spencer Sevilla wrote:
> Hi Juba!
>
> If open5gs is running as a systemd service (the default if you installed with apt-get) you should use journalctl. The relevant systemd service names are open5gs-hssd, open5gs-mmed, open5gs-sgwd, open5gs-pgwd, and open5gs-pcrfd. If you built them from source, they will output all information in the terminal window you’re running them in, and will also write to log files located in {installation_directory}/var/log/open5gs/.
>
> To see all the journalctl logs in one terminal: “sudo journalctl -f -u open5gs-hssd -u open5gs-mmed -u open5gs-pgwd -u open5gs-sgwd -u open5gs-pcrfd"
>
>> On Feb 28, 2020, at 06:58, Rafael Diniz <rafael@rhizomatica.org> wrote:
>>
>> Hi all,
>>
>> Which cmd line should I use to get all the debug information possible
>> from the EPC components?
>>
>> Thanks,
>> Rafael Diniz
>>
>>