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

calling phing long running targets spawns new phing processes endlessly

    Details

    • Similar Issues:

      Description

      When calling phing long running targets jenkins spawns many processes of phing concurently, it's like a fork bomb. My server has about 52-81 processes usually, after executing phing task that copies DB from one server to another (it takes about 20minutes) i see about 1000-5000 processes executed by jenkins all calling phing and system just runs out of memory.

        Attachments

          Activity

          Hide
          frank Frank K added a comment - - edited

          I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04.
          Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server.
          Running the exact same command manually on the commandline works just fine and only launches one process.

          This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported!

          Show
          frank Frank K added a comment - - edited I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported!
          Hide
          sogabe sogabe added a comment -

          Any log in system log? Manage Jenkins -> System log -> All Jenkins Logs

          Show
          sogabe sogabe added a comment - Any log in system log? Manage Jenkins -> System log -> All Jenkins Logs
          Hide
          gameshas Justinas Urbanavicius added a comment - - edited

          where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed.

          ok, found it in /var/log/jenkins
          attaching log files

          Show
          gameshas Justinas Urbanavicius added a comment - - edited where are the logs physically located ? Jenkins does not show whole log, and since the issue is quite old i can't find anything about it in the short fragment that is displayed. ok, found it in /var/log/jenkins attaching log files
          Hide
          frank Frank K added a comment -

          I have figured out why it is causing problems for us and resolved it. In our case it was because we configured a full path to the phing binary (which wasn't in the path).
          After adding the phing binary to the /usr/bin (via update-alternatives) and disabling the phing-path its working fine for our Jenkins.

          Show
          frank Frank K added a comment - I have figured out why it is causing problems for us and resolved it. In our case it was because we configured a full path to the phing binary (which wasn't in the path). After adding the phing binary to the /usr/bin (via update-alternatives) and disabling the phing-path its working fine for our Jenkins.

            People

            • Assignee:
              sogabe sogabe
              Reporter:
              gameshas Justinas Urbanavicius
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: