Unbound log file page not responding

[chtse53]

After upgrading from 22.1.10 to 22.7, the log file page of Unbound DNS was not responding.

[franco]

Can you post the output of:

# ls -lah /var/log/resolver.log


Cheers,
Franco

[chtse53]

 # ls -lah /var/log/resolver.log
ls: /var/log/resolver.log: No such file or directory

[Dantichrist]

Code Select Expand

# ls -lah /var/log/resolver.log
ls: /var/log/resolver.log: No such file or directory

I get the same output but my logs are working fine in Unbound.

Code Select Expand

2022-07-28T13:44:55-06:00 Informational unbound [61035:0] info: control cmd: local_datas
2022-07-28T13:44:54-06:00 Informational unbound [61035:0] info: control cmd: local_datas_remove
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: Verified that unsigned response is INSECURE
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: NSEC3s for the referral proved no DS.
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: resolving emergingthreats.net. DS IN
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: query response was ANSWER
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: reply from <.> XX.XX.XX.XX#853
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: response for opnsense.emergingthreats.net. A IN
2022-07-28T13:44:38-06:00 Informational unbound [61035:3] info: resolving opnsense.emergingthreats.net. A IN

[chtse53]

Thanks for the info. 

I was using MS Edge browser and got non-responding page on the "log files" tab.  I changed to Chrome browser and it worked.  It could be a browser problem or a cache problem.  I would clear the Edge browser cache and try again.

[chtse53]

Turn-out MS Edge Browser also worked after deleting the cookie for my opnsense server.  Just not sure why it affected only the "log file" of Unbound.  I can view other system log files without problem.

[franco]

Strange stuff.  :o


Cheers,
Franco