You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
Myself and at least 4-5 Masternode operators have ran into this issue over the last two months. The issue is over a period of time, both mainchain and sidechain show a decrease number of in/out connections. In my case, the connections is in:0 and out:16 until I restart my Masternode. I observed this behavior after restarting my MN due to Windows Update:
connection was in:30 out:9 for mainchain and in:16 out:14 for sidechain. node log size 180,544 KB
node log size 123,768 KB
node log size 95,922 KB
node log size 82,630 KB
node log size 79,577 KB
connection was in:7 out: 16 for mainchain and in:1 out:16 for sidechain. node log size 82,417 KB
If I recall correctly, this issue was introduced with the SBFN 3.0.5. I check the logs frequently for my Node Map and remember faintly this issue arising after I ran Ian's script to start the MN.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Myself and at least 4-5 Masternode operators have ran into this issue over the last two months. The issue is over a period of time, both mainchain and sidechain show a decrease number of in/out connections. In my case, the connections is in:0 and out:16 until I restart my Masternode. I observed this behavior after restarting my MN due to Windows Update:
If I recall correctly, this issue was introduced with the SBFN 3.0.5. I check the logs frequently for my Node Map and remember faintly this issue arising after I ran Ian's script to start the MN.
The text was updated successfully, but these errors were encountered: