dashd problems on new server

TaoOfSatoshi

TaoOfSatoshi

Well-known member
flare UdjinM6 crowning or anyone else who knows:

I'm trying a new VPS server (lower price, same specs as VULTR). I asked for Ubuntu 14.04 but got 14.04.1. When I transfer and try to activate dashd, it says "-bash: ./dashd: No such file or directory. The file is clearly there, and I can make it executable, even remove it, but when I try to run it, that's what happens.

Any ideas, or am I screwed with this provider?

Tao
 
Check if you use right bit version :) I mean if you have a machine with 32 bit do not start dashd 64 bit... :) it is only the one example I had in past with my vps :D but meaby it is not...check it twice ..
 
The dashd and server are both 64 bit. What else could it be? Is the server too advanced? I've never had this issue before...
 
thelazier said:
Please help share result of "ldd ./dashd" and "file ./dashd".
Click to expand...

ldd ./dashd = not a dynamic executable

file ./dashd = ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=43e65a88642524c2c917e69b9d29ddff923b1e4e, stripped
 
TaoOfSatoshi said:
ldd ./dashd = not a dynamic executable

file ./dashd = ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=43e65a88642524c2c917e69b9d29ddff923b1e4e, stripped
Click to expand...
Please try (as root) , I'm not sure if this will work :)
apt-get install libc6 libstdc++6 libgcc1
 
thelazier said:
Please try (as root) , I'm not sure if this will work :)
apt-get install libc6 libstdc++6 libgcc1
Click to expand...

Actually dashd works on Ubuntu 14.04.1 installations without any additional packages, however instead of installing the libs you've mentioned I'd update to the most recent 14.04 version, which is Ubuntu 14.04.2:

Code: 
sudo apt-get update
sudo apt-get upgrade

After that, a "cat /etc/issue" should show "Ubuntu 14.04.2 LTS \n \l". (or use "lsb_release -a" to do basically the same task).
"uname -i" will show you whether you're on a 32 bit or 64 bit Ubuntu.

Depending on that output, (re-) download the corresponding archive from https://www.dashpay.io/downloads/ and try again.
 
Last edited by a moderator:
thelazier said:
Please try (as root) , I'm not sure if this will work :)
apt-get install libc6 libstdc++6 libgcc1
Click to expand...
Thanks for your help.

OK, tried that and it said that it was already installed. After that, I pretty much came to the conclusion that that VPS is fucked somehow, so I cancelled and got a box from another provider. I'm being somewhat of a guinea pig for lowendbox.

dashd started fine on that VPS, and I successfully (I think) started a masternode. Problem is, although everyone else sees it as a node, it doesn't see itself as a node. Weird! What could cause that? Help a dummy out! :grin:

UdjinM6 Debug.log:

2015-05-31 16:06:40 connected to self at 104.238.215.93:57178, disconnecting
2015-05-31 16:06:40 Misbehaving: 104.238.215.93:9999 (0 -> 1)
2015-05-31 16:06:40 ProcessMessage(dseep, 116 bytes) FAILED
2015-05-31 16:06:49 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-05-31 16:07:19 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-05-31 16:07:40 CActiveMasternode::ManageStatus() - Checking inbound connection to '104.238.215.93:9999'
2015-05-31 16:07:40 CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
2015-05-31 16:07:40 CActiveMasternode::ManageStatus() - Could not find suitable coins!
2015-05-31 16:07:40 CActiveMasternode::Dseep() - Error: Masternode is not in a running status
2015-05-31 16:07:40 CActiveMasternode::ManageStatus() - Error on Ping: Masternode is not in a running status
 
Last edited by a moderator:
TaoOfSatoshi Try this pls:
1) make sure your mnprivkey match on both remote and local
2) make sure remote is synced
3) if #1 and #2 is ok - stop remote node, remove peers.dat, start it again. Check if it started and if it's not run "masternode start(-many)" from local again.
 
UdjinM6 said:
TaoOfSatoshi Try this pls:
1) make sure your mnprivkey match on both remote and local
2) make sure remote is synced
3) if #1 and #2 is ok - stop remote node, remove peers.dat, start it again. Check if it started and if it's not run "masternode start(-many)" from local again.
Click to expand...
Thanks! That worked. I guess I've found a new provider. Cheers from a relieved dummy!
 
Hey Tao,

Are you still using Websound? Have they been working well for you? All of my AWS free tier nodes expire this month and am looking for new hosting. That coupon code above still works :)
 
italx said:
Hey Tao,

Are you still using Websound? Have they been working well for you? All of my AWS free tier nodes expire this month and am looking for new hosting. That coupon code above still works :)
Click to expand...
I have nothing but good things to say. Lots of uptime, extremely fast ticket response, and the price is right.
 
My luck so far with them has been mixed. Performance has been very poor over the last few days, finally culminating in a 14 hr downtime yesterday. To make it worse there was no notice and their website showed everything fine. I had other monitoring setup so I was notified when they went down. Can't beet the price but I'm going to diversify my providers after this week.
 
You must log in or register to reply here.
Back
Top