No Code Attached Yet
avatar brianteeman
brianteeman
21 Jan 2024

Critical error preventing search

Steps to reproduce the issue

Go to the Smart search component options and set

  • Batch index size - to 5 (just so we can show the bug)
  • Enable Logging

Clear the search index
Do a new index

Expected result

Index runs and completed

Actual result

Index stops with an "undefined" error after 5 items
administrator/logs/indexer.php says
image

Doesnt matter which finder plugins are enabled so that error message is not helpful

Doesnt matter what the batch index size is set to it will always stop after the first batch

Additional comments

php 8.1
php 8.2
joomla 5.0.2

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
5.00

avatar brianteeman brianteeman - open - 21 Jan 2024
avatar joomla-cms-bot joomla-cms-bot - change - 21 Jan 2024
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 21 Jan 2024
avatar brianteeman brianteeman - change - 21 Jan 2024
The description was changed
avatar brianteeman brianteeman - edited - 21 Jan 2024
avatar brianteeman
brianteeman - comment - 21 Jan 2024

scan

avatar Quy
Quy - comment - 22 Jan 2024

Unable to reproduce with a clean installation of 5.0.2.

2024-01-22T18:20:50+00:00	INFO 127.0.0.1	-	Starting the indexer
2024-01-22T18:20:51+00:00	INFO 127.0.0.1	-	Starting the indexer batch process
2024-01-22T18:20:51+00:00	INFO 127.0.0.1	-	Batch completed, peak memory usage: 20,971,520 bytes
avatar brianteeman
brianteeman - comment - 22 Jan 2024

Any suggestions how to debug this? It happens 100% time on this live site

avatar Hackwar
Hackwar - comment - 23 Jan 2024

Can you check if this fixes your issue? #42693

avatar brianteeman
brianteeman - comment - 23 Jan 2024

It made no difference. :(

Note that there is no problem when using finder from the CLI

avatar Hackwar
Hackwar - comment - 23 Jan 2024

I can't reproduce it either. If you could open up your browser console and see what the AJAX request returned, we might get a bit wiser.

avatar brianteeman
brianteeman - comment - 23 Jan 2024

Sorry - I completely forgot to check the console

XHR finished loading: GET "redacted/administrator/index.php?option=com_finder&tmpl=component&format=json&task=indexer.start&4148e24ac0e4697f439dcf0791759050=1"

XHR failed loading: GET "redacted/administrator/index.php?option=com_finder&tmpl=component&format=json&task=indexer.batch&4148e24ac0e4697f439dcf0791759050=1"

GET redacted/administrator/index.php?option=com_finder&tmpl=component&format=json&task=indexer.batch&4148e24ac0e4697f439dcf0791759050=1 net::ERR_HTTP2_PROTOCOL_ERROR

avatar Hackwar
Hackwar - comment - 23 Jan 2024

Do you have any additional information in the network tab about the failing AJAX request?

avatar brianteeman
brianteeman - comment - 23 Jan 2024

The network tab just shows the same information

avatar Hackwar
Hackwar - comment - 24 Jan 2024

Without additional information I unfortunately can't help you further.

avatar brianteeman
brianteeman - comment - 24 Jan 2024

No idea what additional information I can provide or how to find it

avatar Hackwar
Hackwar - comment - 24 Jan 2024

Maybe try to see what the result is with debug mode switched on?

avatar brianteeman
brianteeman - comment - 24 Jan 2024

Making some progress - will feedback later

avatar Hackwar
Hackwar - comment - 24 Jan 2024

Any news?

avatar brianteeman
brianteeman - comment - 24 Jan 2024

It was a false dawn. Firefox gave a different error message in the console NS_ERROR_NET_INTERRUPT but apparently that's the normal message for FF when chrome says ERR_HTTP2_PROTOCOL_ERROR

Apache logs did have this extra info but I cant see anything from it
Invalid status line from script 'index.php': 0, referer: redacted/administrator/index.php?option=com_finder&view=indexer&tmpl=component

avatar brianteeman brianteeman - close - 24 Jan 2024
avatar brianteeman brianteeman - change - 24 Jan 2024
Status New Closed
Closed_Date 0000-00-00 00:00:00 2024-01-24 17:59:37
Closed_By brianteeman
avatar brianteeman
brianteeman - comment - 24 Jan 2024

With a lot of help from scalahosting we located the cause of the problem.
It was a 3pd plugin from @ahotzler https://github.com/ahotzler/plg_content_prismsyntaxhighlighter

Add a Comment

Login with GitHub to post a comment