I am able to create a dashboard folder on Local jenkins but same when I am trying to deploy on live jenkins following error I am getting.
Error generating the report: org.apache.jmeter.report.dashboard.GenerationException: Error while processing samples: Consumer failed with message :Consumer failed with message :Consumer failed with message :Consumer failed with message :Consumer failed with message :Cannot create working directory "temp/latencyVsRequest"
Even My JTL file is properly created but folder is not getting created
Following is the command which I have put in Jenkins Execution shell
cd /mnt/apache-jmeter-5.4/bin
sh jmeter -n -t /mnt/qa/erosnow-auto-test/JMeterAutomation/TestingScript.jmx -l /mnt/qa/erosnow-auto-test/JMeterAutomation/test123.jtl -e -o /mnt/qa/erosnow-auto-test/JMeterAutomation/test123
The message means that the user you're running Jenkins from doesn't have sufficient permissions to create temp/latencyVsRequest folder in your Jenkins workspace, you need to either grant the user the appropriate rights via chown command or change jmeter.reportgenerator.temp_dir property to point to some path where your user has write access.
More information:
Create file in folder: permission denied
JMeter Properties Reference - Reporting Configuration
Apache JMeter Properties Customization Guide
Related
I'm trying to execute some chef commands on a Windows server using Jenkins.
When I run the build on Jenkins to execute the chef commands, I get the error below:
ERROR: Failed to authenticate to 172.54.78.989 as demo-user
Response: WinRM::WinRMAuthorizationError
Hint: Make sure to prefix domain usernames with the correct domain name.
Hint: Local user names should be prefixed with computer name or IP address.
EXAMPLE: my_domain\user_namer
ERROR: WinRM::WinRMAuthorizationError: WinRM::WinRMAuthorizationError
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE
Trying to figure out how to fix this
I was able to fix the issue
It was caused by my user (demo-user) not belonging to domain name that allowed to connect from Chef to the Windows Server.
All I had to do was to get a user that was part of my organization domain name, replace demo-user with that user in my chef commands, and then run the Jenkins build again.
This time it worked fine.
Command Used : ./jmeter -n -t TESTSIT.jmx -JTestEnv=sit2 -l ResultLog.log -e -o ResultLog
the same command generates result from local cmd and gives following exception from ec2 instance
Error message
Error generating the report: org.apache.jmeter.report.dashboard.GenerationException: Error while processing samples: Consumer failed with message :Consumer failed with message :Consumer failed with message :Consumer failed with message :Consumer failed with message :Cannot create temporary file for channel #0
First of all, are you sure your EC2 instance has enough free disk space? You can check it using i.e. df command
Second, it is not very possible to provide a comprehensive answer without seeing the full jmeter.log file, however my another assumption is that your EC2 user doesn't have write access to the OS temporary folder. You can amend jmeter.reportgenerator.temp_dir property and point it to the folder where you have write access for sure, i.e.
./jmeter -Jjmeter.reportgenerator.temp_dir=/tmp -g ResultLog.log -o ResultLog
If it helps you can make the change permanent by adding the above line to user.properties or reportgenerator.properties file.
More information:
Apache JMeter Properties Customization Guide
Reporting Configuration
This error occurred during installation of Oracle on Windows Server 2008.
Details:
Cause - Failed to access the temporary location.
Action - Ensure that the current user has required permissions to access the temporary location.
Additional Information:
- PRVG-1901 : failed to setup CVU remote execution framework directory C:\Users\ADMINI~1\AppData\Local\Temp\2\CVU_12.2.0.1.0_Administrator\ on nodes "rgfindbd"
- Cause: An operation requiring remote execution could not complete because
the attempt to set up the Cluster Verification Utility remote
execution framework failed on the indicated nodes at the
indicated directory location because the CVU remote execution
framework version did not match the CVU java verification
framework version. The accompanying message provides detailed
failure information.
- Action: Ensure that the directory indicated exists or can be created and
the user executing the checks has sufficient permission to
overwrite the contents of this directory. Also review the
accompanying error messages and respond to them.
Summary of the failed nodes rgfindbd
- Version of exectask could not be retrieved from node "rgfindbd"
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available
- Version of exectask could not be retrieved from node "rgfindbd"
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available
In the folder, where your setup.exe is, run:
setup -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"
In administrator cmd go to your setup folder then:
For a client installation:
setup
-ignorePrereq
-J"-Doracle.install.client.validate.clientSupportedOSCheck=false"
For a server installation:
setup
-ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"
I can suggest you to
check if RemoteExecService.exe is running from your temp location,
for example C:\Users\\AppData\Local\Temp\oraremservice.
If it does, then kill the process and delete the oraremservice folder.
Rerun your installation
this work in my case
# chmod 777 -R /tmp
Run cmd as administrator
Locate the folder of the setup
And use this
setup -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"
Delete the oraremservicev2 folder in *C:\Users\{name}\AppData\Local\Temp* location and continue the installation. Working fine
Attempting to build my local openwhisk instance using the provided VagrantFile. I am using the ephemeral CouchDB container as my datasource.
During ant clean build deploy I get the following exceptions:
BUILD FAILED
/home/vagrant/openwhisk/build.xml:55: The following error occurred while executing this line:
/home/vagrant/openwhisk/build.xml:99: exec returned: 5
Further up the logs I see the following repeated under the installCatalog.sh section:
[exec] error: The supplied authentication is invalid
I've verified that the couchdb credentials in my cloudant-local.env are correct by executing some test curl commands. Not sure what other authentication credentials it could be complaining about. Any ideas?
http://dumptext.com/6QDOWNE3
When you use an ephemeral Couch instance, you need to start it after ant clean build and before deploy. Further, every time you start the container, you have to run the script tools/db/createImmortalDBs.sh to initialize the authentication store.
ant clean build
tools/db/couchdb/start-couchdb-box.sh ...
tools/db/createImmortalDBs.sh
ant deploy
BTW, Did you mean couchdb-local.env?
I have a jenkins job named 'SampleMavenDeploy1' which copies artifacts(war file,pom.xml) from upstream project('SampleMavenBuild1') successfully to this project.
I have following configuration for this project:
"
Build Steps:
Copy artifacts from another project
Project Name:SampleMavenBuild1
Post-build Actions:
War/Ear files:MavenWebAppV14/target/*.war
Context Path:webapps
Containers:
Tomcat7.x
Manager username:tomcat
Manager Password:tomcat
Tomcat Url:http://localhost:8080/manager/text
"
The build of SampleMavenBuild1(make war file of a maven project) has succeeded. In workspace of this job (SampleMavenDeploy1), there is war file (MavenWebAppV14/target/MavenWebAppV14.war). I have also configured tomcat-users.xml to add user of username 'tomcat' , password 'tomcat' and roles as 'manager-gui' and 'manager-script' .
I am facing following errors in a jenkins build of a job. This job is designed for deploying war file on tomcat7 via CI server. I have also 'deploy to tomcat' plugin installed in jenkins.
Started by user vikas
Building in workspace C:\Users\vikachou\.jenkins\jobs\SampleMavenDeploy1\workspace
Copied 2 artifacts from "SampleMavenBuild1" build number 4
Deploying C:\Users\vikachou\.jenkins\jobs\SampleMavenDeploy1\workspace\MavenWebAppV14\target\MavenWebAppV14.war to container Tomcat 7.x Remote
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception
org.codehaus.cargo.container.ContainerException: Failed to redeploy [C:\Users\vikachou\.jenkins\jobs\SampleMavenDeploy1\workspace\MavenWebAppV14\target\MavenWebAppV14.war]
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:189)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:918)
at hudson.FilePath.act(FilePath.java:896)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Unknown command /manager/text/list
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:566)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:686)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:699)
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:174)
... 16 more
org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Unknown command /manager/text/list
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:566)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:686)
at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:699)
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:174)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
at hudson.FilePath.act(FilePath.java:918)
at hudson.FilePath.act(FilePath.java:896)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Finished: FAILURE
Anyone who can figure out is most welcomed .
Thanks in advance!!!
You need to give permissions to the text-manager to be able to deploy.
Just go to tomcat-users.xml and add this:
<user username="tomcat" password="password" roles="manager-script"/>
Or just give the manager-script permission to your existing tomcat-manager user
You need to set the base URL to localhost:8080/ in the deploy URL, not the manager URL which is localhost:8080/manager/text (which is what happened in my case).
I have the same problem as you. But I had the tomcat users refresh like the first answer of this question and the problem still persists on Jenkins.
When I tried to connect to tomcat admin zone using my navigator, tomcat didn't display the page to me, because the tomcat-admin package was not installed. So I've installed the tomcat7-admin package and restarted tomcat :
sudo apt-get install tomcat7-admin
sudo service tomcat7 restart
Then the problem was fixed. It was because Jenkins couldn't connect with the program. So easy!
All you have to do is add the users and and assign the manager-gui (for GUI access) and manager-script (for access like Jenkins deployment ). Also, make sure to edit the file /webapps/manager/META-INF/context.xml, either to comment out valve or define appropriate reg ex for allow attribute
If it shows a connection error or fails to load when you deploy jenkins.war file on tomcat, then follow the steps below.
Paste the jenkins folder inside tomcat/webapps.
Restart the tomcat (localhost or ip:8080/jenkins)
Jenkins will load and may asks for password.
To get the jenkins admin password then run
{cat /opt/tomcat/.jenkins/secrets/initialAdminPassword}
If the permission is denied to access the password then
sudo chmod 0777 /opt/tomcat/.jenkins/secrets/initialAdminPassword
or else run ls -a there you will see .jenkins folder.