0

I have a bash script that it should start at a specific time. I used from at command. When I run it with at, the job create and after the time the job start but it doesn't do it's work. When I run the script without at it works well. I think the problem is bash because it runs sh scripts.

This a part of my script:

#!/usr/local/bin/bash

IFS=' ' read -r -a array <<< "$LIST"
for element in "${array[@]}"
  do
    touch /tmp/$element.call
    cat >> /tmp/$element.call <<-EOF
    Channel: SIP/${element}
    Application: Playback
    Data:${FILE}
    Callerid: ${CALLERID}
    EOF
    mv /tmp/$element.call  /var/spool/asterisk/outgoing/
done

I run the at command like below:

export FILE=hello-world.gsm LIST=4001 5001 6001  CALLERID=123; sudo -E at -t 20210140636.00 -f  /usr/local/bin/asterisk_wakeup_call.sh

would you please help me to find the problem?

Thanks

Improve this question
6
  • Could you add a line with echo test $FILE $LIST $CALLERID > /home/fm/at-test in the beginning. I assume that the variables are not exported as expected. Commented Jan 14, 2021 at 9:08
  • @Fiximan I test it. the file content is correct Commented Jan 14, 2021 at 9:40
  • You could replace the shebang with #!/usr/local/bin/bash -x and check the logs for the output. Anything obvious there? Commented Jan 14, 2021 at 10:00
  • @Fiximan when I set -x option, with at it doesn't show logs. I run script without at it worked. FILE=hello-world.gsm LIST=4001 5001 6001 CALLERID=123 /usr/local/bin/asterisk_wakeup_call.sh Commented Jan 14, 2021 at 10:22
  • I suspect that at is being run from the original user's queue, but the sudo privilege has expired, or cannot be reinstated by the daemon that runs the job. Commented Jan 14, 2021 at 11:11

1 Answer 1

Reset to default
1

The commands read from standard input, or from the file given to the -f option, are executed by sh on FreeBSD, according to the at(1) manual. This means that the #!-line of your script is ignored.

To have your script execute properly, schedule the execution of the script instead of the commands in the script file.

You do this, for example, like so:

echo /usr/local/bin/asterisk_wakeup_call.sh | at -t 20210140636.00

Your complete command (assuming that LIST should be a string with space-separated numbers):

sudo env \
    FILE=hello-world.gsm \
    LIST='4001 5001 6001' \
    CALLERID=123 \
    sh -c 'echo /usr/local/bin/asterisk_wakeup_call.sh | at -t 20210140636.00'

or,

echo /usr/local/bin/asterisk_wakeup_call.sh |
sudo env \
    FILE=hello-world.gsm \
    LIST='4001 5001 6001' \
    CALLERID=123 \
    at -t 20210140636.00

This also uses env to pass the environment variables to the shell that we start, which is safer than using sudo -E. If there are other environment variables that needs to be passed as-is, then you might obviously do this in whatever way you want.

Also note that your time specification, 20210140636.00, is wrong. It lacks one digit somewhere (probably in the specification of the day): 2021 01 40 636 .00

Improve this answer
2
  • Thank for your reply. I tested it but it doesn't do anything. Another guess I made was that it did not have permission. I set the user daemon in sudoers but no succeed Commented Jan 14, 2021 at 14:47
  • @F.M Did you correct the time specification that I pointed out was wrong? Also, you could try running it as at now + 1 minutes as a test. Does the root user get any email from the cron daemon about errors? I don't understand what you mean about setting the daemon user in sudoers. Care to explain? Commented Jan 14, 2021 at 21:54

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.