Rebuilding index fails after upgrade to v4 from 3.3.2
Index rebuild fails for large collection:
I just upgraded from 3.3.2 to 4 and attempted to update my indexes. This worked for all of them except the big one which has 2349 entries - it stops at 1600 and the progress bar says:
"An error occurred rebuilding the index. Try again later or contact support."
I'm running EE 2.9.2 build date 20141004.
Other extensions:
AB Pagination v1.6.5
CartThrob v2.5
CartThrob Offers v1.1.1
Category Field v1.5.6
DataGrab v1.8.0
DevDocs v0.1.6
ED Image Resizer v1.0.4
Event Helper v2.2
Expresso v3.3.3
Freebie v0.2.2
Google Sitemap Lite v1.9
Low NoSpam v3.0.0
Low Yearly Archives v2.3.0
Matrix v2.6
Mo' Variables v1.2.1
Playa v4.5.1
SEO Lite v1.4.9.2
Shine PDF v0.1
Snaptcha v1.7.3
Stash v2.6.0
Stringy v1.1
Structure v3.3.14.7
Studio 24 Twitter v0.3
Studio 24 Utils v1.1
TruncHTML v2.0
Twomile Login Redirect v2.1.1
User v3.5.0
All on PHP 5.5.19, memory limit is 768M. MySQL 5.1. If there's a way I can get the indexer to output debug info please let me know and I'll stick it here.
Cheers,
John. 
Replies
Low 9 Mar 2015 15:11
The server responded in an unexpected way here. You can see the response if you open up your browser's web Inspector on the Network tab while it's building. A correct response would be 'true' or an integer. A different response would be an error message generated by EE.
If you're uncertain how to get to it, I'll need to take a look myself. Please send SuperAdmin login credentials to hi at gotolow dot com in that case.
johnrhunt 9 Mar 2015 15:21
Cool thanks Low,
I've fixed it myself.. some of the entries were very, very big and MySQL wasn't happy:
Error Number: 1153 Got a packet bigger than 'max_allowed_packet' bytes
Fixed myself by increasing the allowed packet size:
mysql> set global net_buffer_length=1000000;
Query OK, 0 rows affected (0.01 sec)
mysql> set global max_allowed_packet=1000000000;
Query OK, 0 rows affected (0.00 sec)
It then re-indexed fine.
The only thing I would say is perhaps make error reporting a bit more obvious? If you want, this is probably not something that happens often!
Cheers Low.
Low 9 Mar 2015 15:22
Ah, excellent. I already was looking into making the error reporting better. :)