• Type: Bug
• Resolution: Not A Defect
• Priority: Minor
• Component/s: ec2-plugin
• Labels:

  • slave
• Environment:

  Jenkins: 1.596.3
  Amazon EC2 plugin: 1.28
  Amazon Linux

1. slave-init.txt

   0.9 kB

   2015-06-09 14:43

2. 

   jenkins-slave-config.png

   140 kB

   2015-06-09 14:42

[JENKINS-28811] Can't start background process during init of new worker?

Vincent Rivellino created issue - 2015-06-09 14:38

Vincent Rivellino made changes - 2015-06-09 14:40

Description

Original: I'm utilizing the EC2 plugin to spin up Jenkins worker slaves on-demand. During the start-up of each worker, I want to download and start a selenium server. After downloading the selenium server jar via curl, I've tried starting selenium via the Init Script. Both: {{screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar}} And: {{nohup java -jar /tmp/selenium-server-standalone.jar &}} Fail to start selenium. I've done a little digging, and in each case those commands exit with a status of 0, but it seems like nothing happens. As a workaround, I'm using a cronjob to ensure selenium is running via screen: {{curl -o /tmp/selenium-server-standalone.jar http://selenium-release.storage.googleapis.com/2.46/selenium-server-standalone-2.46.0.jar cat > /etc/cron.d/selenium-hack << _END_ * * * * * ec2-user test -n "\`ls -1 /var/run/screen/S-ec2-user\`" || screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar _END_ sleep 60}} This is pretty hacky. I'd love to start a background process via the Init Script.

New: I'm utilizing the EC2 plugin to spin up Jenkins worker slaves on-demand. During the start-up of each worker, I want to download and start a selenium server. After downloading the selenium server jar via curl, I've tried starting selenium via the Init Script. Both: {{screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar}} And: {{nohup java -jar /tmp/selenium-server-standalone.jar &}} Fail to start selenium. I've done a little digging, and in each case those commands exit with a status of 0, but it seems like nothing happens. As a workaround, I'm using a cronjob to ensure selenium is running via screen: {quote}curl -o /tmp/selenium-server-standalone.jar http://selenium-release.storage.googleapis.com/2.46/selenium-server-standalone-2.46.0.jar cat > /etc/cron.d/selenium-hack << _END_ * * * * * ec2-user test -n "\`ls -1 /var/run/screen/S-ec2-user\`" || screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar _END_ sleep 60{quote} This is pretty hacky. I'd love to start a background process via the Init Script.

Vincent Rivellino made changes - 2015-06-09 14:43

Attachment		New: slave-init.txt [ 29924 ]
Attachment		New: jenkins-slave-config.png [ 29925 ]
Description	Original: I'm utilizing the EC2 plugin to spin up Jenkins worker slaves on-demand. During the start-up of each worker, I want to download and start a selenium server. After downloading the selenium server jar via curl, I've tried starting selenium via the Init Script. Both: {{screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar}} And: {{nohup java -jar /tmp/selenium-server-standalone.jar &}} Fail to start selenium. I've done a little digging, and in each case those commands exit with a status of 0, but it seems like nothing happens. As a workaround, I'm using a cronjob to ensure selenium is running via screen: {quote}curl -o /tmp/selenium-server-standalone.jar http://selenium-release.storage.googleapis.com/2.46/selenium-server-standalone-2.46.0.jar cat > /etc/cron.d/selenium-hack << _END_ * * * * * ec2-user test -n "\`ls -1 /var/run/screen/S-ec2-user\`" || screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar _END_ sleep 60{quote} This is pretty hacky. I'd love to start a background process via the Init Script.	New: I'm utilizing the EC2 plugin to spin up Jenkins worker slaves on-demand. During the start-up of each worker, I want to download and start a selenium server. After downloading the selenium server jar via curl, I've tried starting selenium via the Init Script. Both: {{screen -d -m -L -S selenium java -jar /tmp/selenium-server-standalone.jar}} And: {{nohup java -jar /tmp/selenium-server-standalone.jar &}} Fail to start selenium. I've done a little digging, and in each case those commands exit with a status of 0, but it seems like nothing happens. As a workaround, I'm using a cronjob to ensure selenium is running via screen. It is pretty hacky. I'd love to start a background process via the Init Script. EDIT: I've added a screenshot of the work config, as well as full text of the Init Script.

Francis Upton made changes - 2016-01-25 13:09

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:57

Workflow

Original: JNJira [ 163671 ]

New: JNJira + In-Review [ 197275 ]