I've seen something similar to this; we found that running builds on the master that include shell steps often failed because the java exec() would require too much memory; I believe it attempts to basically fork the entire master process, which may be quite large.
Our solution was to create a slave node that we connect to via ssh, using the same hostname as the master; the master will then connect and launch slave.jar, which has a much smaller footprint and can easily exec the shell. On Thu, Mar 27, 2014 at 5:23 AM, <[email protected]> wrote: > Hello, > > we have sometimes the problem on our jenkins-master that our builds are > failing with the following error: > > exec] 1) ...\Backend\Cronjob\RunnerTest::testRun[exec] shell_exec(): > Unable to execute 'nohup bash -c 'echo 'testcronjob1'' > >*/data/*.../shared-jenkins/tmp//cronjob-532efe285ff844.06237873 2>&1 & > echo $!' > > Sometimes it's working and sometimes it's not. > > Jenkins Version: > ii jenkins 1.535 > Continuous integration system written in Java > > Regards - Willi > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Marc MacIntyre -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
