Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48676

After jenkins restart complete directroy got wiped out

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: _unsorted, core
    • Labels:
    • Environment:
      Jenkins version : 2.11
      Java Version : open jdk 1.8.0_45
      OS : Ubuntu 16.04
    • Similar Issues:

      Description

      User reported that Jenkin UI was not loaded properly, when we checked the server load average was too high and jenkins occupied more CPU. So we restarted the jenkins service then after restart it looks like new instance (newly deployed jenkins). We lost all the build configuration and log files which was located inside jenkins home directory.

      Is there any possibility to find out what went wrong? or could please suggest some possible root cause for this.

       

      Regards,

      Mugunthan R

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Without logs I cannot say anything.

          • Do you run Jenkins in a container?
          • Is your JENKINS_HOME mapped/mounted from an external filer or from a volume?
          Show
          oleg_nenashev Oleg Nenashev added a comment - Without logs I cannot say anything. Do you run Jenkins in a container? Is your JENKINS_HOME mapped/mounted from an external filer or from a volume?
          Hide
          mugunthan_r Mugunthan RP added a comment - - edited
          • Do you run Jenkins in a container?

                    No.

          • Is your JENKINS_HOME mapped/mounted from an external filer or from a volume?

                    it is from a volume.

          even /var/log/jenkins directory also wiped out. Is there any way to find out what went wrong? or is there any similiar case happened earlier?

           

          Thanks,

           

          Show
          mugunthan_r Mugunthan RP added a comment - - edited Do you run Jenkins in a container?           No. Is your JENKINS_HOME mapped/mounted from an external filer or from a volume?           it is from a volume. even /var/log/jenkins directory also wiped out. Is there any way to find out what went wrong? or is there any similiar case happened earlier?   Thanks,  
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          No, there is no similar cases. With the current info it seems to be a system configuration error.

          • Have you installed Jenkins using its Debian package (from apt-get)?
          • Have you ever modified its service scripts or configuration files?
          Show
          oleg_nenashev Oleg Nenashev added a comment - No, there is no similar cases. With the current info it seems to be a system configuration error. Have you installed Jenkins using its Debian package (from apt-get)? Have you ever modified its service scripts or configuration files?
          Hide
          mugunthan_r Mugunthan RP added a comment -
          • Have you installed Jenkins using its Debian package (from apt-get)?

                     yes. I have installed jenkins using apt-get

          • Have you ever modified its service scripts or configuration files? 

                     No.

           

          Also Fyi.

          We did dist-upgrade of Ubuntu(14.04 => 16.04 ) on Jun.

           

          Thanks...

          Show
          mugunthan_r Mugunthan RP added a comment - Have you installed Jenkins using its Debian package (from apt-get)?            yes. I have installed jenkins using apt-get Have you ever modified its service scripts or configuration files?             No.   Also Fyi. We did dist-upgrade of Ubuntu(14.04 => 16.04 ) on Jun.   Thanks...
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          I have several instances running on 16.04 without any issues.
          Maybe there are just volume mapping issues

          Show
          oleg_nenashev Oleg Nenashev added a comment - I have several instances running on 16.04 without any issues. Maybe there are just volume mapping issues

            People

            • Assignee:
              Unassigned
              Reporter:
              mugunthan_r Mugunthan RP
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: