-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maximum execution time of 30 seconds exceeded #80
Comments
Thanks for the details. The file is simply too lengthy for your local server to process. Consider using the media service feature instead. |
Hi Ernesto, |
If you don'tr get any results for anything in the file content, then it's not indexed for sure. That means that the indexing process fails. That could be just a simple server or process performance issue, it is quite a lengthy file, I can imagine the PHP process failing if the server can't handle it. The error message confirms that as well. I suggest the PHP ini changes I mentioned above, longer time and a bit more memory will very likely do the trick. |
Okay, at least there is an error message, which leads somewhere. Error 500 means an internal server error, which will write a log and will lead to the solution here. Usually the easiest way to find the related error in the PHP error log is to replicate the issue, then check the log immediately. You can upload it as well after triggering the error, I can probably find it. |
Check if the error logging is enabled, error 500 will trigger a log, as it's due to a fatal error. Check the php.ini configuration for the log file location. Usually it's in /var/log foldel on the server. |
Well, that error seems to be unrelated, as far as I can tell. Unless the log file can be found somewhere, I can't do much. You may have to consult with the host to see where PHP is actually logging (not by WP configuration), and if the error reporting is enabled with that configuration. |
Try a different error log location, that is the same as it's defined in the wordpress config, so you can't be sure if it's coming from the PHP ini or the config. Note that there are multiple php.ini-s on most servers, one for the CLI and one for the Apache or FPM handler. I suggest only adding the Either way, this is now not plugin related, but I will still try to help if I can. If there is an error 500 reported, that is triggered by a fatal error in the PHP and it has to exist or logged somewhere. PHP fatal errors don't just vanish. |
Well, only thing left is then to direct the error log to a different file in the php.ini to see if that actually directs the log there. Also, might be worth checking the Apache access logs to see if there is something valuable. I honestly don't know what is wrong here. |
Describe the bug
I created an search index including PDF content to be indexed and a search instance.
Then I added a PDF file to the WordPress Media Library (s. attachment, 4MB) and after 30 seconds I get this error message:
"PHP Fatal error: Maximum execution time of 30 seconds exceeded in [...]/wp-content/plugins/ajax-search-pro/includes/classes/Index/Tokenizer.php on line 248"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The PDF content shall be indexed or if maximum execution time is exceeded a fatal error shall be avoided
Screenshots
n/a
Environment checklist
Desktop (please complete the following information):
Smartphone (please complete the following information):
n/a
Additional context
n/a
TestTomHaushalt2023.pdf
The text was updated successfully, but these errors were encountered: