On one of the developer's RAD 7.5.5.1 box, WTE 7.0.0.21 admin console thows 404 when accessed.
http://localhost:admin_port/ibm/console is the standard URL.
*[11/6/12 12:53:57:159 CST] 00000012 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /ibm/console/login.do has not been defined.*
This is the error message what it shows in the SystemOut.log.
AdminConsole is a systemApp that comes with the installation. There few commands using which one can remove the console and reinstall the app and even restore the app.
Solution :
1. Remove the AdminConsole application
2. Re install the AdminConsole application
1. Remove the AdminConsole -
Goto that profile\bin in which the problem is occurring,
start the server process in that profile.
Issue the following command from command line, with administrative privileges when running on windows
wsadmin -f deployConfig.py remove
This command removes the Adminconfig app.
Restart the server
2. Re install the AdminConsole application
Make sure the server is up and running,
Goto that profile where the issue is occurring,
issue the following command from command line, with administrative privileges when running on windows
wsadmin -f deployConfig.py install
This command installs the AdminConsole.
After successful exit from the command, bounce the server process.
Access the AdminConsole. It worked for me.
InfoCenter URL for the above quoted commands -
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tcon_startstop.html
Showing posts with label InfoCenter. Show all posts
Showing posts with label InfoCenter. Show all posts
11/7/12
1/20/11
Proxy Error Bad Gateway
- InfoCenter is down.
- 502 Bad Gateway
- The server was acting as a gateway or proxy and received an invalid response from the upstream server.[2]
- 503 Service Unavailable
- The server is currently unavailable (because it is overloaded or down for maintenance).[2] Generally, this is a temporary state.
- 504 Gateway Timeout
- The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.[2]
1/28/10
InfoCenter 6.1
Today, InfoCenter URL is spitting with this message
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /infocenter/wasinfo/v6r1/advanced/searchView.jsp.
Reason: Error reading from remote server
IBM_HTTP_Server/6.0.2.13 Apache/2.0.47 (Unix) Server at publib.boulder.ibm.com Port 80
According to IBM Technote http://www-01.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&dc=DB560&dc=DB520&uid=swg21316599&loc=en_US&cs=UTF-8&lang=en&rss=ct177websphere
Problem(Abstract)
A Proxy Error in IBM® HTTP Server (IHS) causes a 502 error response in the browser.
Symptom
The user sees a 502 Proxy Error in the browser that says:
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request ....
The IBM HTTP Server error log displays errors similar to:
proxy: Error reading from remote server returned by ....
Cause
The most common cause of this problem is when the back-end web server is either not using KeepAlive, or is using too low of a value for KeepAlive.
Environment
IBM HTTP Server is configured as a proxy or reverseproxy in front of some other back-end web server.
Resolving the problem
There are two possible solutions to this problem:
1) Disable KeepAlive in IBM HTTP Server, by adding these directives into your IBM HTTP Server config (httpd.conf):
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
OR
2) Increase the KeepAlive value in the back-end web server. The KeepAlive value for the back-end web server should be at least double or triple whatever IBM HTTP Server is using for KeepAlive. The default KeepAlive for IBM HTTP Server is 15 seconds. So the back-end web server should be configured to use KeepAlive of 30 or 45 seconds.
-------------------------------------
Here the question is, who is going set those values on the IBM remote servers? :):)
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /infocenter/wasinfo/v6r1/advanced/searchView.jsp.
Reason: Error reading from remote server
IBM_HTTP_Server/6.0.2.13 Apache/2.0.47 (Unix) Server at publib.boulder.ibm.com Port 80
According to IBM Technote http://www-01.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&dc=DB560&dc=DB520&uid=swg21316599&loc=en_US&cs=UTF-8&lang=en&rss=ct177websphere
Problem(Abstract)
A Proxy Error in IBM® HTTP Server (IHS) causes a 502 error response in the browser.
Symptom
The user sees a 502 Proxy Error in the browser that says:
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request ....
The IBM HTTP Server error log displays errors similar to:
proxy: Error reading from remote server returned by ....
Cause
The most common cause of this problem is when the back-end web server is either not using KeepAlive, or is using too low of a value for KeepAlive.
Environment
IBM HTTP Server is configured as a proxy or reverseproxy in front of some other back-end web server.
Resolving the problem
There are two possible solutions to this problem:
1) Disable KeepAlive in IBM HTTP Server, by adding these directives into your IBM HTTP Server config (httpd.conf):
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
OR
2) Increase the KeepAlive value in the back-end web server. The KeepAlive value for the back-end web server should be at least double or triple whatever IBM HTTP Server is using for KeepAlive. The default KeepAlive for IBM HTTP Server is 15 seconds. So the back-end web server should be configured to use KeepAlive of 30 or 45 seconds.
-------------------------------------
Here the question is, who is going set those values on the IBM remote servers? :):)
Subscribe to:
Posts (Atom)
