Search results

Is that failure consistent or intermittent? You're welcome! Glad I could help! And, much appreciated!

I've pushed a patch that will get rid of most of the stderr noise your older distro was creating. as well as fixes to work with git 1.7. I wasn't able to reproduce the netcat error that is causing the failed local-port-open test. Try this version and see if the problem remains: cd dashman git...

I'm spinning up a centos6.2 vagrant instance now. I'll let you know what I find.

that indicates the pull didn't complete for some reason (new one to me), so you're running the same code. notice how the line numbers didn't shift. Also, this one is concerning: It shouldn't even be continuing. odd. The JSON error is due to dashwhale sometimes not having the file in place...

Those line numbers show you're running a slightly older version of .11 which had some netcat problems that I think you may be experiencing. Try this command (sync then run status) and see if it fixes you up: dashman sync status you don't have to run sync every time, this hotfix is just between...

Nice find on the darkcoinj! I'd figured out the first half, but didn't know there was an easy way to extract from the classfile. Good going!

use square brackets. :) ('dashman install' does this for you automatically. :P ) --> https://github.com/moocowmoo/dashman masternodeaddr=[ipv6goeshere]:9999

commit 100! w00t! should fix the issue (for this platform at least!) https://github.com/moocowmoo/dashman/commit/52f7369b0203609ccba6248a9071817d2fe3139b (run dashman sync to pull this in if it's affecting you, already done on the box you gave me access to, paperThin ! Thanks again! )

so it turns out it's a distro thing. Debian I think. They distribute netcat as two different packages. netcat - TCP/IP swiss army knife -- transitional package <-- "nc" only supports ipv4, doesn't have a -4 switch netcat-traditional - TCP/IP swiss army knife netcat6 - TCP/IP swiss army knife...

problems his netcat is old. doesn't support ipv4/ipv6 flags.. pondering a workaround. his: $ nc -h [v1.10-40] connect to somewhere: nc [-options] hostname port[s] [ports] ... listen for inbound: nc -l -p port [-options] [hostname] [port] options: -c shell commands as `-e'...

he already did, MangledBlue :) I'm just logging in now. EDIT: But, I can't work on the problem. Something is completely blocking dashpay.io on that box. I can't even ping it. :/ ~/dashman$ ping www.dashpay.io PING www.dashpay.io (128.127.106.235) 56(84) bytes of data. --- www.dashpay.io...

Problem's definitely within dashman. Grant me access to debug in place? I'll share a screen session with you if you like and you can watch me fix the issue. Use zerobin.net to send credentials to me -- set 'burn after reading' so only I get them, then message me the link.

I understand you. Your masternode can't connect to it's ip is why dashman shows a red "NO" telnet isn't a dashman dependency, it's just another tool to try out. sudo apt-get install telnet to install telnet to try. look for 'connected' here's me trying it out on one of my nodes...

some network configurations (NAT) prevent connecting to the public ip from a host behind masquerading/translation. try "telnet ip.address.of.masternode 9999" from the masternode itself and see if it connects. If it doesn't, you'll have to get more info about your vps instance and network, but...

most current utilities focus on single masternode management. my project 'dashman' https://github.com/moocowmoo/dashman also focuses on single-instance configurations. Once I add machine-readable output, dashman will work well within a monitoring infrastructure, but I've not yet had much...

I think this is it for now... enjoy! dashman version 0.1.11 released protip: you can always run the latest version by prepending 'sync' to your command like 'dashman sync status'

thanks! you can always pull in the latest stuff manually by doing 'dashman sync' https://github.com/moocowmoo/dashman/compare/v0.1.10...master todays commits include: * 40b07dc bugfix - voting - fail gracefully when dash-cli not in path * 618d066 added balance display * 4db404f support...

dashman version 0.1.10 released! added ipv6 support - use icanhazip for ipv4/6 polling added last masternode payment display added dashd uptime calculation added support for hot-node (Internet server) dash.conf voting added initial host metrics: uptime/load average switch to using curl. much...

That's unfortunate to hear. I was hoping to use docker for a lot of upcoming testing projects. Any ideas why? Sweet! I've been thinking about adding some unattended modes, so let me know if you run into a blocker before building your own patch. Also been considering some machine-readable...

Thanks and you're welcome! It's a fun project that scratches a bunch of my personal developer itches. Thanks for the docker image too! I forked it to try and update it to use version .55 but didn't have immediate success (I'm a docker noob) and haven't swung back around to try again.