This is really surprising.
Until 24 April I had a perfectly working cron job with this syntax:
/console core:archive --force-all-websites --force-date-last-n=1000 --url=https://piwik.mydomain
Some days before 24 April this cron job gave already a warning message:
"force-date-last-n" is deprecated. Please use the "process_new_segments_from" INI configuration option instead.
Since 24 April this cron job gives only an error message:
/usr/bin/env: php: No such file or directory
According to my server provider, php in this directory is intact, but there could be something with the cron job parameters.
If I consider the cron job warning messages before 24 April, I supposed that I should replace the parameter
"force-date-last-n" by the parameter
But now I have to see, that this recommended parameter
"process_new_segments_from" even doesn’t exist.
Unfortunately I have no direct acccess to a server console. I can only try to change my existing cron job and replace the outdated parameter “
--force-date-last-n=1000” by a working parameter.
But if I read your screenshot correctly, the allegedly deprecated parameter “
--force-date-last-n” is still listed among the valid Matomo archive parameters.
So I am wondering why Matomo or my server gave warning messages before 24 April that “
force-date-last-n” is deprecated.
If it is not deprecated, my old cron job syntax should be working on your system. Do you have the time to try a command like this on your server?:
... php console core:archive --force-all-websites --force-date-last-n=1000 ...