Nomad periodic doesn't run bash script

Question

I have this periodic task below in nomad. The purpose is to run a script on host nomad3 every 5 minutes. I've also included the contents of the script below.

job "periodic" {
  datacenters = ["dc1"]

  type = "batch"

  periodic {
    cron             = "*/5 * * * * *"
    prohibit_overlap = true
    time_zone        = "UTC"
  }

  group "periodic" {
    count = 1

    restart {
      interval = "5m"
      attempts = 10
      delay    = "25s"
      mode     = "delay"
    }

    task "cronjob-test" {
      driver = "exec"

      constraint {
        attribute = "${node.unique.name}"
        value = "nomad3"
      }

      config {
        command = "/bin/bash"
        args = ["/usr/local/bin/cronjob-test.sh"]
      }

      resources {
        cpu = 100 # Mhz
        memory = 10 # MB

        network {
          mbits = 10

          # Request for a dynamic port
          port "uptime" {
          }
        }
      }
    }
  }
}

with the cronjob-test.sh containing:

#!/usr/bin/env bash

DATE=$(date '+%F-%s')
touch /tmp/$DATE

The script is on nomad host nomad3. I'm supposed to see a file in /tmp with the format I indicated in the bash script but I'm not seeing this. Need help on what is going on.

I've already included the script in the post. It's below the nomad job definition. — FrancisV, Apr 04 '18 at 11:09
yes, if you look at the job definition, it's an absolute path to the script. — FrancisV, Apr 04 '18 at 12:05

score 1 · Answer 1 · answered Apr 04 '18 at 09:24

1

The below script will create a 0 byte file under /tmp:-

DATE=$(date '+%F-%s')
touch /tmp/$DATE //file name would be 2018-04-04-%s

Check your DATE variable whether it is correctly set. Just add a echo command like $DATE and check whether that is accepted or not.

answered Apr 04 '18 at 09:24

Abhijit Pritam Dutta

5,521
2
11
17

That's odd. In my environment, it creates a 0 byte file like so: `-rw-rw-r-- 1 vagrant vagrant 0 Apr 4 11:11 2018-04-04-1522840263` – FrancisV Apr 04 '18 at 11:11
if it is creating a 0 byte file `2018-04-04-1522840263` it is working fine. Your script will simply do that only. – Abhijit Pritam Dutta Apr 04 '18 at 11:18
But the problem is: it's not creating that file. I was expecting this with the nomad periodic job. – FrancisV Apr 04 '18 at 12:04

score 0 · Accepted Answer · answered Apr 27 '18 at 10:42

0

It appears I was using the exec driver which is chrooted. I tried using raw_exec and it worked. I then re-tried using exec by adding the target directory in the chroot_env in the configuration and it worked as well.

answered Apr 27 '18 at 10:42

FrancisV

1,619
5
21
36

score -1 · Answer 3 · edited Jul 24 '19 at 06:01

-1

Use this code:

config {
    command = "/bin/bash"
    args = ["-c"，"/usr/local/bin/cronjob-test.sh"]
  }

edited Jul 24 '19 at 06:01

jkdev

11,360
15
54
77

answered Jul 23 '19 at 01:13

李玉柱

1

Nomad periodic doesn't run bash script

3 Answers3