Topic: 【ANN】◢◣ Swipp ◢◣ Modern cryptocurrency ● X11 ● POW/POS ● Masternodes - page 11. (Read 19080 times)

may depend on OS?. Who has MN on Windows and receiving awards?

I can simplify the conversation. I've been running 2 SWP masternodes. They're set up the same way (the only difference is that they're on different VPS providers) and up until 140,000 they've been running fine. Once 140,000 hit, one masternode kept receiving rewards but the other stopped. I couldn't find an obvious reason why.

I've recently moved the non-functioning masternode to a VPS from the same provider as for the masternode that does still work. I'm waiting now to see if it will start receiving rewards once it's fully registered on the network. This is essentially as close as I can get to having both masternodes be the same. I won't know what else to do if this doesn't solve the problem. It also makes me a bit wary about my thoughts of moving a masternode to a less crowded IP location to avoid reduced rewards. Seems risky now, assuming I can get this masternode functioning again.

So the VPS isn't running any firewall, ufw is inactive. This was a working configuration with no changes other than trying and then downgrading the upgrade to swippd.

telnet to the port definitely immediately closes. But my working PhantomX nodes (also forked from Peercoin) on the same VPS do the same thing and they are receiving payments. There is no log data explaining that the connection was immediately closed by the daemon, and even telnet localhost [port] does that... so its even more unlikely that a firewall or route limit is in place.

The MN also thinks its active from "masternode debug"..

Separately, my Swipp wallet running v2.1.1.0: Yggdrasil is showing zero connections to the swipp network even after hours. This is a Windows machine on a totally different network... that works with the older Swipp wallet like a champ.

So I would love to know what else may have changed without having to do a diff on the code.

thanks!

Fusion

We noticed we can connect to the port and that we are not being thrown out. Other than that, it's really hard to tell. Sometimes you can get a clue on the side that tries to send a payment to a masternode (by looking in the debug.log), but in this case, it's pretty difficult to know what's going on.

How is your swipp.conf set up ?

Yours, team swipp

I can appreciated that it's a mystery for both parties. Nothing has changed in the masternode code and nothing has changed in the masternodes we're running, but there is this problem of no rewards. Hopefully we're all able to get to the bottom of it somehow. I'll keep experimenting.

Good question. I can pretty much guarantee nothing related to this has changed in the wallet though. Some firewalls will close a port only after an application restarts. It's definitely either the firewall or miss-configured port though, because there is nothing on the other side to handle the connection.

Yours, team swipp

strangely, my MN always worked and received a rewards. But suddenly after 140,000 became a "firewall closed, rejecting connections"   How is this possible?  

Coin added to pool:

http://hashpool.eu

I'm one of those with "unknown issue, this one has us stumped". Any info you can share? I guess I will need to set it up somewhere else, try a fresh start on a new server.

We already went through and troubleshot all the masternodes that in one way or another are not receiving payments. Please see our post concerning this. Most masternodes not receiving payment have a firewall that is incorrectly configured.

Yours, team swipp

Please do not spam the thread and double-post the same thing twice. I already answered this here;

https://bitcointalksearch.org/topic/m.26611707

Yours, team swipp

My MN is on the list as "connects, but then instantly drops our connection".

My debug.log looks like this:

2017-12-19 15:01:00 connect() to 31.148.219.41:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:06 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:01:07 Misbehaving: 115.78.128.102:24055 (0 -> 1)
2017-12-19 15:01:07 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:19 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:25 Misbehaving: 104.251.218.157:24055 (0 -> 1)
2017-12-19 15:01:25 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:31 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:01:40 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:03:32 connect() to 183.181.170.69:24055 failed after select(): Con
2017-12-19 15:03:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:03:44 connect() to 88.117.5.39:24055 failed after select(): Connec
tion refused
2017-12-19 15:03:45 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:46 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:47 SetBestChain: new best=00000000000e8e2ba467a6cf9d182a2ee366a
69f9e5871f5d52eefbc2b49dd61  height=141585  trust=56142781818565511163  blocktru
st=15754019755107  date=12/19/17 15:03:25
2017-12-19 15:03:47 ProcessBlock: ACCEPTED
+2017-12-19 15:03:52 connect() to 31.148.219.41:24055 failed after select(): Con
nection refused
2017-12-19 15:03:58 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:04:10 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:04:11 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:04:23 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused

It thinks all of the incoming connections are misbehaving for some reason.

Coin added to pool:

http://hashpool.eu

anybody can solve this problem?

We updated our pool wallet

http://s1.altcoinix.com/swipp/public

Hi. Actually, most of the "connection refused" messages you are seeing are caused by nodes/wallets that are closed and do not accept connections. This is completely normal.

To troubleshoot this via terminal, you can telnet to your node from the outside with;

telnet

If it holds the connection and lets you enter some characters, it's behaving correctly. If it instantly disconnects  you, something is wrong and most likely caused by a firewall issue.

Yours, team swipp

My MN is on the list as "connects, but then instantly drops our connection".

My debug.log looks like this:

2017-12-19 15:01:00 connect() to 31.148.219.41:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:06 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:01:07 Misbehaving: 115.78.128.102:24055 (0 -> 1)
2017-12-19 15:01:07 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:19 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:25 Misbehaving: 104.251.218.157:24055 (0 -> 1)
2017-12-19 15:01:25 ProcessMessage(ping, 8 bytes) FAILED
2017-12-19 15:01:31 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:01:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:01:40 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:03:32 connect() to 183.181.170.69:24055 failed after select(): Con
2017-12-19 15:03:40 CDarkSendPool::UpdateState() == 3 | 3
2017-12-19 15:03:44 connect() to 88.117.5.39:24055 failed after select(): Connec
tion refused
2017-12-19 15:03:45 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:46 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused
2017-12-19 15:03:47 SetBestChain: new best=00000000000e8e2ba467a6cf9d182a2ee366a
69f9e5871f5d52eefbc2b49dd61  height=141585  trust=56142781818565511163  blocktru
st=15754019755107  date=12/19/17 15:03:25
2017-12-19 15:03:47 ProcessBlock: ACCEPTED
+2017-12-19 15:03:52 connect() to 31.148.219.41:24055 failed after select(): Con
nection refused
2017-12-19 15:03:58 connect() to 78.46.142.25:24055 failed after select(): Conne
ction refused
2017-12-19 15:04:10 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing v
in = CTxIn(COutPoint(8af5718190, 1), scriptSig=)
2017-12-19 15:04:11 connect() to 63.142.252.38:24055 failed after select(): Conn
ection refused
2017-12-19 15:04:23 connect() to 36.55.235.149:24055 failed after select(): Conn
ection refused

It thinks all of the incoming connections are misbehaving for some reason.

Congrats

Yours, team swipp

http://explorer.swippcoin.com/tx/adaace65575b4300695940b5cbac95b31d0ffccd124ef6e1205b9133e97b165f

my first 4.8swp reward!  

The PoW rewards (~4.8 Swipp) will come as well. It takes a little time for the network to normalize. If you got a reward it is working as intended. Remember, it's a random payout, so exactly what you get and how much varies slightly.

Yours, team swipp