[6.7.0-rc5] Mover errors out and does not run from cron

"From the mover script, this error is from the mover supposedly already running."

 

Not necessarily. When the mover runs it finishes with this statement

[[ $LOGLEVEL -gt 0 ]] && echo "mover: finished"

By default LOGLEVEL = 0, which lets the mover script terminate with exit code 1

 

Changing the code to

[[ $LOGLEVEL -eq 0 ]] || echo "mover: finished"

would solve the error reporting issue

Edited February 24, 2019 by bonienl

This came up before, apparently that happens when the mover runs on a schedule:

 

 

 

 

 

1 minute ago, johnnie.black said:

This came up before, apparently that happens when the mover runs on a schedule:

Any script running on a schedule needs to terminate with exit code 0, otherwise an error is reported.

18 minutes ago, bonienl said:

Not necessarily. When the mover runs it finishes with this statement

The way I read the script it didn't get that far.

 

11 minutes ago, bonienl said:

Any script running on a schedule needs to terminate with exit code 0, otherwise an error is reported.

I agree.

 

This is not just a situation of the exit code from the mover or the start/stop showing in the log.  I have logging turned off, so I get it that the mover started/stopped messages won't show in the log.

 

Regardless, the mover failed to run.

I've tried to turn on mover logging to catch this error, but I have not been able to catch it.

As a test I changed this to see if it was where the error occurred:

start() {
  if [ -f $PIDFILE ]; then
    if ps h $(cat $PIDFILE) | grep mover ; then
        echo "mover: already running"
        exit 10
    fi
  fi

I got the same error:

Feb 27 03:45:56 BackupServer crond[1675]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

I think bonienl is right.  The error is occurring later in the script and occurs when the logging is turned off.  That's why turning on logging does not create this error.