crowning
Well-known member
Me too, after 60 mins goes to :0 then vanishes
v0.10.16.07 seems not have fixed the 60-minutes-die problem:
Me too, after 60 mins goes to :0 then vanishes
I just got home from work. Out of 4 masternodes I manage, three were offline. The one that was online still had the cold wallet on my home PC open.
I've just ran the command grep HotCold .darkcoin/debug.log
Maybe it will help with the cold/hot wallet setup. I guess i'll know in an hour.
That command does nothing...just searches the debug log. I'd say shut down both sides, restart and leave both open.
I was keeping it online all the day and it didn't change anything (16.6-16.7). Have listed mn too on 16.8, go to bed now. Will post tomorrow.Know what, I got a feeling of keeping the local online.
So the 2 MN updated on 16.8,I leave one local wallet online and see..
For the moment not exactly one hour. but both of them are still listed...
if(isCapableMasterNode != MASTERNODE_IS_CAPABLE && isCapableMasterNode != MASTERNODE_REMOTELY_ENABLED) return;
#define MASTERNODE_MIN_SECONDS (5*60)
#define MASTERNODE_PING_SECONDS (20*60)
#define MASTERNODE_EXPIRATION_SECONDS (65*60)
#define MASTERNODE_REMOVAL_SECONDS (70*60)
ALL my v0.10.16.08 Masternodes went inactive again after 1 hour and had to be resurrected...
Same here ...v8 looks ok so far...
I'm running a shell script to check my nodes every 5 min.
been 1 hour so far.
Edit: oops all nodes return :0 now :sad: .... now the are not on the MN list.
No I don't have, but other people (Tante2, gwghwgk2hg2h) report the same..dont you people have the "inbound port not open" error when starting masternode from local machine? I would need to take v6 to start from local machine, v7 and v8 give the error
Well one of my MN is on DigitalOcean too, and no problem with v6, 7, and 8...no I am using digital ocean. so i only got the error with v7 and v8, with v6 its working! it got nothing to do with the server i would say