I have restarted Jenkins using the following:
service jenkins stop
service jenkins start
Followed to that I can see some jobs are missing from the GUI.
I have also tried to go the job URL using http://<jenkins_url>/job/<JOBNAME>/
Unfortunately it is also giving:
HTTP ERROR 404
Problem accessing /job/<JOBNAME>/. Reason:
Not Found
Powered by Jetty://
Also performed Doing a Reload Configuration from Disk with no luck.
I checked the config.xml file and I can see it is corrupted. The size of config.xml file is around 110 MB. Why this file got corrupted? How to trace it.
Can anyone give me any pointer how to troubleshoot this problem?
I had the same symptoms, but I'm using a homebrew installation of Jenkins.
The Jenkins machine was shut down improperly, likely from a power outage, so when it came back up it was basically a clean instance. No jobs and no system configurations.
The following solution isn't for your exact use case, but it does solve the problem for some users who return to Jenkins to find it without any jobs.
The solution basically involves you checking to see if you have started the Jenkins service incorrectly or from the wrong place.
...
On to the specific homebrew issue:
For whatever reason, the homebrew.mxcl.jenkins.plist file was found in ~/Library/LaunchDaemons/
It belongs in ~/Library/LaunchAgents/ only.
If this happens, it can be solved as follows
Stop the service:
sudo launchctl unload ~/Library/LaunchDaemons/homebrew.mxcl.jenkins.plist
Reload the correct file, located in ~/Library/LaunchAgents/ by trying the following line in case it's running:
launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist
Note: the above line may yell at you if it's not running, which is ok.
Start it up again:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.jenkins.plist
If all looks good when Jenkins loads again, you can and should
delete homebrew.mxcl.jenkins.plist in ~/Library/LaunchDaemons/:
sudo rm ~/Library/LaunchDaemons/homebrew.mxcl.jenkins.plist
Related
I performed a manual clean by deleting job folders directly into the filesystem, and now I find a stucked running job that I cannot abort.
I've tried the answers here to force it to be stopped, but it doesn't work as it is not able to find the existing job in the system.
Additionally, when I click over the running job I get a 404 error:
"Problem accessing <route_to_job_that_doesnt_exist_anymore>"
Reason: Not found
Is there something I can do to abort this running job without restarting the server?
A way to stop a build (Like actually aborting it) is by adding a /stop at the end of the job url, behind the Build Number.
Example: http://myjenkins/project/123/stop
If this doesn't work, there is also the "Hard Kill". Instead of adding /stop you add /kill. I guess you need Admin Access for that POST action.
Don't know though if it works for jobs that don't exist on the Jenkins Host anymore due to missing filesystems
$ neo4j version
neo4j 3.3.4
Host machine
https://neo4j.com/developer/neo4j-cloud-google-image/
Data Import
neo4j-admin import --database=actors.db --nodes movies.csv --nodes actors.csv --relationships roles.csv
after I changes to neo4j.conf as follows:
#dbms.active_database=graph.db
# changed into
dbms.active_database=actors.db
The server still points to graph.db.
I tried to restart the neo4j service to see if it will help
$ sudo service neo4j restart
However, neo4j.conf gets fully reset, and it is reverted back to
#dbms.active_database=graph.db
what is the proper step by step solution to change neo4j.conf?
Can't comment because I don't have enough reputation points... but did you ever figure this out? I've been running into the same issue.
I overwrite the neo4j.conf file, but everytime I restart the service with:
$ sudo service neo4j restart
The neo4j.conf file goes back to how it was
Update: I was able to figure this out. Chances are you have a neo4j.template file which is used to create the neo4j.conf file each time the database is reset. If you edit that, you should be good to go.
I also ran into same issue. When I dig more I found the answer. It is happening when I am trying to runNeo4J server on aws ec2 instance using custom community ami provided by Neo4j. There is a script having name pre-neo4j.sh which is configured to run on every restart of Neo4j service. Inside that script, it is replacing neo4j.conf on every restart of service with some configured template to preserve public-ip or anything like that.
I'm getting an error msg "Load Generator Unavailable" pop up evry 2 iterations when I run the script via check virtual user.Closing and reopeing Neoload solves the issue.Could any of you please help me in resolving this issue?
This looks like it is a common issue with Neoload across versions, we have seen this across all of our windows installations where we run with localhost as a load generator or when we run with stand-alone generators. Most of the time a stop and restart of the load generators and load controllers will solve this issue. On more rare occasions a complete restart of the controller server needs to happen. This is issue is appearing in the latest version as of the date of my response.
I use to have this problem. I just needed to restart my load generator. All I did was ssh into my load generator that was acting up. Then ran sudo –u neoload /opt/neoload/bin/LoadGeneratorAgent stop then after that I would run sudo –u neoload /opt/neoload/bin/LoadGeneratorAgent start & Exit and restart neoload and I stopped having the problem. You will just replace the path with your own. This is for external load generators not local host generators.
My jenkins setup is not overly complicated, there are just a bit over 200 jobs; the problem I'm having is as follows:
The jobs folder is mounted on NFS drive;
Some of the jobs are creating log file fine, but then it is loosing permissions completely (it becomes 000), resulting in an error on the console regarding log file permissions:
I've checked and rechecked permissions on the folder and all the jobs, but nothing is there stands out that could explain what's the cause of the problem. It's not an issue on its own, but some of the jobs are quite important, and without manually fixing permissions, they can't be debugged.
Any hints would be welcome.
I had the same issue, it's more than likely that your version control (e.g Perforce/SVN) sets log files to read only permissions when synced.
An easy work around to this problem is to add an "Execute Windows Batch Command" build step where you cd into the directory containing your log file and change it's permissions.
Use the commands:
cd
attrib -r
This will alter the permissions of your log file and allow your jobs to write to the file. I'm sure there's other ways of dealing with this issue but this is a pretty quick and easy way.
i am getting this
Windows could not start the SphinxSearch service on Local Computer.
Error 1067: The process terminated unexpectedly.
i got installation instruction from this .
http://blog.robbsnet.com/2011/07/how-to-install-and-implement-sphinx.html
build process is complete but when i start the sphinx search service i got errors .
Try running searchd manually from Command Prompt. Maybe it will give you a useful error message.
Try also looking in searchd.log
For anyone who is still having problems with the Windows service:
Make sure your configuration is correct for both database and paths and the needed folders & files are created.
Make sure that the service "command" matches the correct paths and files, to do so you have to:
Run administrative tools, click on local services, then find SphinxSearch. Click on its properties and read the line the service is trying to execute. If the configuration path doesn't match the service start command, it will fail to start.
FYI, this can also happen because your search data files are corrupt. Easy fix for that is to nuke the files and refill them.