Problem: Unable to start/stop webserver from Dmgr console.
Environment:
Windows XP professional sp3
WASv7.0 ND
HTTPServer6.0
Scenario : While trying to start or stop the webserver from the dmgr console exception was encountered:
"unable to start adminnode04/webserver1"
"look under nodeagent logs"
Systemout log displayed something like:
"exception thrown while starting webserver..launchprocess failed...modelmbean not found"
While playing around the console while trying to access the configuration file at:
Web servers > webserver1 > ${WEB_INSTALL_ROOT}/conf/httpd.conf
it was unable to be found.
Ultimately a more detailed analysis proved that the entire "conf" and "bin" directories were missing from the {WEB_INSTALL_ROOT} dir.
After making sure that the {WEB_INSTALL_ROOT} has these three directories:
1.Plugins
2.conf
3.bin
The problem was fixed.
Environment:
Windows XP professional sp3
WASv7.0 ND
HTTPServer6.0
Scenario : While trying to start or stop the webserver from the dmgr console exception was encountered:
"unable to start adminnode04/webserver1"
"look under nodeagent logs"
Systemout log displayed something like:
"exception thrown while starting webserver..launchprocess failed...modelmbean not found"
While playing around the console while trying to access the configuration file at:
Web servers > webserver1 > ${WEB_INSTALL_ROOT}/conf/httpd.conf
it was unable to be found.
Ultimately a more detailed analysis proved that the entire "conf" and "bin" directories were missing from the {WEB_INSTALL_ROOT} dir.
After making sure that the {WEB_INSTALL_ROOT} has these three directories:
1.Plugins
2.conf
3.bin
The problem was fixed.
No comments:
Post a Comment