No problem, the time zone difference helps here :-).
>
> How can i upgrade to the new version ?
Given the output of unbound -V you provided, you seem to be using a
Linux based system. You might get an update from your provider. If
that fails, you can compile your own version.
/usr/local/etc/unbound/var/log/unbound: No such file or directory
[1634376986] unbound-checkconf[50224:0] fatal error: logfile directory does not exist
> 2. Unbound-checkconf
> # unbound-checkconf /etc/unbound/unbound.conf
> /usr/local/etc/unbound/var/log/unbound: No such file or directory
> [1634376986] unbound-checkconf[50224:0] fatal error: logfile directory does
> not exist
>
> But still can not start unbound with RPZ.
You aparently changed stuff you don't tell about. I cann not help you this way.
Log errors
Oct 16 10:29:56 ip-172-32-10-82 systemd[1]: Stopped Unbound DNS server.
Oct 16 10:29:56 ip-172-32-10-82 systemd[1]: Starting Unbound DNS server…
Oct 16 10:29:57 ip-172-32-10-82 package-helper[50489]: /var/lib/unbound/root.key has content
Oct 16 10:29:57 ip-172-32-10-82 package-helper[50489]: success: the anchor is ok
Oct 16 10:29:57 ip-172-32-10-82 unbound[50490]: /etc/unbound/unbound.conf:36: error: unknown keyword ‘rpz’
Oct 16 10:29:57 ip-172-32-10-82 unbound[50490]: /etc/unbound/unbound.conf:36: error: stray ‘:’
Oct 16 10:29:57 ip-172-32-10-82 unbound[50490]: /etc/unbound/unbound.conf:37: error: syntax error
Oct 16 10:29:57 ip-172-32-10-82 unbound[50490]: read /etc/unbound/unbound.conf failed: 3 errors in configuration file
Oct 16 10:29:57 ip-172-32-10-82 unbound[50490]: [1634380197] unbound[50490:0] fatal error: Could not read config file: /etc/unbound/unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf
Oct 16 10:29:57 ip-172-32-10-82 systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 10:29:57 ip-172-32-10-82 systemd[1]: unbound.service: Failed with result ‘exit-code’.
Oct 16 10:29:57 ip-172-32-10-82 systemd[1]: Failed to start Unbound DNS server.
I have the feeling that you may have installed your updated unbound in /usr/local, but you still have your distribution's (old) version installed in /usr/, and perhaps your systemd unbound.service references the older version.
How did you install the updated unbound exactly?
Could you run "systemctl cat unbound" (as root), and post the output here?