My shekel.conf file is empty and my wallet is out of sync..
can someone help please..
Topic: [ANN][JEW] Shekel-Global Decentralized Cryptocurrency-PoS/Masternodes-No ICO - page 6. (Read 38374 times)
April 22, 2018, 08:07:49 PM
April 19, 2018, 11:16:48 PM
hello DEV. y wallet continues to show NO BLOCK SOURCE AVAILABLE. Been two days now even with consistent internet connection. Please what do I do?
Has there been any resolution on this? I have the same issue and I will not do the masternode install if the wallet will not sync...
April 19, 2018, 04:26:43 PM
It’s interesting to see the progress of this project, very clear and systematic. I hope good price this coin for listing in exchanges
April 19, 2018, 05:34:03 AM
The coin fraud, hope the line industry association to give punishment, the exchange of old COINS
April 18, 2018, 11:10:02 PM
Anyone running multiple MN's on a single VPS? Can this be done for Shekel MN's ?
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=:5503
masternodeaddr=:5503
masternodeprivkey=
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=
masternodeaddr=
masternodeprivkey=
datadir= should not include shekel.conf, it's a pointer to a directory
externalip and masternodeaddr must use port 5500
you need a unique rpcport=
you also need to bind= to IP: another unique port (if you use same IP)
C.
Thank you for the response. The datadir in my question wa a typo. Putting in the bind key was the kicker. Thanks again.
April 18, 2018, 06:50:55 PM
Anyone running multiple MN's on a single VPS? Can this be done for Shekel MN's ?
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=:5503
masternodeaddr=:5503
masternodeprivkey=
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=
masternodeaddr=
masternodeprivkey=
datadir= should not include shekel.conf, it's a pointer to a directory
externalip and masternodeaddr must use port 5500
you need a unique rpcport=
you also need to bind= to IP: another unique port (if you use same IP)
C.
April 18, 2018, 06:28:56 PM
Anyone running multiple MN's on a single VPS? Can this be done for Shekel MN's ?
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=:5503
masternodeaddr=:5503
masternodeprivkey=
Here is what iam trying to do.
1st instance:
shekeld -datadir=/root/.shekel/shekel.conf - All good.
2nd instance
shekeld -datadir=/root/.shekel2/shekel.conf - Errors out with the below error
~/.shekel2# Error: Unable to bind to 0.0.0.0:5500 on this computer. Shekel Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
I have changed the ports in shekel2/shekel.conf to a different port ( 5503 ) but still it appears that the binding is happening to 5500 which is the default port.
rpcuser=shekelrpc
rpcpassword=
rpcport=5502
listen=1
server=1
daemon=1
maxconnections=250
masternode=1
externalip=
masternodeaddr=
masternodeprivkey=
April 18, 2018, 06:18:32 PM
Thanks for your response. I was able to ping the addresses individually. Wonder what the problem was with connect(); Once I destroyed the instance and recreated again the problem went away.
Your not routing properly... try pinging google.com I bet it doesnt work and if it does your still not resolving addresses properly... look into that.... /etc/resolve.conf and googles or opendns's servers in there like 8.8.8.8 and ill bet things work.... I might be out to lunch but this sounds familure
I am trying to get my masternode started.
Any help is appreciated in troubleshooting the following...
On running the command ' shekel-cli masternode status' i get the below message :
error: {"code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Node just started, not yet activated"}
This has been occurring since the past 1 hour. Let me know if this is normal or if there is an underlying screwup on my part.
my debug log has a lot of connection refused messages - Here is a snippet
2018-04-14 11:34:10 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:34:31 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:35:44 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:36:08 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
2018-04-14 11:37:47 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:11 connect() to 199.247.6.191:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:58 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:39:46 connect() to 45.77.9.77:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:29 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:43 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:04 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:41:20 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:23 connect() to 54.37.235.223:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:11 connect() to 139.99.169.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:12 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:45:19 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:09 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:20 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
Any help is appreciated in troubleshooting the following...
On running the command ' shekel-cli masternode status' i get the below message :
error: {"code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Node just started, not yet activated"}
This has been occurring since the past 1 hour. Let me know if this is normal or if there is an underlying screwup on my part.
my debug log has a lot of connection refused messages - Here is a snippet
2018-04-14 11:34:10 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:34:31 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:35:44 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:36:08 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
2018-04-14 11:37:47 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:11 connect() to 199.247.6.191:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:58 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:39:46 connect() to 45.77.9.77:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:29 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:43 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:04 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:41:20 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:23 connect() to 54.37.235.223:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:11 connect() to 139.99.169.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:12 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:45:19 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:09 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:20 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
April 18, 2018, 12:27:47 PM
And how is the development of the milestones in Q2 of the roadmap?
Will the wallet for mobile devices be available by the end of this semester?
Will the wallet for mobile devices be available by the end of this semester?
Yes our android wallet is currently being developed.
The desktop wallet updates may not push out until Q3 before Governance & we are waiting for the mandatory wallet update before listing on new exchanges. We will have AT LEAST have an updated wallet preview this Quarter.
April 18, 2018, 12:25:31 PM
honestly i got problems with stakes since day 1.
on windows it was just not turning green for days.
in last several days i get payment less often thats quite sad cause pos reward will be pushed down automatically.
but like i said worst part about this coin that lots of coins was just left behind on coinsmarkets. such a bad timing for swap.
on windows it was just not turning green for days.
in last several days i get payment less often thats quite sad cause pos reward will be pushed down automatically.
but like i said worst part about this coin that lots of coins was just left behind on coinsmarkets. such a bad timing for swap.
you get less payments cause more coins are being stake (we cant really help that)
April 18, 2018, 10:01:06 AM
honestly i got problems with stakes since day 1.
on windows it was just not turning green for days.
in last several days i get payment less often thats quite sad cause pos reward will be pushed down automatically.
but like i said worst part about this coin that lots of coins was just left behind on coinsmarkets. such a bad timing for swap.
on windows it was just not turning green for days.
in last several days i get payment less often thats quite sad cause pos reward will be pushed down automatically.
but like i said worst part about this coin that lots of coins was just left behind on coinsmarkets. such a bad timing for swap.
April 17, 2018, 04:30:29 PM
dev are you still alive. this coin is going down. people are selling because staking work like shit.
are you going to do something ?
are you going to do something ?
What are you on about?
Staking works fine. So do the masternodes. I should know as I answer the questions in Discord. Not many issues reported vs number of wallets staking!
C.
April 17, 2018, 03:03:09 PM
dev are you still alive. this coin is going down. people are selling because staking work like shit.
are you going to do something ?
are you going to do something ?
April 17, 2018, 09:02:08 AM
And how is the development of the milestones in Q2 of the roadmap?
Will the wallet for mobile devices be available by the end of this semester?
Will the wallet for mobile devices be available by the end of this semester?
April 17, 2018, 08:52:11 AM
this is why i'm not dumping any real money into crypto.
i'm quite poor and losing even 0.029-0.025 of profits is big deal for me.
i still don't understand why its "impossible" to swap remaining unswapped coins.
i'm quite poor and losing even 0.029-0.025 of profits is big deal for me.
i still don't understand why its "impossible" to swap remaining unswapped coins.
April 17, 2018, 08:42:04 AM
i'm very very sad that coinsmarkets coins was left unswapped.
even now after all this dump i could get like 0.029-0.025btc from selling coins that was left there.
lol, fork it
but seriously speaking that is not the only project that have unswapped coins by different reasons. Such life. If I get at least 10% form scryptcc, I will have 3.3BTC
April 17, 2018, 07:01:45 AM
i'm very very sad that coinsmarkets coins was left unswapped.
even now after all this dump i could get like 0.029-0.025btc from selling coins that was left there.
April 16, 2018, 08:43:59 PM
Your not routing properly... try pinging google.com I bet it doesnt work and if it does your still not resolving addresses properly... look into that.... /etc/resolve.conf and googles or opendns's servers in there like 8.8.8.8 and ill bet things work.... I might be out to lunch but this sounds familure
I am trying to get my masternode started.
Any help is appreciated in troubleshooting the following...
On running the command ' shekel-cli masternode status' i get the below message :
error: {"code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Node just started, not yet activated"}
This has been occurring since the past 1 hour. Let me know if this is normal or if there is an underlying screwup on my part.
my debug log has a lot of connection refused messages - Here is a snippet
2018-04-14 11:34:10 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:34:31 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:35:44 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:36:08 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
2018-04-14 11:37:47 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:11 connect() to 199.247.6.191:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:58 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:39:46 connect() to 45.77.9.77:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:29 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:43 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:04 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:41:20 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:23 connect() to 54.37.235.223:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:11 connect() to 139.99.169.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:12 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:45:19 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:09 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:20 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
Any help is appreciated in troubleshooting the following...
On running the command ' shekel-cli masternode status' i get the below message :
error: {"code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Node just started, not yet activated"}
This has been occurring since the past 1 hour. Let me know if this is normal or if there is an underlying screwup on my part.
my debug log has a lot of connection refused messages - Here is a snippet
2018-04-14 11:34:10 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:34:31 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:35:44 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:36:08 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
2018-04-14 11:37:47 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:11 connect() to 199.247.6.191:5500 failed after select(): Connection refused (111)
2018-04-14 11:38:58 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:39:46 connect() to 45.77.9.77:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:29 connect() to 139.99.106.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:40:43 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:04 connect() to 54.37.205.119:5500 failed after select(): No route to host (113)
2018-04-14 11:41:20 connect() to 209.250.243.131:5500 failed after select(): Connection refused (111)
2018-04-14 11:41:23 connect() to 54.37.235.223:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:11 connect() to 139.99.169.14:5500 failed after select(): Connection refused (111)
2018-04-14 11:44:12 connect() to 107.161.24.232:5500 failed after select(): Connection refused (111)
2018-04-14 11:45:19 connect() to 45.77.239.108:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:09 connect() to 107.191.44.102:5500 failed after select(): Connection refused (111)
2018-04-14 11:46:20 connect() to 209.250.241.176:5500 failed after select(): Connection refused (111)
April 16, 2018, 04:05:58 PM
Early investors' money is not change, how to solve? Destruction of the old link is actually an excuse. Has a hidden purpose.
you had time to change. now it is finished.
I was looking all this thread because of other project. I do not have any JEW.
But my advise guys, if you like to have MN or continue to work with project and you do not participate in discord, then I don't know what are you doing. Discord is MUST have tool, especially if you think about MN.
April 16, 2018, 09:57:34 AM
I see this project has great potential. I am very interested and decided to join.
Agree, am In too.
Jump to: