On a local setup and on Tiki25 I used hundreds of times the console with this command:
php console.php i:r -p --log
Since a few days (I updated to the last bread) I have an error.
I believe extra-checks have been added or something has changed in the console process (because my configuration didn't changed) and it is causing all the process to fail if the log file cannot be written:
php console.php i:r -p --log
sh: tesseract: command not found
2023-04-30 02:19 Started rebuilding index...
Logging to file(s):
* ../tmp/Search_Indexer_mysql_xxxxx_tiki25_console.log
Unified search
------
Engine: MySQL, version 5.7.39
< 1 sec/< 1 sec [>---------] Rebuilding...sh: tesseract: command not found
1 sec/1 sec ============================ — Rebuilding preferences indexerror: The search index could not be rebuilt.
"../tmp/Search_Indexer_mysql_xxxx_tiki25_console.log" cannot be opened with mode "w"
The search index could not be rebuilt. "../tmp/Search_Indexer_mysql_xxxx_tiki25_console.log" cannot be opened with mode "w"
I have re-re-run the setup.sh permissions setup.
Removing the "--log" allow the index:rebuilt to complete.
This is may be totally legit and true however, it should not stop the process. "index:rebuild" is critical today to keep freshness of data and correct Tiki behavior.
I suggest a warning to be displayed, but the process to keep on.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |