Search results

I hope you're right, fingers crossed! :smile:

You watch... Now I've said all that it won't do it again! lol

I'm just running a test now I'm home for the evening. I've closed my wallet after getting them all running again. I'm going to do a grep every 10 mins until they drop off. Hopefully this will tell me how long they're staying on for roughly. I wouldn't think it was start-many related other than...

Hey orangecycle, no worries dude! it's a very good and useful document and it helped me get my MNs running start-many relatively easily... Was expecting it to be a ballache! lol Cheers :smile:

Are there any known issues with MNs deactivating after a couple of hours of the start-many wallet being closed? I rolled out my start-many wallet and it works a charm... Trouble is I'm having to reopen my wallet on my PC every couple of hours, go to the console and run the start-many again... Is...

Seems that way, been running fine for me for the last few hours... :smile:

Well two hours later and my transition to start-many was relatively smooth... I've shifted my increased number of MNs onto two VMs now and got the start-many function working. It's going to be a big time saver going forwards. Should be able to update my MNs in a couple of minutes now...

Ah... That makes more sense! Couldn't figure out why i'd need it but this guide is a bit misleading in that respect... https://github.com/perrywoodin/darkcoin-startmany-guide " Create a darkcoin.conf file Remember... this is local. Make sure your QT is not running. You should already have a...

How should my darkcoin.conf file look? I've done my masternode.conf file as described but not sure what I need to put into the darkcoin.conf file. Can't seem to find an example documented anywhere either. It's more the syntax i need guidance on if anything... Any help appreciated! :smile:

Well, this fork has become a bit of a clusterfuck for my MN set up. Constantly getting kicked off, updating, reindexing etc. Going to take the opportunity to consolidate my set up and utilise this start-many function I think... Sounds like a good idea as I type this but no doubt I'm about to...

Thanks dude. I'll leave them alone for now then :)

All my MNs still snapped. One just stopped the daemon and the other two: "errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues." Does that error message mean that the MN is not functioning properly? Or is it just an observation by the MN...

All of my MNs were down this morning, lovely! Just updated to 11.0.11 and had to do a --reindex. Waiting to see if that's fixed things now... looks like bct is down too!

That's the problem though... I turn up, do the job, then don't get paid - whereas the guy who doesn't show up keeps getting nice fat MN payments! :tongue:

I have to agree to an extent. I've always diligently updated my MNs as soon as the latest versions are available. Sadly, all it seems to bring me is hassle and lost MN payments... Of course, the reason I stick to my policy of updating ASAP is because I want to 'do the right thing' for the good...

Just updating my tMNs but having a problem with getting them to bind to separate IP addresses. They all want to bind to the primary. Each .darkcoin/darkcoin.conf for each user account has the BIND=X.X.X.X:19999 set to the specific public IP. This is correct yes? So for example: User accounts...

All three of my tMNs are updated to the latest version. Hope this helps! :smile: Walter

Haha, same here. Waiting to get my hands on it :)

This is going to be good... :smile::smile::smile: I'll set up a couple of test MNs shortly. Walter

I agree, a necessary evil as it stands... It's interesting to see the forces of economics at work here though! Centralisation and control go hand in glove with the desire and means to increase profit so it's going to be a difficult problem to solve.