-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSS Check Failure #337
Comments
Sorry for the delay, I missed this originally. This check is provided directly by 389-ds and executed by freeipa-healthcheck. I'm not completely sure what it is doing. You can try increasing the timeout to see if the check itself will fail with a better reason. Create /etc/ipahealthcheck/ipahealthcheck.conf with contents: [default] |
This is quite interesting. I actually had a few errors that were all "resolved" by increasing this timeout. I have two FREEIPA Servers running AlmaLinux 9.5 (Teal Serval) on Raspberry Pi 4 Model B Rev 1.5. Server are connected on the same 1G switch/LAN so traffic between them should be very fast. Happy its reporting "more healthy" but wondering why the timeout would play such a big role here? Thoughts would be appreciated. (I am working on the remaining CA issue still) You can see here - before:
After:
|
I cannot seem to figure out why this health check keeps failing.
{
"source": "ipahealthcheck.ds.nss_ssl",
"check": "NssCheck",
"result": "ERROR",
"uuid": "18e1cb64-ca7f-4247-8fdb-a11fdd87b217",
"when": "20240919194444Z",
"duration": "10.003445",
"kw": {
"exception": "Request timed out"
}
},
Server: Almalinux
The text was updated successfully, but these errors were encountered: