[SOLVED]why in openwrt all the syslog messages are put in daemon.err category?

[rezad1393]

In openwrt apps write their messages to syslog.

Most app use correct categorization for different kind of messages:
fatal,error,warn,notice,debug and so on.

But it seems that dnscrypt-proxy daemon uses error category (daemon.err) for everything and then puts the text [NOTICE] and [ERROR] and the start of messages.

like this:

Wed Feb 21 06:50:32 2024 daemon.err dnscrypt-proxy[507]: [2024-02-21 06:50:32] [NOTICE] Firefox workaround initialized
Wed Feb 21 06:50:32 2024 daemon.err dnscrypt-proxy[507]: [2024-02-21 06:50:32] [ERROR] Get "https://dns.google/dns-query?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABChWRjkGcv7ERDvlbOkfdoH": dial tcp 8.8.8.8:443: connect: network is unreachable

this messes with log reading software.

can this be fixed?

[welwood08]

I'm not familiar with OpenWrt's packaging, but it appears as though the current package is not telling dnscrypt-proxy to use syslog which causes it to default to output to stderr (see here) and then captures that for logging... On cursory inspection I think adding -syslog to here should probably tell dnscrypt-proxy to output directly to syslog instead, but I'm just guessing. Also, there is an appropriate repository to report issues with the OpenWrt package - we aren't responsible for that here.

[rezad1393]

thank you for the fast answer.

I forget to say that I use the arm version pacakged binary here on github and put it on usb for openwrt to user.
so technically I am not using the openwrt packaged version (it is too big for router built-in nand flash).

your hint helped and I found the option in toml for it to use:
use_syslog = true