Unbound log doesn't update after upgrade to 20.7

[hushcoden]

As per title, the last entry in the unbound log is yesterday at the time I upgraded to 20.7 and nothing since then, how come ??

Tia.

[mimugmail]

Can you also check other logs? Any entries?
Did you switch to text based logging?

[hushcoden]

Can you also check other logs? Any entries?

So, the following logs are not updated as last entries are back to August 1 at 18:33 when I updated to 20.7

   - System: Log Files: Backend
   - System: Log Files: Web GUI
   - Firewall: Log Files: Live View
   - Firewall: Log Files: Plain View
   - Services: DHCPv4: Log File
   - Services: Network Time: Log File
   - Services: Unbound DNS: Log File

and the only up-to-date log is
 
   - System: Log Files: General

Did you switch to text based logging?

Sorry, I don't what it means... 

And checking the dashboard, I see that both syslog-ng and syslogd are currently running.

[mimugmail]

Can you restart syslog a couple of times or maybe restart OPN again?

[hushcoden]

Done, restarted once again OPN but no luck... I feel I will have to install 20.7 from scratch... 

[mimugmail]

Can you take a video from boot up process when connecting monitor and look for a syslog crash?

[CJ]

I'm seeing the same issues but not with all of the same log files.

These work.

   - System: Log Files: Backend
   - System: Log Files: Web GUI
   - Firewall: Log Files: Live View
   - Firewall: Log Files: Plain View
   - Services: DHCPv4: Log File

These do not.

   - Services: Network Time: Log File
   - Services: Unbound DNS: Log File

[mimugmail]

20.7.2 brings a fix

[CJ]

Awesome.

On a related note, are there plans to make Unbound provide the Apply Settings notice when updating the new DNS options for DoT and DNSBL?

Thanks.

[mimugmail]

No, the second Apply is for legacy pages and new style just Save

[danielm]

Try to clear logs that have many items in them, for me it helped and syslog-ng could be restarted again.
It is also prone to crashes in this version, so always if your logs seems stale, it's probably because syslog has crashed again...
Let's hope 20.7.2 comes fast as I also wasted hours on this before figuring it out - and it's quite annoying to me when configuring something new that needs debugging, but your log keeps crashing  .

[CJ]

No, the second Apply is for legacy pages and new style just Save

Ah, okay.  I didn't realize there was a shift going on.

To confirm, you're saying that when I hit save on the DNSBL page it will automatically restart Unbound?

Sorry for the derailment and thanks.

[mimugmail]

Yes, but sometimes it needs 2 or 3, but I have mit yet found the reason

[CJ]

Yes, but sometimes it needs 2 or 3, but I have mit yet found the reason

Interesting.  Not sure if I've seen that.  However, my Unbound log started working recently.  I'm not sure why.  I'm still on 20.7.1

[patcsy88]

I am facing the same issue where Unbound is NOT logging via syslog-ng. I am on 20.7.3 on a PCEngine kit. On a similar system with 20.7.3 i5 Qotom, that is working correctly. I have checked the settings and they are near identical. Any insights would be most helpful please...