FUDforum: How To » Rebuild search index failure?

Home » FUDforum » How To » Rebuild search index failure? (Rebuld apparently stopped at 16.27% done)

Show: Today's Messages :: Unread Messages :: Polls :: Message Navigator
| Unsubscribe from topic | Bookmark topic

Rebuild search index failure? [message #187976]

Thu, 12 November 2020 06:09

duffer60

Messages: 6
Registered: November 2020

Karma: 0

Junior Member

add to buddy list
ignore all messages by this user

Using version 3.1.0 on Hostgator Baby shared webhosting.

Messages I knew were in database weren't being found in searches, so I tried rebuilding the search index.

Within about 15 minutes, the following messages appeared:

5.42% done; ETA: 25.00 minutes
10.85% done; ETA: 14.93 minutes
16.27% done; ETA: 11.75 minutes

Since then it's been over 8 hours, with no further progress indicated, and no error messages.

The forum is locked.

This can't be normal, can it?

I haven't received a CPU restriction notice from Hostgator, and Cpanel shows 0% utilization.

SSH is a jailed shell and won't show me the full process list.

Unfortunately I'm a php and mysql newbie, so I don't know how to carry out diagnostics.

The forum has just over 18,000 messages. I sure would hate to nuke the db and start all over from scratch.

I'll greatly appreciate any suggestions.

Thanks!

The Old Duffer

Report message to a moderator

Rate author: +1 -1

Re: Rebuild search index failure? [message #187977 is a reply to message #187976]

Thu, 12 November 2020 07:06

naudefj

Messages: 3771
Registered: December 2004

Karma: 27

Senior Member
Administrator
Core Developer

add to buddy list
ignore all messages by this user

The process obviously terminated and now some messages are indexed and some are not.
Log in to the Admin Control Panel and unlock/ re-enable your forum.
Every empty search on the forum will index a couple of messages, so over time it should auto-correct.

Report message to a moderator

Rate author: +1 -1

Re: Rebuild search index failure? [message #187978 is a reply to message #187977]

Thu, 12 November 2020 08:19

duffer60

Messages: 6
Registered: November 2020

Karma: 0

Junior Member

add to buddy list
ignore all messages by this user

Thank you many times over! That seems to have worked.

Do non-blank queries also help index the message base, or just empty searches?

It's off topic, but I discovered something interesting in the process of following your instructions. I initially misread your advice, and unlocked the forum files instead.

After I re-locked them, none of the page formatting worked. No images, no css, just plain text.

Opening an SSH instance and doing chmod go+r on all the files solved the problem.

find . -depth -exec chmod go+r {} \;

Hope I didn't make any readable that shouldn't be.

All seems to be working now, so no harm done.

Thanks again for your patient help!

The Old Duffer

Report message to a moderator

Rate author: +1 -1

Re: Rebuild search index failure? [message #187982 is a reply to message #187978]

Thu, 12 November 2020 17:57

duffer60

Messages: 6
Registered: November 2020

Karma: 0

Junior Member

add to buddy list
ignore all messages by this user

Thanks again. Successfully rebuilt the search index from ssh (shell) with

nice -10 php indexdb.php yes

It took just under 14 minutes to index about 19,000 messages, apparently without hitting the 25% cpu load limit.

Report message to a moderator

Rate author: +1 -1

Re: Rebuild search index failure? [message #187988 is a reply to message #187982]

Mon, 16 November 2020 13:13

duffer60

Messages: 6
Registered: November 2020

Karma: 0

Junior Member

add to buddy list
ignore all messages by this user

Now no longer able to rebuild the index from shell prompt. I get this error after about 20 minutes:

40.97% done; ETA: 18.83 minutes

Fatal error: Uncaught exception 'Exception' with message '(/home3/xxxxx/fuddata/include/theme/default/db.inc:74 
/home3/xxxxx/public_html/yyyy/fud/adm/indexdb.php:76 
) internal: internal 
Query: DB_UNLOCK: no previous lock established 
_POST: array (
'conf' => 1,
) 
Database version: 5.6.41-84.1 
' in /home3/xxxxx/fuddata/include/core.inc:253
Stack trace:
#0 /home3/xxxxx/fuddata/include/theme/default/db.inc(74): fud_sql_error_handler('DB_UNLOCK: no p...', 'internal', 'internal', '5.6.41-84.1')
#1 /home3/xxxxx/public_html/yyyy/fud/adm/indexdb.php(76): db_unlock()
#2 {main}
thrown in /home3/xxxxx/fuddata/include/core.inc on line 253

EDIT: Sorry for the duplicate post.

[Updated on: Mon, 16 November 2020 13:14]

Report message to a moderator

Rate author: +1 -1