Pages:
Author

Topic: CRAVE: Revival - page 38. (Read 54978 times)

sr. member
Activity: 790
Merit: 261
July 04, 2017, 08:08:21 AM
hi i send crave from my wallet to cryptopia 2 hours ago
is it normal it is not received yet

regards
In your wallet check if your transaction has confirmations.
Status: 0/unconfirmed, broadcast through 2 nodes
hero member
Activity: 824
Merit: 1000
July 04, 2017, 08:07:17 AM
hi i send crave from my wallet to cryptopia 2 hours ago
is it normal it is not received yet

regards
In your wallet check if your transaction has confirmations.
sr. member
Activity: 790
Merit: 261
July 04, 2017, 08:03:26 AM
hi i send crave from my wallet to cryptopia 2 hours ago
is it normal it is not received yet

regards
sr. member
Activity: 434
Merit: 251
July 04, 2017, 07:55:18 AM
Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?
When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.

ok, so as long as my wallet doesnt go under 500 im fine right?
Just dont touch the 500 crave thing. You can select individually the 0.666666 rewards with the advanced coin control and send them wherever you want.

Oh great, i didnt know about this advanced coin control, i just checked and i can select what i want and dont touch the 500! Thanks!!
hero member
Activity: 824
Merit: 1000
July 04, 2017, 07:50:04 AM
Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?
When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.

ok, so as long as my wallet doesnt go under 500 im fine right?
Just dont touch the 500 crave thing. You can select individually the 0.666666 rewards with the advanced coin control and send them wherever you want.
sr. member
Activity: 434
Merit: 251
July 04, 2017, 07:48:27 AM
Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?
When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.

ok, so as long as my wallet doesnt go under 500 im fine right?
hero member
Activity: 824
Merit: 1000
July 04, 2017, 07:47:13 AM
Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?
When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.
You can also make transactions from the MN without touching the first 500 crave sent (need advanced coin control on your wallet)
sr. member
Activity: 434
Merit: 251
July 04, 2017, 07:37:36 AM
Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?
newbie
Activity: 46
Merit: 0
July 03, 2017, 01:47:47 PM
I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.
Well, say each node gets 4 crave per day.  That's 6 rewards per day, or one reward every ~4 hours per node.

I would wait a bit more to see what they do.  The rewards are random, so it might be more or less.

Thanks a lot man, I'll see Smiley
legendary
Activity: 1551
Merit: 1002
♠ ♥ ♣ ♦ < ♛♚&#
July 03, 2017, 01:09:08 PM
I gave assistance to create masternodes, im old  Cry
Good luck with the project
sr. member
Activity: 332
Merit: 263
Embrace The Darkness.
July 03, 2017, 01:05:08 PM
I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.
Well, say each node gets 4 crave per day.  That's 6 rewards per day, or one reward every ~4 hours per node.

I would wait a bit more to see what they do.  The rewards are random, so it might be more or less.
member
Activity: 125
Merit: 20
July 03, 2017, 01:04:09 PM
I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

It's absolutly random, so it's normal))

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.

It's absolutly random, so it's normal))
newbie
Activity: 46
Merit: 0
July 03, 2017, 12:23:44 PM
I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.
sr. member
Activity: 332
Merit: 263
Embrace The Darkness.
July 03, 2017, 12:17:23 PM
I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.
newbie
Activity: 46
Merit: 0
July 03, 2017, 11:36:31 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew Cheesy
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))


And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf


Code:
rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104


Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:
9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)


I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?

You use ipv4 or ipv6 address?

i use ipv4, at the moment they are running since 2 hours...
i got also first rewards, crazy Smiley
but not sure when they are off again.
member
Activity: 125
Merit: 20
July 03, 2017, 09:31:28 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew Cheesy
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))


And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf


Code:
rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104


Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:
9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)


I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?

You use ipv4 or ipv6 address?
newbie
Activity: 46
Merit: 0
July 03, 2017, 09:13:57 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew Cheesy
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))


And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf


Code:
rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104


Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:
9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)


I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?
member
Activity: 125
Merit: 20
July 03, 2017, 07:49:33 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew Cheesy
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))
newbie
Activity: 46
Merit: 0
July 03, 2017, 07:47:17 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew Cheesy
now its gonna working fine
yay
member
Activity: 125
Merit: 20
July 03, 2017, 07:29:57 AM
Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.
Pages:
Jump to: