# Error: Failed to submit solutions response: Request timeout

**URL:** <https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893>\
**Category:** Incentivized Testnet\
**Tags:** gemini\
**Created:** [September 17, 2023, 2:57am UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893 "2023-09-17T02:57:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xorinox](https://avatars.discourse-cdn.com/v4/letter/x/e68b1a/32.png) [@xorinox](https://forum.autonomys.xyz/u/xorinox)\
**Post date:** [September 17, 2023, 2:57am UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893/1 "2023-09-17T02:57:23Z")

</div>

Hello, on sep-11 the farmer process died after running into the error posted below. There were no other non-INFO in the log than what’s posted below

> Blockquote  
> 2023-09-17T01:47:55.776025Z INFO single\_disk\_farm{disk\_farm\_index=1}: subspace\_farmer::reward\_signing: Successfully signed reward hash 0x3e3492a5a636231ed2d476b9c7c611a6c18e94b3146716b98006eb6e40efe124  
> 2023-09-17T01:48:32.382008Z INFO single\_disk\_farm{disk\_farm\_index=0}: subspace\_farmer::reward\_signing: Successfully signed reward hash 0xc95eb4344f471ac2870eb42dddf12a110d9a37c739d19420ad619d4aafca1426  
> 2023-09-17T01:54:33.702866Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703378Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703387Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703395Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703404Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703410Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703417Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703424Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:54:33.703431Z WARN jsonrpsee\_core::client::async\_client::helpers: Subscription Str(“GI5Aq6rHp2ZGtOMd”) is not active  
> 2023-09-17T01:57:35.222617Z INFO subspace\_networking::node\_runner: Added observed address as external: /ip4/192.168.3.1/tcp/30005  
> 2023-09-17T01:57:48.812868Z INFO single\_disk\_farm{disk\_farm\_index=2}: subspace\_farmer::single\_disk\_farm::plotting: Sector replotted successfully sector\_index=83  
> Error: Failed to submit solutions response: Request timeout  
> [srv\_subspace@node-2 subspace]$

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 17, 2023, 3:16am UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893/2 "2023-09-17T03:16:51Z")

</div>

Looks like node was so slow it wasn’t able to process a request, this typically happens when machine is severely overloaded, in particular on disk I/O side from my experience.

---

<div class="post-metadata">

**Author:** ![xorinox](https://avatars.discourse-cdn.com/v4/letter/x/e68b1a/32.png) [@xorinox](https://forum.autonomys.xyz/u/xorinox)\
**Post date:** [September 17, 2023, 3:42am UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893/3 "2023-09-17T03:42:46Z")

</div>

I take your word for it but as for disk I/O I yet have to see heavy load, maybe we define overloaded as per disk I/O?

I am not sitting on top of each machine all the time, but the occasional disk stat never revealed anything concerning. Attached a few minutes of disk IO of nvme drives that are currently plotting/farming. Even if the ~18 MB/s was all random IO (bad for HDD), still no concern at all for flash (sata, sas or nvme)

 ![009](https://canada1.discourse-cdn.com/flex011/uploads/subspace/original/2X/4/4fe3abd29bca82f75c1085f3ec18e02d3bcefb22.jpeg)

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 17, 2023, 9:07pm UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893/4 "2023-09-17T21:07:17Z")

</div>

I have not seen it for a long time, but especially consumer SSDs that are not high-end can “stutter” or “lock up” periodically under heavy load as controller decides what to do with all that data and requests. So generally it would be related to random I/O or general controller slowness. Hard to provide more specifics, if you have monitoring you might want to check load average there.

---

<div class="post-metadata">

**Author:** ![xorinox](https://avatars.discourse-cdn.com/v4/letter/x/e68b1a/32.png) [@xorinox](https://forum.autonomys.xyz/u/xorinox)\
**Post date:** [September 19, 2023, 3:27am UTC](https://forum.autonomys.xyz/t/error-failed-to-submit-solutions-response-request-timeout/1893/5 "2023-09-19T03:27:14Z")

</div>

Somewhat related to that, earlier this year, I was asking if a benchmark cli can be provided, something that would help to assess and support optimizing hardware configuration.