sgslufread：读取时出现硬错误，操作系统错误 = 104 Linux
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/10634973/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
sgslufread: Hard error on read, OS error = 104 Linux
提问by missingsemicolon
I'm getting an issue in LINUX when I do
我在 LINUX 中遇到问题
ldapsearch -p 6567 "iispsid=BBEU68843256" iispoffername
ldapsearch -p 6567 "iispsid=BBEU68843256" iispoffername
Its giving error
它给出的错误
sgslufread: Hard error on read, OS error = 104 ldap_bind: Can't contact LDAP server
sgslufread：读取时出现硬错误，操作系统错误 = 104 ldap_bind：无法联系 LDAP 服务器
The same works well in UNIX. What does this hard error mean?
这同样适用于 UNIX。这个硬错误是什么意思？
回答by Rajalaxmi K
Oracle Internet Directory (OID) ldapbind gives: sgslufread: Hard error on read, OS error = 10054 We were using a Cisco Load Balancing Router (LBR or CSS) and trying to do a simple ldapbind -p 389 -h machine would give the following error: sgslufread: Hard error on read, OS error = 10054 (on windows) sgslufread: Hard error on read, OS error = 104 (on linux) ldap_bind: Can't contact LDAP server
Oracle Internet Directory (OID) ldapbind 给出：sgslufread：读取时出现硬错误，OS 错误 = 10054 我们正在使用 Cisco 负载平衡路由器（LBR 或 CSS）并尝试执行简单的 ldapbind -p 389 -h 机器将给出以下结果错误：sgslufread：读取时出现硬错误，操作系统错误 = 10054（在 Windows 上） sgslufread：读取时出现硬错误，操作系统错误 = 104（在 linux 上）ldap_bind：无法联系 LDAP 服务器
(might have also seen sgslufread: Hard error on read, OS error = 194 )
（可能还看过 sgslufread: Hard error on read, OS error = 194 ）
It turned out that the LBR was configured with Layer 5 load balancing (it does URL inspection). It is turned on by adding url "/" to the content content layer5 protocol tcp vip address xxx.xxx.xxx.xxx add service server1 port 389 url "/" active
结果证明 LBR 配置了第 5 层负载平衡（它进行 URL 检查）。通过在内容内容layer5协议tcp vip地址xxx.xxx.xxx.xxx add service server1 port 389 url "/" active中加入url"/ "开启
The problem is that we have LDAP traffic, not HTTP traffic. Layer5 (url "/") is for HTTP traffic. Removing the url "/" took care of the issue.
问题是我们有 LDAP 流量，而不是 HTTP 流量。第 5 层（网址“/ ”）用于 HTTP 流量。删除网址“/”解决了这个问题。
I also received the same error when using an F5 load balancer to connect via LDAPS (SSL encrypted) on port 636. In this case the solution was to turn off the F5 LDAP monitor for port 636. For some reason the F5 does not like to monitor the OID SSL LDAP port.
在使用 F5 负载平衡器通过端口 636 上的 LDAPS（SSL 加密）进行连接时，我也收到了同样的错误。在这种情况下，解决方案是关闭端口 636 的 F5 LDAP 监视器。出于某种原因，F5 不喜欢监视 OID SSL LDAP 端口。
