Deus

Hi, I don't know if these should be separate issues, but here's what I've observed so far with `tac_plus-ng` workers. **`tac_plus-ng` version:** `v314daf09c93ad958e51ab493df2675952a8c5a98/PCRE2/CRYPTO/ARES/CURL/SSL` I've run into a couple of issues...

Previous attempts to resolve this issue have not been successful. The problem persists. The remote side (client `5.5.5.5`) has initiated the connection closure by sending a FIN packet. Our server...

Quick update on that `CLOSE_WAIT` problem we saw on the TACACS+ server (`1.2.3.4:1049`). So, I commented out all the MAVIS stuff in the `tac_plus-ng` config, and things seem to be...

I rewrote my users into local **user {} blocks** directly within my **tac_plus-ng.cfg** and **disable the MAVIS shadow backend**. Since doing that, the original problem seems to have vanished for...

**Experiments:** 1. **Using `exec = /usr/local/lib/mavis/mavis_tacplus_shadow.pl`:** Experienced TCP hangs and reload issues. 2. **Using `exec = /etc/tacacs/mavis_auth_shadow.py`:** . **Experienced the exact same TCP hangs and reload issues.** The script language...

Hi Marc, Thanks again for your help. As requested, I've attached `strace` to one of the high-CPU `tac_plus-ng` processes (PID `3113335`, which was at 100% CPU). **`strace` Output** Command used:...

Hi Marc, Thanks for the patch for libmavis_external.c. I've applied it successfully: /event-driven-servers-master# patch -p1 < fix_mavis_external.patch patching file mavis/libmavis_external.c Unfortunately, the issue with high CPU usage persists.