Thanks … but these tail'd logs are going a million mile an hour, I don’t think I’ll catch anything 
I just tried it again, with the /logs/ open, and there’s no new errors, just new warnings. Mostly:
Perhaps search the logs for the category name?
This happens with any category or one specific category?
If you create a new category and rename it the error happens?
Do your categories have a lot of posts?
Just tried renaming a smaller Category and it worked fine.
The one I’m trying to rename sure did.
Nothing there 
Same issue as me then I guess:
Summary:
Something during category renames is touching every topic or every post and causing the operation to time out.
It looks related to the search stuff? That will indeed be very costly and should be moved into a background task.
Hope not, I fear there are already too many of those.
My server-side backups keep failing because even though they’re running at 2am (local time for the majority of users) there’s too much disk activity for it to complete.
…but I don’t want to get this off topic
It is this:
@tgxworld can you kick all the search work including setting version to 0 to a background job?
PR up at https://github.com/discourse/discourse/pull/11161.
EDIT: Merged 
This appears to be fixed in the latest update. Thanks team!
