Recent content by caleb89taylor

We assumed this we be the case. If we reindex manually will it try to reindex all of the existing posts/content or just what isn't currently in ElasticSearch?

@Mike We have an ES cluster set up and we are now preparing to do a production deploy. Here's our big issue: We took a snapshot of our production db and then built the indices of the ES cluster in a staging environment based off of that production snapshot. We were hoping to now just install...

Thanks for the info guys. I don't think we have anyone with extensive knowledge of Elasticsearch so I might be back with more questions when we implement it.

I thought so. We'll make it a priority. Thanks!

Hi guys, We are seeing our db spike to 100% CPU usage occasionally and using MySql workbench I see a lot of queries that are essentially searches for content or content created by users (via xenforo/library/XenForo/Search/SourceHandler/MySqlFt.php). I'm not sure if this is what's causing the...

Fair enough. I'm not sure what was in place before but as far as I know we are relying on the default XF cron job system. I'll list what I know: 1. Cron entries are enabled via admin panel > tools > cron entries and all have future run dates. 2. I can run cron jobs manually via the admin panel...

This might be an option as we've been having a lot of issues recently that may be cron related. I think we need to go back to the beginning and figure out cron problems in general.

I'm not sure I understand this part. I believe we are running it via the standard XF method of cron entries set in the admin panel.

Update to this. I've added logging to the cron jobs in the form of something like this: $logDate = date("Y-m-d H:i:s", XenForo_Application::$time); XenForo_Error::logException(new Exception("runHourlyCleanup start at $logDate"), false, 'Cron job log: '); at the beginning and...

I'll try that just as a quick fix to see if it works but if not I'm going to add logging to narrow down where it's failing and separate out the bigger cleanup methods into separate cron jobs as that one method runs a lot of different cleanup.

Yup that seems to be likely with the size of our db. I'll add some logging. Running it manually caused some errors by locking up our db because of the magnitude of the cleanup run (especially if it has been failing before and hasn't completed the expected task in a while). I'll add some logging...

So it appears that when I ran that hourly cleanup cron job manually that it fixed trophies for a lot of users. Even though it kicked me out to the admin login screen it must've done something as users I didn't manually fix got trophies they should've got a while ago. @Mike You must have had a...

uh I seem to be having issues. I get kicked out of the admin panel and back to the admin login page after the job has been running for a minute or two. We have had authentication issues before as we have custom auth and don't use Xenforo's.

Update: Setting the user's last activity value to today then correctly updated their trophy points when the cron job for trophies ran. So I just need to figure out why some users aren't getting updated. A lot of the users I saw had last_activity fields equal to the day we upgraded from 1.1 to...

I'm trying to think of custom code we added that could've affected that last_activity column getting updated. We did add a check in Xenforo_Model_User::updateSessionActivity() that skips any updating if the userID is 0. We were getting slammed by queries at one point that were updating session...