Increasing debug logging of Lora Server
- This topic has 1 reply, 2 voices, and was last updated 10 years, 2 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You cannot reply to this topic.
Home › Forums › Conduit: AEP Model › Increasing debug logging of Lora Server
Hey all,
Trying to no avail to increase logging of the LoRa network server.
As per doc on this site, trying to increase log level from 30 (info) to 60 (Trace) in
/var/config/lora/lora-network-server.conf
by changing
"log": {"syslog": true, "path": "", "console": true, "level": 30}
to
"log": {"syslog": true, "path": "", "console": true, "level": 60}
however, on each restart the config file resets.
I had a look at
/etc/init.d/lora-network-server
and while I see a lot of the settings on AEP are comming from AEP API, I can’t seem to find anything that indicates it would overwrite the .conf file.
If anyone has a suggestion, please let me know!
Thanks,
Chris
PS: Is it typical for the lora-network-server to be logged to /var/log/messages instead of to /var/log/lora-network-server as per pretty much all other reference material on this site…?
Hey Chris,
Yes, on the AEP model, most config files are generated from the API. You can easily increase lora logging level on AEP from the UI on the bottom of the Lora configuration page.
-Brandon