"Also, /scripts/upcp --force will resolve this issue, the problem was due to a file on our update servers that was corrupted."
Funny - that is the script that broke my fully functional tomcat....
I just opened a ticket ion the meantime. I got to say - it does not make sense to just run a script again and hope it fixes what it just broke. Can you explain that one Kenneth (I'm not trying to be a jerk - just curious).
About /scripts/upcp --force:
This forces cPanel update to essentially do a reinstall of all cPanel software and files (retaining your settings however). It is useful when the update process determines something on the server is already up-to-date and thus skips it during the update process.
--force causes the updater to ignore that check and update anyway.
The easiest solution with a corrupt web.xml file[1] is to replace it with a fresh copy from the the tomcat tarball distributed at
http://tomcat.apache.org Some people dislike doing that, meddling on the commandline and so forth. Thus the instruction to execute
/scripts/upcp --force[2] to force a download of the correct web.xml file.
[1] Easy way to determine your web.xml file is corrupt:
Code:
grep httpservlet /usr/local/jakarta/tomcat/conf/web.xml
<servlet-name>httpservlet</servlet-name>
<servlet-name>httpservlets</servlet-name>
<servlet-name>httpservlet</servlet-name>
<servlet-name>httpservlets</servlet-name>
If there are more than those entries, the web.xml file is corrupted.
[2] We have since added a way to do this via WHM, since so many dislike the command line. Simply tick the box labeled
Force a reinstall even if the system is update to date on the Upgrade to Latest Version page (/scripts2/upcpform)
