Describe the bug
During normal operation, many entries of the following type appear in the journalctl service logs:
AmneziaVPN-service[25496]: [DEBUG] Amnezia LinuxNetworkWatcherWorker : Properties changed for interface org.freedesktop.NetworkManager.Device.Statistics
AmneziaVPN-service[25496]: [DEBUG] Amnezia LinuxNetworkWatcherWorker : Access point did not changed. Ignoring the changes
AmneziaVPN-service[25496]: [DEBUG] Amnezia LinuxNetworkWatcherWorker : Properties changed for interface org.freedesktop.NetworkManager.Device.Statistics
AmneziaVPN-service[25496]: [DEBUG] Amnezia LinuxNetworkWatcherWorker : Access point did not changed. Ignoring the changes
I have a lot of such logs:
$ journalctl -u AmneziaVPN | grep -B 1 -E 'Access point did not changed. Ignoring the changes' | wc -l
8126619
Logs are written regardless of whether the VPN is activated or not;
the service simply needs to be running.
To Reproduce
Steps to reproduce the behavior:
- Setup Amnezia
- The service needs to run for a few minutes; enabling the VPN is not required.
- See debug messages in logs
Expected behavior
This debug message holds no meaning for the average user. It could potentially
be set to TRACE level, or perhaps AmneziaVPN-service is not being built in DEBUG mode.
Log files
Screenshots
Desktop:
- OS: NixOS unstable
- Version 4.8.21.0
Server:
Additional context
Describe the bug
During normal operation, many entries of the following type appear in the
journalctlservice logs:I have a lot of such logs:
Logs are written regardless of whether the VPN is activated or not;
the service simply needs to be running.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This debug message holds no meaning for the average user. It could potentially
be set to
TRACElevel, or perhapsAmneziaVPN-serviceis not being built inDEBUGmode.Log files
Screenshots
Desktop:
Server:
Additional context