![\"jenkins-troubleshooting\"](\"http:\/\/www.scmgalaxy.com\/tutorials\/wp-content\/uploads\/2015\/09\/jenkins-troubleshooting.png\")
<\/p>\n<\/p>\n
Jenkins Troubleshooting<\/strong><\/p>\n Jenkins is one of the important CI tools which many organization used as part of their Build and DevOps infrasture. I am going to consolidate all the troubshooting techniques which can be used in order to find any issues related in jenkins.<\/p>\n Step 1.<\/strong> Take a look at Log generated by the jenkins and plugins via http:\/\/jenkins-master\/log<\/a><\/p>\n Note: Here you can also create your own logger and and set your custom log levels such as (severe, warning, info, config, file, finer, finest, all)<\/p>\n Step 2<\/strong>. Also, you can look at \/var\/log\/jenkins\/jenkins.log via doing “tail -f \/var\/log\/jenkins\/jenkins.log” and check carefully whats breaking it.<\/p>\n Log file in windows – jenkins.err.log & jenkins.out.log<\/p>\n Slave log file in windows – logs\\slaves<\/p>\n Step 3.<\/strong> Check the system log file<\/p>\n Step 4. Few Jenkins plugins which can you help you Step 4.<\/strong> Make sure your Jenkins & installed plugins version is installed with most uptodate stable release.<\/p>\n Some Common issues:<\/strong> Issues 2 Site is down with no 404 messages Issues 3 Site is up however no jobs are displayed Issues 4 – java.lang.outofmemoryerror permgen space issues<\/p>\n
\nhttps:\/\/wiki.jenkins-ci.org\/display\/JENKINS\/Monitoring<\/a><\/p>\n
\nIssues 1. If Jenkins hangs, follow https:\/\/wiki.jenkins-ci.org\/display\/JENKINS\/Jenkins+is+hanging<\/a><\/p>\n
\nCause- Jenkins had an Out of Memory (OOM) error causing the server to kill the jenkins instance
\nSolution: Restart server; Review heap logs to identify root cause of error<\/p>\n
\nCause 1: AWS Server rebooted but data volume did not mount properly
\nSolution: mount <device> <path> on the instance<\/p>\n