Cannot start jmeter on my linux terminal

Question

Hey, I tried to run Jmeter (Jmeter-server.bat) on my Linux terminal, but I got the command "Command not found". Jmeter is already downloaded from http://jmeter.apache.org/download_jmeter.cgi . Tried sh jmeter.sh,. / Jmeter = An error occurred: null. What can I do? By the way, I am doing all this from the lib directory. I tried sh jmeter, it says: sh: 0: cannot open jmeter

Answer 1

Ok, I got a solution. I just used the ./jmeter -n -t mytextplan.jmx command in the bin directory. I did not include "./jmeter" in non-GUI mode. It shows that I am in the current working directory.

Then i use

./jmeter -n -t TestPlanResult.jmx -l jmeteroutput.csv

to copy the results to a csv file.

It worked!

Answer 2

First, you must have Java installed to run JMeter.

Then follow these steps.

1) Goto http://apache.apache.org/site/downloads/downloads_jmeter.cgi 2) Download Binary 2.11.tgz . The tgz file name will be "apache-jmeter-2.11″ 3) Paste it in /usr/USERNAME/Jmeter 4) Unzip "apache-jmeter-2.11″ 5) New folder with name "apache-jmeter-2.11″ will be created 6) Go to command prompt 7) go to "apache-jmeter-2.11″ folder (cd /usr/USERNAME/Jmeter/apache-jmeter-2.11) 8) go to "bin" folder (cd bin) 9) Now you are in bin folder (ie /usr/USERNAME/Jmeter/apache-jmeter-2.11/bin/) 10) type the command "sh jmeter" 11) After a short pause, the JMeter GUI should appear. 

Slightly modified for you from this .

Answer 3

You just need to go to the bin folder.

 cd ../bin sh jmeter 

*. bat files are for windows only, but it makes no sense to try to run them on linux. jmeter-server is designed for remote slaves to communicate with the jmeter wizard, which is also probably not what you want at this point.

I assume that you already have a java installation and a desktop environment to run the GUI.

Answer 4

I have the same problem, in my case it was caused by removing the Java icon from the dock with an environment variable:

 export JAVA_TOOL_OPTIONS='-Djava.awt.headless=true' 

commenting on this in my ~ / .bash_profile and rewriting the terminal, fixed it for me.