Camunda v7.8.0 Tomcat Server Running on CentOs

I have an issue getting Camunda with Tomcat running on CentOs. Running the start-camunda.sh yields the errors:
image

This is a really import issue. I’ve been testing this locally on Windows 7. Our production environment is a Linux CentOs machine. Any help with this issue would be most appreciated .

You don’t have to use start-camunda.sh. As a replacement, run ${TOMCAT_HOME}/bin/cataline.sh run to start Tomcat. start-camunda.sh opens the default browser on top of that and I guess that you do not need an automated step for that.

Cheers,
Thorben

Ok cool, I’ll give that a shot and get back to you with the results. Thank you!

Running the catalina.sh script I get this error:
image

Looks like its complaining about the literals used, but I am not sure how to address this. Any Ideas?

To which shell is sh actually linked on your system? Doesn’t look like bash or?

Running “which sh” gives me /bin/sh. I’m not very Linux savvy but that seems correct. Would be different on other Linux distros? I’m running on Centos, not sure if that would make a difference.

What is the result of ls -l $(which sh) or sh --version?

This is what I get below:
image

Okay that is bash. :slight_smile:

So my next question would be how you got the camunda files on the server. As you mentioned before that you were using Windows before, did you transfer the files from your Windows machine or did you a clean unpack of the tar file? If you transferred the files from windows the issue could be the different line endings or similar. What is the output of the command file catalina.sh? If it contains something like with CRLF line terminators then I would guess that this is the problem. If that is the case please try to unpack the camunda-bpm-tomcat-7.8.0.tar.gz again on the linux server and not windows. Or use a tool like dos2unix to convert the file to unix line endings, the tool is part of the unix2dos package on CentOS if I remember correctly.

Hey Good morning!

This is what I found yesterday, turns out when I copied the files over from Windows to the Linux this was in fact the issue. To fix this I opened the catalina.sh file with “vi” and ran :set fileformat=unix and then saved the file and then running the script works. I appreciate you help! Thank you!

I was just going to suggest that you run dos2unix on the files. It happens all the time when a “generic” package (i.e. one that can run on multiple platforms (e.g., Linux, Windows)) is derived from a Windows server. The ^M that Windows formatted files use causes UNIX shell scripts to behave strangely.