# DistributedMutex error warnings frequently appearing in logs

**URL:** https://meta.discourse.org/t/distributedmutex/402855
**Category:** Support
**Created:** [May 13, 2026, 11:19am UTC](https://meta.discourse.org/t/distributedmutex/402855 "2026-05-13T11:19:44Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [May 15, 2026, 10:01am UTC](https://meta.discourse.org/t/distributedmutex/402855/8 "2026-05-15T10:01:31Z")

</div>

Thanks for testing that.

In that case I would not treat the AI plugin as the likely cause. It may just have been a coincidence, or the disable/re-enable cycle may have changed some transient state temporarily.

The most useful next thing to capture is probably the request timing and the pattern of when the warning appears.

For example:

```bash
curl -s -o /dev/null \
  -w "total=%{time_total}s connect=%{time_connect}s starttransfer=%{time_starttransfer}s\n" \
  -X POST "https://your-site.example.com/posts.json" \
  -H "Api-Key: YOUR_API_KEY" \
  -H "Api-Username: YOUR_USERNAME" \
  --data-urlencode "title=API timing test" \
  --data-urlencode "raw=Small plain text API test post" \
  --data-urlencode "category=1"

```

If the warning appears again, it would be useful to compare:

1. the `time_total` value from the client side;
2. whether it happens only sometimes or on every API post;
3. whether it happens after a restart/rebuild, or during normal running;
4. whether multiple API requests are being made close together;
5. whether the same API call creates the post successfully and only once.

At this point it still sounds like a warning from the API post-create path taking longer than the short mutex window, rather than evidence of a failed post or duplicate-post problem.

---

_[View the full topic](https://meta.discourse.org/t/distributedmutex/402855)._