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

Starting Hudson execvp: No such file or directory on RHEL4

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Incomplete
    • Component/s: core
    • Labels:
    • Environment:
      cat /etc/redhat-release
      Red Hat Enterprise Linux ES release 4 (Nahant Update 7)
    • Similar Issues:

      Description

      There are two problems with the RPM package for RHEL4:
      1. The daemon binary expects a nicelevel to be given:
      I had to add this to /etc/init.d/hudson:

      NICELEVEL=0
      daemon $NICELEVEL --user "$HUDSON_USER" --pidfile "$HUDSON_PID_FILE" $JAVA_CMD $PARAMS

      2. Seems to use execvp:
      Starting Hudson execvp: No such file or directory

        Attachments

          Activity

          davidkarlsen davidkarlsen created issue -
          Hide
          davidkarlsen davidkarlsen added a comment -

          I got it working by changing the init.d script, so that it looks like:
          daemon --user "$HUDSON_USER" $JAVA_CMD $PARAMS

          RHEL doesn't use the deaemon package like in debian, it uses a custom script in . /etc/init.d/functions
          which doesn't seem compatible for RHEL. Thus there should be packages specific for this distro.

          Show
          davidkarlsen davidkarlsen added a comment - I got it working by changing the init.d script, so that it looks like: daemon --user "$HUDSON_USER" $JAVA_CMD $PARAMS RHEL doesn't use the deaemon package like in debian, it uses a custom script in . /etc/init.d/functions which doesn't seem compatible for RHEL. Thus there should be packages specific for this distro.
          oleg_nenashev Oleg Nenashev made changes -
          Field Original Value New Value
          Component/s core [ 15593 ]
          Component/s other [ 15490 ]
          Labels rpm
          Hide
          danielbeck Daniel Beck added a comment -

          david: To clarify, you had to remove the --pidfile option? What happened to the $NICELEVEL from the original report?

          Is this still an issue in recent versions of Jenkins installed from scratch? Do you still have this system to provide feedback?

          Show
          danielbeck Daniel Beck added a comment - david: To clarify, you had to remove the --pidfile option? What happened to the $NICELEVEL from the original report? Is this still an issue in recent versions of Jenkins installed from scratch? Do you still have this system to provide feedback?
          Hide
          danielbeck Daniel Beck added a comment -

          No response to comment asking for additional information in several months, so resolving as incomplete.

          Show
          danielbeck Daniel Beck added a comment - No response to comment asking for additional information in several months, so resolving as incomplete.
          danielbeck Daniel Beck made changes -
          Resolution Incomplete [ 4 ]
          Status Open [ 1 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135744 ] JNJira + In-Review [ 187031 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            davidkarlsen davidkarlsen
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: