Troubleshooting Tip: High memory utilization rising gradually day after day
| Description | This article describes a behavior that affects setups using RADIUS authentication with PEAP/MSCHAPv2 and that have a partially functioning Winbind configuration. |
| Scope | FortiNAC. |
| Solution | When Winbind is not working properly, for example, when one or more Domain Controllers are not reachable, DNS settings have changed, or new network security policies have been applied in the network, the setup may end up in a state where this service restarts every ~5 seconds. This causes memory usage to gradually increase, and if left unattended, it may lead to system instability.
To check if the setup is affected by this behavior, check the following log file:
fnac76 # diagnose tail -f messages Jan 21 14:55:10 fortinac daemon.err winbindd[13856]: [2026/01/21 14:55:10.628297, 0] ../../source3/winbindd/winbindd.c:1441(main)
The frequency of the service restart can also be checked with the following command:
fnac76 # diagnose tail -n 9999 messages | grep started Jan 21 14:54:26 fortinac daemon.err winbindd[10895]: winbindd version 4.19.3 started.
The configurations for Winbind can be found in the Administration UI under Network -> RADIUS-> Winbind. Check the Domain join status, in case of issues (red icon and status) try to fix them or in case the configuration is pointing to a non working Domain controller, delete the configuration completely.
Related articles: Technical Tip: MSCHAPv2 authentication, join FortiNAC in domain and checks Troubleshooting Tip: Local Winbind configuration fails to start Technical Tip: Create an additional Winbind instance for a second domain |
