Recent content by Groatz

Not that I'm aware, but the absence of complaint doesn't mean that users aren't being negatively impacted. We want our users to have a good experience. Anywhere from a thousand to eight thousand simultaneous users. But the error doesn't seem to correlate with instantaneous aggregate user activity.

We are getting the server log error.

Yes.

We have started getting that error recently on XF 2.1.10P2 and our servers are all syncing time.

We have started getting that error recently on XF 2.1.10P2 and our servers are all syncing time.

Happening for us with PHP 7.3.21 (we use stream wrappers).

Sorry, what I mean is do you have an official fix on the horizon? The system value of php is pointing to /tmp to get around the streaming issues (we host on s3) for temporary files as Xon pointed out. That's coming up now in PHP 7.3 for us and not being handled. It's essentially the same issue.

gifsicle 1.91 installed with yum is broken with this addon. No longer has the option 'lossy' since giflossy merged back into gifsicle. Any suggestions?

Sorry, just trying to understand how this is Fixed as the problem still exists and there doesn't seem to be a XenForo workaround or fix in this thread?

This would still appear to be an issue, we're getting same problem as @m1ne. Any fix on the horizon yet?

So was there a conclusion? We've started getting this recently. We use AWS S3 also. PHP 7.3

If ES has one of its (many) conniptions and all shards fail (hopefully someday it will become a stable product) then it will be resolved by XenForo making an ES error a soft-fail that is logged as a warning or notice but essentially the user isn't impacted. Indexing is soft, it can always be...

You are correct. More like ~70,000,000 attachments for us. :-(

From your Setup.php: 'TickTackk\ChangeContentOwner:Upgrade\RebuildAttachmentOwner',

What sort of underlying server issues should we be looking for? Is there a gold standard of what should be checked and corrected?