cron.php - open_basedir restriction in effect

[Alex-e107nl]

@e107help When on page e107_admin/cron.php?mode=main&action=setup&elan=en i see in the debug after latest changes:

Warning is_file(): open_basedir restriction in effect. File(/usr/local/cpanel/version) is not within the allowed path(s): (/home//:/tmp/:/var/tmp/:/opt/alt/php84/usr/share/pear/:/dev/urandom:/usr/local/php83/lib/:/usr/local/php84/lib/:/usr/local/php82/lib/:/usr/local/php81/lib/:/usr/local/php73/lib/:/usr/local/php83/lib/:/usr/local/php74/lib/:/usr/local/php85/lib/:/usr/local/lib/php/), Line 1765 of /home//domains/********/private_html/e107_handlers/cron_class.php

And

Warning is_file(): open_basedir restriction in effect. File(/usr/local/php83/bin/php8.3) is not within the allowed path(s): (/home//:/tmp/:/var/tmp/:/opt/alt/php84/usr/share/pear/:/dev/urandom:/usr/local/php83/lib/:/usr/local/php84/lib/:/usr/local/php82/lib/:/usr/local/php81/lib/:/usr/local/php73/lib/:/usr/local/php83/lib/:/usr/local/php74/lib/:/usr/local/php85/lib/:/usr/local/lib/php/), Line 1777 of /home//domains/********/private_html/e107_handlers/cron_class.php

Please look at this, why?

[e107help[bot]]

@Alex-e107nl Nothing for you to do, and nothing to change: the cron you already run is untouched by this. What you are looking at is our own Setup page probing paths your open_basedir forbids, and PHP saying so out loud.

Both lines come from cronSetup::detectEnvironment(), which works out your control panel and your PHP binary by stat'ing a short list of absolute paths. Your open_basedir allows /usr/local/php83/lib/ but not /usr/local/php83/bin/, so PHP refuses the stat. I wrote those probes with @ in front expecting silence, which was wrong for a reason that is not the probes' fault: e107's own error handler ignores @. Same fault as your #5992.

#6019 (master) and #6020 (v2.3.x) skip a path open_basedir has already ruled out instead of probing it and hoping. Merging is @Deltik's call.

One thing that will not change either way, so it is worth knowing rather than chasing: on a host like yours the Setup tab cannot see a PHP binary to name, so its command-line option falls back to a bare php. That is a limit on what the page can show you, not a comment on the crontab line you have.