Redhat the invisible character of the configuration file causes Tomcat to fail to start

A recent project from Ubuntu to Redhat requires the installation of Tomcat.

After installation, it is customary to configure, modify/etc/profile and/etc/envirmonment two files. Because the content of the configuration content is more, the configuration content is directly stored in a TXT file, and then in the Redhat with Gedit through the copy paste to modify two files.

I did not expect this practice to provoke a * * * annoyance.

After the modification, run the source file name, so that the configuration to take effect, the results run catalina.sh times error, the hint can not find "/bin/setclasspath.sh This file was needed to run the".

Of course, the setclasspath.sh is still well in the proper position. That's strange, why can't you find it?

Because I did not have this problem on Ubuntu, I thought it was file permissions and so on, but none of them worked. It seems a little overkill to modify catalina.sh directly and set a fixed file name.

Later I tried overloading and did not solve the problem.

Found on the Internet, there are foreign netizens said is catalina_home environment variable error, unset catalina_home good. Sure enough, I followed suit, setclasspath.sh problem solved, but another error emerged, "Logs/catalina.out" no way to touch.

This is another strange question, but this time the system hints give me a hint that there is a "\ r" character in the path.

I suddenly understand that the original is a soft return to this character in trouble, because it is not visible, so add in Catalina_home and catalina_base behind also can not see, but the path is completely different, resulting in error.

Sure enough, after careful modification of/etc/profile, Tomcat smoothly started.

This article is from the "LTE Learning Ambassador" blog, reproduced please contact the author!

Redhat the invisible character of the configuration file causes Tomcat to fail to start