找不到 Synology Scheduler .sh java 命令

Question

I have a bash script thats only task is to execute a jar file.

sms.sh

java -jar /volume1/homes/jar/smssender.jar

Using my Synology NAS I set up a task.

Adding the command to execute bash script. Adding log output.

Executing my new Task.

Checking the log to see the following error:

/volume1/homes/jar/sms.sh: line 1: java: command not found

Checking Java version/installation:

Checking execution of sh script manually (working):

Anyone with this same strange case? Any workarounds/ideas?

I tried

• Rebooting my NAS
• Uninstall / install Java8 package

but none worked.

Answer 1

When the Synology task scheduler executes the script sms.sh the PATH setting is taken from script /etc/crontab . Which does not contain the Java path.

The default login shell environment is defined int /etc/profile . At the end there is a section to add the Java path.

PATH=$PATH:/var/packages/Java8/target/j2sdk-image/bin # Synology Java runtime enviroment
PATH=$PATH:/var/packages/Java8/target/j2sdk-image/jre/bin # Synology Java runtime enviroment
JAVA_HOME=/var/packages/Java8/target/j2sdk-image/jre # Synology Java runtime enviroment
CLASSPATH=.:/var/packages/Java8/target/j2sdk-image/jre/lib # Synology Java runtime enviroment
LANG=en_US.utf8 # Synology Java runtime enviroment
export CLASSPATH PATH JAVA_HOME LANG # Synology Java runtime enviroment

As already stated in already given comments sourcing a profile script which is meant for an interactive shell isn't suggested. You might mimic the behavior of the /etc/profile script in your sms.sh script to set CLASSPATH PATH JAVA_HOME LANG.

The raised points about hardcoding the path in your script and the resulting reduced portability might have a lover precedence in this specific case.

Answer 2

I'm not familiar with Synology so fwiw ...

The shell script works when executed at the command line because the particular login session has already loaded a set of environment variables (eg, upon logging in the .profile/.bashrc script(s) in the home directory is sourced and the various java-specific environment variables are loaded - PATH, JAVA_HOME, CLASSPATH , etc) that allow java and the script to run without issue.

The failed Synology job error indicates that the java-specific environment variables have not been loaded and therefore the job/script is unable to locate java .

Assuming Synology does not have a configuration setting/flag that stipulates to pre-load a login's profile, the 'easy' solution would be to edit the script ( sms.sh ) and have it source the appropriate resource file before performing any operations (eg, calling java ). A simple example:

$cat sms.sh
#!/usr/bin/bash

. ~root/.bashrc      # load the root account profile before continuing ...

java ...

NOTES :

• replace root with the name of the login under which the script is to be run (in the example Synology images it appears you've chosen the root user hence my example references ~root )
• replace ~root/.bashrc with the path to user's profile in order to pre-load the environment variables needed to allow the script to find java