Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • It's unlikely to be an issue with the interpreter's path, but more likely to be an issue with environment variables used by the script itself. Commented Apr 18, 2018 at 6:27
  • @Kusalananda, nonsense, original crontab has no environment, EDubman is right. Commented Apr 18, 2018 at 9:47
  • @GerardH.Pille "No environment", really? Try running env >"$HOME/cron.env" in a cron job. Unless the system's default configuration has been totally disfigured, that should output PATH=/usr/bin:/bin to $HOME/cron.env along with other environment variables. Commented Apr 18, 2018 at 9:56
  • @Kusalananda I stand corrected. Commented Apr 18, 2018 at 10:14
  • I forgot to mention that I already tried adding the full path of Python Commented Apr 18, 2018 at 14:17