Http 500 Server Error 10 0004
Contents |
don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page.All Places > CA Security > DiscussionsLog in to create and rate content, and to follow,
Exiting With Http 500 Server Error '00-0016'
bookmark, and share content with other members.AnsweredAssumed AnsweredExiting with HTTP 500 server exiting with http 500 server error '10-0003' error '00-0001'.Question asked by sso on Mar 7, 2012Latest reply on Mar 14, 2012 by keatsk Like • Show
Hla: Missing Resource Data
0 Likes0 Comment • 3Hi, I am having issues adding multiple webagent for different websites on same Webserver. Here is senario . Two Virtual Websites abc.xyz.com (default Website) def.xyz.com Created agents abc and def added both in aco default agent as multi-value. And added webagent.conf agentname="abc,abc.xyz.com" agentname="def,def.xyz.com" When I try to access abc.xyz.com I am getting 500 Error on IE browser and I see the Errors in Log file [ERROR] Unable to resolve agent name for host “abc.xyz.com'. Exiting with HTTP 500 server error '00-0001'. If I remove Multi-value from ACO and Webagent.cof, default website abc.xyz.com works normally Environment:: Webserver: Windows 2008 IIS 7.5 Webagent :: 6.0 QMR06, Update HF-06 Thank you,SungHoon_Kim Mar 8, 2012 6:33 AMCorrect AnswerAre your 2 web instances listening on the same IP and port? In that case, you would have configured HTTP host header for each instance. As long as the host header value matches then the agent should be able to resolve. You can try renaming the agentname to FQHN to match your web instance dns name and set agent config parameter "AgentNamesAreFQHostNames=Yes" and see if that helps. If it does not, then please submit a ticket to support to investigate the issue further.See the reply in contextNo one else had this questionMark as assumed answeredOutcomesVisibility: CA Security4985 ViewsLast modified on Mar 9, 2012 8:41 PMCategories: CA Single Sign-OnThis content has been marked as final. Show 3 comments3 RepliesNameEmail AddressWebsite AddressName(Required)Email Address(Required, will not be published)Website AddressSungHoon_Kim Mar 8, 2012 6:33 AMUnmark CorrectCorrect AnswerAre your 2 web instances listening on the same IP and port? In that case, you would have configured HTTP host header for each instance. As long as
is installed) did not receive a Host header in the request from the client. Few explanations: 1. Error 500 with code [10-0004] error means that the hostname cannot be resolved. A monitoring tool that is trying to contact SiteMinder or the server. The tool will prompt 10-0004 errors because they are not connecting via HTTP 1.0 or 1.1 protocols. The 10-0004 errors can be ignored in this case. 2. Seeing bunch of 10-0004 and 10-0003 errors. A security team was running the scanner server to https://communities.ca.com/thread/97647435 check the external servers and so was generating tons of url requests for all web servers. For these web servers the siteminder agent is intercepting the requests as non HTTP1.0 complaint and gives 10-0004 errors. It does not affect any user. 3. A 10-0004 error means that the webserver did not receive a Host header in the request from the client. http://my-computing-blog.blogspot.com/2011/09/siteminder-host-header-error.html This usually occurs when you have some kind of health monitoring device that hits the webserver periodically to check if it is alive. Notice that every instance of this error likely occurs EXACTLY X seconds apart. Your company probably has some kind of monitor checking the website every X seconds. These devices often do not adhere to HTTP 1.1 spec, and so do not send down a Host header with the request. Customer has confirmed that they are running a hardware device that does health checking. There is no way to resolve this error from the SiteMinder software. This is due to the hardware device not meeting specifications. 4. F5 load balancer can verify that site is up (by getting a URL and validating page content) when the Siteminder Agent is OFF. When the agent is on, F5 cannot validate content of unprotected URI. F5 load balancers by default do not send a host header name, thus the webagent does not accept any connections that do not send this and will generate a 10-0004 in the webagent log. If you see thes
using SiteMinder error 500; http://www-01.ibm.com/support/docview.wss?uid=swg21422958 internal server error; create page; create room; siteminder Technote http://lists.jboss.org/pipermail/mod_cluster-issues/2013-March/001470.html (troubleshooting) Problem How do I avoid getting a 500 error when creating a page or a room? Cause These errors are caused by the BadURLChars value in the Agent Conf object. As an example, if Siteminder http 500 logging is enabled, you see the following log entry: [5944/8232][Wed Mar 03 2010 11:11:22][SmAgentCore.cpp:5850][ERROR] Bad characters in URL '/../../h_15E504A2BEB4364D8525767900754513/6A011068987724718525767900753BEF/?OpenDocument&Form=h_PageUI&StartAtLastPage'. Exiting with HTTP 500 server error: 00-0002. Resolving the problem To resolve the problem, the adminstrator for SiteMinder needs to update the Agent Conf object's BadUrlChars value http 500 server to remove slash period ("/.") and period slash ("./") from the list. This removal is necessary due to the way Lotus Quickr generates relative URLs after page and room creation. The default BadUrlChars value is as follows: //,./,/.,/*,*.,~,\,%00-%1f,%7f-%ff,%25 Changing the value to the following and restarting HTTP resolves the problem: //,/*,*.,~,\,%00-%1f,%7f-%ff,%25 Note: It is not enough to simply adjust the WebAgent.conf file, because the SiteMinder administrator might have disabled local updates. It is best to adjust the server side object. Document information More support for: Lotus End of Support Products Lotus Quickr for Domino Software version: 8.0, 8.1, 8.2 Operating system(s): Windows Reference #: 1422958 Modified date: 2013-03-06 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
JIRA] (MODCLUSTER-306) Backport MODCLUSTER-201 to 1.0.10.GA - update mod_cluster to use HTTP/1.1 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ https://issues.jboss.org/browse/MODCLUSTER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Ogburn reopened MODCLUSTER-306: ------------------------------------- I had a customer using this backported fix through the JBPAPP-9571 patch. They use this along with Siteminder and see STATUS MCMP requests were randomly failing/500ing without any real reason. Come to find out that any failed STATUS is missing the Host header and so siteminder fails it: {noformat} 10.170.104.52 - - [06/Mar/2013:12:44:52 -0800] "STATUS / HTTP/1.1" 500 535 "-" "ClusterListener/1.0" 0 375 10.170.104.52 - - [06/Mar/2013:12:44:52 -0800] "STATUS / HTTP/1.1" 500 535 "-" "ClusterListener/1.0" 0 343 10.170.104.52 - - [06/Mar/2013:12:44:56 -0800] "STATUS / HTTP/1.1" 500 535 "-" "ClusterListener/1.0" 0 468 10.170.104.51 - - [06/Mar/2013:12:45:01 -0800] "INFO / HTTP/1.1" 200 5088 "-" "ClusterListener/1.0" 0 848 ina-internal-ch-prd-web1.uboc.com:8466 10.170.104.51 - - [06/Mar/2013:12:45:01 -0800] "INFO / HTTP/1.1" 200 5088 "-" "ClusterListener/1.0" 0 757 ina-internal-ch-prd-web1.uboc.com:8466 10.170.104.51 - - [06/Mar/2013:12:45:01 -0800] "CONFIG / HTTP/1.1" 200 - "-" "ClusterListener/1.0" 0 574 ina-internal-ch-prd-web1.uboc.com:8466 [CSmHttpPlugin.cpp:278][ERROR] Unable to resolve server host name. Exiting with HTTP 500 server error '10-0004'. {noformat} Here's DefaultMCMPHandler.sendRequest from the 1.0.10.GA_CP branch currently: {code:title=DefaultMCMPHandler.java|borderStyle=solid} String head = builder.toString(); int length = encoder.getLength(); char[] body = encoder.getBuffer(); // Require exclusive access to proxy socket synchronized (proxy) { try { String line = null; StringBuilder proxyheadBuilder = new StringBuilder(head); proxyheadBuilder.append(proxy.getAddress().getHostName() + ":" + proxy.getPort()); String proxyhead = proxyheadBuilder.toString(); try { line = sendRequest(proxy, proxyhead, body, length); } catch (IOException e) { // Ignore first write failure } if (line == null) { // Retry failed read/write with fresh connection proxy.closeConnection(); line = sendRequest(proxy, head, body, length); } {code} So it looks like they occasionally use that second sendRequest, which wasn't updated to use the proxyHead string that was built with the info for the Host header. I ca