This message was deleted.
# generala
adamant-kite-43734
02/13/2025, 5:03 PMThis message was deleted.
b
bland-article-62755
02/13/2025, 5:22 PMexec into the rancher pod and ran
nslookup ldapservername.domainhost ldapservername.domainbland-article-62755
02/13/2025, 5:23 PMOutside of that, it mentions ssl connection. Is the cert signed? Your config is using only the ssl port? (636)?
s
sparse-ghost-91718
02/13/2025, 5:52 PMThe cert is signed by known provider. I can't run any of those commands on rancher pod. I can run them on underlying worker nodes as I did in the troubleshooting.
Copy code
bash-4.4# dpkg
bash: dpkg: command not found
bash-4.4# nslookup
bash: nslookup: command not found
bash-4.4# host
bash: host: command not found
bash-4.4# apt
bash: apt: command not found
bash-4.4#b
bland-article-62755
02/13/2025, 5:53 PMpings
sparse-ghost-91718
02/13/2025, 5:54 PMnot available.
Copy code
bash-4.4# ping
bash: ping: command not foundb
bland-article-62755
02/13/2025, 5:56 PMit's still important to try to run from a container vs the host.
bland-article-62755
02/13/2025, 5:56 PMIt's possible the cluster doesn't have dns fallthrough or can't resolve that name, but the host can.
s
sparse-ghost-91718
02/13/2025, 5:57 PMIt may be , where to check ? This is exact issue
https://github.com/rancher/rancher/issues/44593
b
bland-article-62755
02/13/2025, 5:58 PMI don't see ``x509: certificate is valid for xxx, not yyy` in your posting
bland-article-62755
02/13/2025, 5:59 PMit's a similar error, but not the same
s
sparse-ghost-91718
02/13/2025, 7:54 PMIt's not the same , I don't get ssl error.
b
bland-article-62755
02/13/2025, 10:35 PMright, but that git issue is with the ssl error, so not that exact issue right?
s
sparse-ghost-91718
02/14/2025, 1:12 AMSorry , you're right it's not exact issue. Is there away to add debug for rancher ldap provider ?
34 Views