[Isocops] Cron <ibexops at ena> $IBEX_CRON/cronswitch.sh sftp_driver tidy < /dev/null >/dev/null
Cron Daemon
root at ena.sr.unh.edu
Fri Feb 2 02:11:01 EST 2018
/home/ibexops/IBEX/sw/isoc/src/ops/admin/cronswitch.sh: line 100: ilog.sh: command not found
Can't exec "ibex_time": No such file or directory at
/home/ibexops/IBEX/sw/i686-5.e/lib/perl5/site_perl/common_hdr.pl line 51 (#1)
(W exec) A system(), exec(), or piped open call could not execute the
named program for the indicated reason. Typical reasons include: the
permissions were wrong on the file, the file wasn't found in
$ENV{PATH}, the executable in question was compiled for another
architecture, or the #! line in a script points to an interpreter that
can't be run for similar reasons. (Or maybe your system doesn't support
#! at all.)
Use of uninitialized value $file in scalar chomp at
/home/ibexops/IBEX/sw/i686-5.e/lib/perl5/site_perl/common_hdr.pl line 51 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it cannot
do this, so it also tells you what operation you used the undefined value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in your
program. For example, "that $foo" is usually optimized into "that "
. $foo, and the warning will refer to the concatenation (.) operator,
even though there is no . in your program.
Use of uninitialized value in concatenation (.) or string at
/home/ibexops/IBEX/sw/i686-5.e/bin/sftp-mirror.pl line 155 (#1)
Already running with pid 23978
PID PGID SID TTY TIME CMD
Trying to clobber master 23978
kill 23978: No such process
More information about the Isocops
mailing list