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

Terminated with fatal signal 11 when connecting to CVS

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • cvs-plugin
    • None
    • Jenkins 1.611 with CVS plugin Version 2.12

      I have recently upgraded the Jenkins from 1.58 to 1.611 and upgraded the CVS plugin. After the upgrade, Build now is failing with the error "Terminated with fatal signal 11".

      Is anyone seeing same issue? any insight on this would be helpful

      Thanks
      BY

          [JENKINS-28295] Terminated with fatal signal 11 when connecting to CVS

          Bobby Yala added a comment -

          CVS plugin version is 2.12 and Here is the last few lines of the error

          Terminated with fatal signal 11
          Core dumped; preserving /tmp/cvs-serv9124 on server.
          CVS locks may need cleaning up.

          ERROR: Cvs task failed

          Thanks
          BY

          Bobby Yala added a comment - CVS plugin version is 2.12 and Here is the last few lines of the error Terminated with fatal signal 11 Core dumped; preserving /tmp/cvs-serv9124 on server. CVS locks may need cleaning up. ERROR: Cvs task failed Thanks BY

          Bobby Yala added a comment -

          I went little further and fixed this error.

          Now seeing a new Error "May 11, 2015 9:22:54 AM hudson.ExpressionFactory2$JexlExpression evaluate
          WARNING: Caught exception evaluating: it.symbolicNames"

          When I rolled back the Jenkins version to 1.590 it works without any issues. It could able to pull all the Tags from CVS.

          Looks like something got changed on cvs-plugin in Jenkins from version 1.591 and this CVS Symbolic Name Parameter got broke and failing to get the Tags from cvs. it gives same error "WARNING: Caught exception evaluating: it.symbolicNames" from Jenkins 1.591 to Jenkins 1.613

          Thanks
          BY

          Bobby Yala added a comment - I went little further and fixed this error. Now seeing a new Error "May 11, 2015 9:22:54 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.symbolicNames" When I rolled back the Jenkins version to 1.590 it works without any issues. It could able to pull all the Tags from CVS. Looks like something got changed on cvs-plugin in Jenkins from version 1.591 and this CVS Symbolic Name Parameter got broke and failing to get the Tags from cvs. it gives same error "WARNING: Caught exception evaluating: it.symbolicNames" from Jenkins 1.591 to Jenkins 1.613 Thanks BY

          Bonsai Bonsai added a comment -

          I've got the same problem (on Jenkins ver. 1.620 from the debian package):
          Terminated with fatal signal 11
          ERROR: Cvs task failed

          Bonsai Bonsai added a comment - I've got the same problem (on Jenkins ver. 1.620 from the debian package): Terminated with fatal signal 11 ERROR: Cvs task failed

          Robert Rusk added a comment -

          For me this issue was resolved by setting CVS compression to '0' (None) in Jenkins system settings.

          It was only happening with a particular jar file; I can only guess that it was some kind of interaction between compression in the jar file and the CVS compression method sending the CVS process into a spin.

          Robert Rusk added a comment - For me this issue was resolved by setting CVS compression to '0' (None) in Jenkins system settings. It was only happening with a particular jar file; I can only guess that it was some kind of interaction between compression in the jar file and the CVS compression method sending the CVS process into a spin.

          James Coleman added a comment -

          Useful info here, thanks rusk

          Jenkins 2.233 CVS plugin 2.19, jobs running for months/years

          A new job that did CVS checkout failed with this error on checkout of one particular file each time.

             "Terminated with fatal signal 11"

             "Core dumped; preserving on server."

             "CVS locks may need cleaning up."

          Existing jobs that did same CVS update did not have a problem.

          Cleanup of lock files required on cvs server each time.

          WORKAROUND: (as described by Robert)

           Manage Jenkins > Configure System >

              CVS set Default Compression Level to None (it was 3 (Recommended))

           

           

           

           

          James Coleman added a comment - Useful info here, thanks rusk .  Jenkins 2.233 CVS plugin 2.19, jobs running for months/years A new job that did CVS checkout failed with this error on checkout of one particular file each time.    "Terminated with fatal signal 11"    "Core dumped; preserving on server."    "CVS locks may need cleaning up." Existing jobs that did same CVS update did not have a problem. Cleanup of lock files required on cvs server each time. WORKAROUND: (as described by Robert)  Manage Jenkins > Configure System >     CVS set Default Compression Level to None (it was 3 (Recommended))        

            Unassigned Unassigned
            lyalaman Bobby Yala
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: