in reply to Re^2: Crontab "Can't open perl script", " No such file or directory"
in thread Crontab "Can't open perl script", " No such file or directory"

That would be a very odd situation indeed considering he said it does run sometimes. If there was an issue determining what binary would interpret the file, it shouldn't ever run.

  • Comment on Re^3: Crontab "Can't open perl script", " No such file or directory"

Replies are listed 'Best First'.
Re^4: Crontab "Can't open perl script", " No such file or directory"
by Anonymous Monk on Oct 09, 2014 at 20:28 UTC
    successful execution manually:
    :~$ bash -l -c '/usr/bin/perl /home/myuser/scripts/perl/flash.pl' running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0 :~$ /usr/bin/perl /home/myuser/scripts/perl/flash.pl running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0 :~/scripts/perl$ ./flash.pl running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0

      Strange. Just some debugging ideas: what happens when running the following commands from the crontab:

      • ls -l /home/myuser/scripts/perl/
      • ls -l /usr/bin/perl
      • file /home/myuser/scripts/perl/flash.pl
      • head /home/myuser/scripts/perl/flash.pl
      • /usr/bin/perl -le 'print "Hello, World"'

        Whoops, forgot the probably most important one: mount

Re^4: Crontab "Can't open perl script", " No such file or directory"
by Anonymous Monk on Oct 09, 2014 at 20:26 UTC
    :~$ bash -l -c '/usr/bin/perl /home/myuser/scripts/perl/flash.pl' running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0 :~$ /usr/bin/perl /home/myuser/scripts/perl/flash.pl running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0 :~/scripts/perl$ ./flash.pl running for: 2014-10-08 get, success 148847 bytes of data. Number of rows affected: 0