Syslog backend over LTE-M for nrf9160

[ANDRIJ GRABCZAK]

How to properly activate zephyr logs with network syslog backend to work over LTE-M for nrf9160 custom device?

[Simonr]

Are you saying this is what you're seeing too? Where are you outputting this syslog exactly on your end?

Best regards,

Simon

[ANDRIJ GRABCZAK]

I meant that the example project I showed you is compiling and I can see the logs in the shell terminal. However, I do not see logs of the Syslog type (RFC 5424) on the server specified in the configuration (169.46.82.174:25736). In the example, I use a server that is provided by service https://papertrailapp.com. However, in reality there should be a full-fledged Syslog server.

[ANDRIJ GRABCZAK]

Yes. If I download the Modem Shell (MoSh) example to my nRF9160-DK, I can ping from my operator's network and send data via a socket commands.

[Michal]

What happens if you add "tcp://" in your CONFIG_LOG_BACKEND_NET_SERVER?

[ANDRIJ GRABCZAK]

This causes an error:

[00:00:00.629,364] <inf> net_syslog_lte: Starting application...
[00:00:00.684,783] <inf> net_syslog_lte: LTE connected successfully
[00:00:00.684,814] <inf> net_syslog_lte: Begin logging to syslog...
[00:00:00.684,844] <err> log_backend_net: Cannot configure syslog server address

Normally it looks like:

[00:00:00.651,672] <inf> net_syslog_lte: Starting application...
[00:00:00.707,061] <inf> net_syslog_lte: LTE connected successfully
[00:00:00.707,092] <inf> net_syslog_lte: Begin logging to syslog...
[00:00:00.707,183] <dbg> net_utils: parse_ipv4: (main): IPv4 host 169.46.82.174 port 25736

but my log server is still empty...

[Michal]

Thank you for testing.

I'll see if we can find anything else after the weekend.

[Michal]

I will try to test it against Papertrail myself, but I will have to understand it properly first. Hoping to get some tests done before the end of the week at least.