<blockquote>
<p>&quot;Failed to start all required subscriptions&quot;</p>
</blockquote>
<p>As recommended by @KC Gibson, reduce the valency for the IOHK node to two, and restart the node. The remote host is closing your connections, probably due to some connection limiting policy on their end.</p>
<blockquote>
<p>I recently went through a router failure and an upgrade. And with that local and external IP addresses changes. After an IP address update both relay and producer nodes are fetching updates from the blockchain (as in passive node) but not processing transactions. Or at least this is what Guild Live View is showing.</p>
</blockquote>
<p>If your issue is that gLiveView is not 'processing transactions', then you must first set <code>TraceMempool</code> to <code>true</code> in your <code>mainnet-config.json</code> to enable this feature.</p>
<blockquote>
<p>Interestingly the producer node just minted a block that I take that will be lost on network write sync up.</p>
</blockquote>
<p><code>cardano-node</code> uses a 'pull' system for sharing blockchain data, so your ability to broadcast blocks depends on other nodes connecting to yours to pull data.</p>
<p>pool.vet suggests that you may not be well connected because you don't use topologyUpdater. Nevertheless, it reports that you should have one inbound connection from an IOHK node, and this is enough for you to publish blocks. Your netstat example doesn't show this, but if you run <code>netstat -pant | grep cardano-node</code> on your relay, you will see an incoming connection from IOHK.</p>

CC BY-SA 4.0
2021-05-04T00:25:30.963Z
2021-05-04T00:25:30.963Z
soccer193
<h3>Description</h3>
<p>I recently went through a router failure and an upgrade. And with that local and external IP addresses changes. After an IP address update both relay and producer nodes are fetching updates from the blockchain (as in passive node) but not processing transactions. Or at least this is what Guild Live View is showing. Interestingly the producer node just minted a block that I take that will be lost on network write sync up.</p>
<h3><strong>Setup</strong></h3>
<ul>
<li>Relay node: 192.168.0.12</li>
<li>Producer node: 192.168.0.10</li>
<li>IP: 82.44.254.62</li>
<li>Adapools: <a href="https://adapools.org/pool/41f3b15c7c181a004e178446c33a379c686d404aa99ad680199d8b83" rel="nofollow noreferrer">see here</a></li>
<li>Pooltool: <a href="https://pooltool.io/pool/41f3b15c7c181a004e178446c33a379c686d404aa99ad680199d8b83" rel="nofollow noreferrer">see here</a></li>
<li>Pool.vet: <a href="https://pool.vet/#41f3b15c7c181a004e178446c33a379c686d404aa99ad680199d8b83" rel="nofollow noreferrer">see here</a></li>
</ul>
<h3><strong>Topology</strong></h3>
<p>a) Relay</p>
<pre><code>  1 {
  2   &quot;Producers&quot;: [
  3     {
  4       &quot;addr&quot;: &quot;192.168.0.10&quot;,
  5       &quot;port&quot;: 6000,
  6       &quot;valency&quot;: 1
  7     },
  8     {
  9       &quot;addr&quot;: &quot;relays-new.cardano-mainnet.iohk.io&quot;,
 10       &quot;port&quot;: 3001,
 11       &quot;valency&quot;: 50 
 12     }
 13   ]
 14 }
</code></pre>
<p>b) Producer</p>
<pre><code>  1 {
  2   &quot;Producers&quot;: [
  3     {
  4       &quot;addr&quot;: &quot;192.168.0.12&quot;,
  5       &quot;port&quot;: 6000,
  6       &quot;valency&quot;: 1
  7     }
  8   ]
  9 }

                                                                                                                                                                                                          
</code></pre>
<h3><strong>Exceptions</strong> (might be related as well as might not):</h3>
<p>a) Relay</p>
<pre><code>20844 Apr 27 18:52:38 jolanta bash[677]: [jolanta:cardano.node.ChainDB:Notice:108] [2021-04-27 17:52:38.20 UTC] Chain extended, new tip: 1e774042b9adf5e4d4677dac54069ecce09926af382f5979e3db3200bfae31f2 at slot 2      7979667
20845 Apr 27 18:52:51 jolanta bash[677]: [jolanta:cardano.node.DnsSubscription:Error:2319] [2021-04-27 17:52:51.67 UTC] Domain: &quot;relays-new.cardano-mainnet.iohk.io&quot; Application Exception: 204.236.187.238:3001 Mu      xError MuxBearerClosed &quot;&lt;socket: 45&gt; closed when reading data, waiting on next header True&quot;
20846 Apr 27 18:52:51 jolanta bash[677]: [jolanta:cardano.node.ErrorPolicy:Warning:127] [2021-04-27 17:52:51.67 UTC] IP 204.236.187.238:3001 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxB      earerClosed &quot;&lt;socket: 45&gt; closed when reading data, waiting on next header True&quot;))) 20s 20s
20847 Apr 27 18:52:52 jolanta bash[677]: [jolanta:cardano.node.DnsSubscription:Notice:4453] [2021-04-27 17:52:52.72 UTC] Domain: &quot;relays-new.cardano-mainnet.iohk.io&quot; Connection Attempt Start, destination 3.9.116      .228:3001
</code></pre>
<h3><strong>Netstat</strong></h3>
<p>a) Relay</p>
<pre><code>maciej@jolanta:~/cardano-node$ netstat -pant | grep 6000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.0.12:6000       0.0.0.0:*               LISTEN      677/cardano-node    
tcp        0      0 192.168.0.12:6000       192.168.0.10:45311      ESTABLISHED 677/cardano-node    
tcp        0      0 192.168.0.12:37851      192.168.0.10:6000       ESTABLISHED 677/cardano-node 
</code></pre>
<p>b) Producer</p>
<pre><code>maciej@wladyslawa:~/cardano-node$ netstat -pant | grep 6000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.0.10:6000       0.0.0.0:*               LISTEN      718/cardano-node    
tcp        0      0 192.168.0.10:6000       192.168.0.12:37851      ESTABLISHED 718/cardano-node    
tcp        0      0 192.168.0.10:45311      192.168.0.12:6000       ESTABLISHED 718/cardano-node   
</code></pre>
<p><a href="https://i.sstatic.net/9CXx2.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/9CXx2.png" alt="enter image description here" /></a></p>
<p>UPDATE:</p>
<h3>Logs</h3>
<p>Relay:
<a href="https://www.dropbox.com/s/w4sv5vt74vyk5n6/relay-node?dl=0" rel="nofollow noreferrer">Download</a></p>
<p>Producer:
<a href="https://www.dropbox.com/s/37pvt1dxo8ridd2/producer-node?dl=0" rel="nofollow noreferrer">Download</a></p>

CC BY-SA 4.0
2023-04-05T14:20:16.833Z
Hey very off topic but what is that terminal chart you have to see the status of the cardano-node?
CoderMan
CC BY-SA 4.0
2021-04-27T20:21:36.970Z
See this https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node
Ghost
CC BY-SA 4.0
2021-04-27T20:59:55.957Z
Thanks. Did the whole IP address change according to this very guide. Paragraph 18.4
https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node#18-4-changing-the-pledge-fee-margin-etc
matcheek
CC BY-SA 4.0
2021-04-27T21:02:33.013Z
Sorry not sure :)
Ghost
CC BY-SA 4.0
2021-04-27T22:57:50.160Z
Have you verified that both machines are running with the correct IP and has firewalls allowing for the new IPs? The relay might be pushing blocks to the BP, but the BP may not be able to push its blocks back to the relay.
Casey Gibson
CC BY-SA 4.0
2021-04-28T10:00:55.103Z
Thanks. Yes, I nmapped from the same subnet and can see that both relay and producer ports are reachable. Also, have updated the question with the logs
matcheek
CC BY-SA 4.0
2021-05-02T10:12:55.063Z
did you disable "TraceMempool" in main config file ? 
can you send screen for your relay ?
Mahdi Gh
CC BY-SA 4.0
2021-05-03T09:46:30.023Z
Try dropping your valency down to the recommended 2 for your IOHK connection. You might be chocking it with too many connections.
Casey Gibson
<stake-pool><block-production>
Stake pool - Failed to start all required subscriptions
# Stake pool - Failed to start all required subscriptions

(Asked by: username_0 on 2021-04-27)

Description
I recently went through a router failure and an upgrade. And with that local and external IP addresses changes. After an IP address update both relay and producer nodes are fetching updates from the blockchain (as in passive node) but not processing transactions. Or at least this is what Guild Live View is showing. Interestingly the producer node just minted a block that I take that will be lost on network write sync up.
Setup

Relay node: 192.168.0.12
Producer node: 192.168.0.10
IP: 82.44.254.62
Adapools: see here
Pooltool: see here
Pool.vet: see here

Topology
a) Relay
  1 {
  2   "Producers": [
  3     {
  4       "addr": "192.168.0.10",
  5       "port": 6000,
  6       "valency": 1
  7     },
  8     {
  9       "addr": "relays-new.cardano-mainnet.iohk.io",
 10       "port": 3001,
 11       "valency": 50 
 12     }
 13   ]
 14 }

b) Producer
  1 {
  2   "Producers": [
  3     {
  4       "addr": "192.168.0.12",
  5       "port": 6000,
  6       "valency": 1
  7     }
  8   ]
  9 }

                                                                                                                                                                                                          

Exceptions (might be related as well as might not):
a) Relay
20844 Apr 27 18:52:38 jolanta bash[677]: [jolanta:cardano.node.ChainDB:Notice:108] [2021-04-27 17:52:38.20 UTC] Chain extended, new tip: 1e774042b9adf5e4d4677dac54069ecce09926af382f5979e3db3200bfae31f2 at slot 2      7979667
20845 Apr 27 18:52:51 jolanta bash[677]: [jolanta:cardano.node.DnsSubscription:Error:2319] [2021-04-27 17:52:51.67 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Application Exception: 204.236.187.238:3001 Mu      xError MuxBearerClosed " closed when reading data, waiting on next header True"
20846 Apr 27 18:52:51 jolanta bash[677]: [jolanta:cardano.node.ErrorPolicy:Warning:127] [2021-04-27 17:52:51.67 UTC] IP 204.236.187.238:3001 ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxB      earerClosed " closed when reading data, waiting on next header True"))) 20s 20s
20847 Apr 27 18:52:52 jolanta bash[677]: [jolanta:cardano.node.DnsSubscription:Notice:4453] [2021-04-27 17:52:52.72 UTC] Domain: "relays-new.cardano-mainnet.iohk.io" Connection Attempt Start, destination 3.9.116      .228:3001

Netstat
a) Relay
maciej@jolanta:~/cardano-node$ netstat -pant | grep 6000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.0.12:6000       0.0.0.0:*               LISTEN      677/cardano-node    
tcp        0      0 192.168.0.12:6000       192.168.0.10:45311      ESTABLISHED 677/cardano-node    
tcp        0      0 192.168.0.12:37851      192.168.0.10:6000       ESTABLISHED 677/cardano-node 

b) Producer
maciej@wladyslawa:~/cardano-node$ netstat -pant | grep 6000
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.0.10:6000       0.0.0.0:*               LISTEN      718/cardano-node    
tcp        0      0 192.168.0.10:6000       192.168.0.12:37851      ESTABLISHED 718/cardano-node    
tcp        0      0 192.168.0.10:45311      192.168.0.12:6000       ESTABLISHED 718/cardano-node   


UPDATE:
Logs
Relay:
Download
Producer:
Download

**Tags:** stake-pool, block-production
> **Comments:**
> **username_2**: See this https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node  
> **username_0**: Thanks. Did the whole IP address change according to this very guide. Paragraph 18.4 https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node#18-4-changing-the-pledge-fee-margin-etc  
> **username_2**: Sorry not sure :)  
> **username_3**: Have you verified that both machines are running with the correct IP and has firewalls allowing for the new IPs? The relay might be pushing blocks to the BP, but the BP may not be able to push its blocks back to the relay.  
> **username_0**: Thanks. Yes, I nmapped from the same subnet and can see that both relay and producer ports are reachable. Also, have updated the question with the logs  
> **username_4**: did you disable "TraceMempool" in main config file ?  can you send screen for your relay ?  
> **username_3**: Try dropping your valency down to the recommended 2 for your IOHK connection. You might be chocking it with too many connections.  
> **username_1**: Hey very off topic but what is that terminal chart you have to see the status of the cardano-node?  

---

## 1 answers

### Answer by username_5 on 2021-05-04. Score: 4 | Accepted answer

> "Failed to start all required subscriptions"

As recommended by @KC Gibson, reduce the valency for the IOHK node to two, and restart the node. The remote host is closing your connections, probably due to some connection limiting policy on their end.

> I recently went through a router failure and an upgrade. And with that local and external IP addresses changes. After an IP address update both relay and producer nodes are fetching updates from the blockchain (as in passive node) but not processing transactions. Or at least this is what Guild Live View is showing.

If your issue is that gLiveView is not 'processing transactions', then you must first set `TraceMempool` to `true` in your `mainnet-config.json` to enable this feature.

> Interestingly the producer node just minted a block that I take that will be lost on network write sync up.

`cardano-node` uses a 'pull' system for sharing blockchain data, so your ability to broadcast blocks depends on other nodes connecting to yours to pull data.

pool.vet suggests that you may not be well connected because you don't use topologyUpdater. Nevertheless, it reports that you should have one inbound connection from an IOHK node, and this is enough for you to publish blocks. Your netstat example doesn't show this, but if you run `netstat -pant | grep cardano-node` on your relay, you will see an incoming connection from IOHK.


---

