M
dashman - linux masternode mangement made mootastic
- Thread starter moocowmoo
- Start date
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. :/
EDIT: working now
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. :/
Code:
~/dashman$ ping www.dashpay.io
PING www.dashpay.io (128.127.106.235) 56(84) bytes of data.
--- www.dashpay.io ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6000msEDIT: working now
Last edited by a moderator:
problems his netcat is old. doesn't support ipv4/ipv6 flags.. pondering a workaround.
his:
mine:
his:
Code:
$ 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'; use /bin/sh to exec [dangerous!!]
-e filename program to exec after connect [dangerous!!]
-b allow broadcasts
-g gateway source-routing hop point[s], up to 8
-G num source-routing pointer: 4, 8, 12, ...
-h this cruft
-i secs delay interval for lines sent, ports scanned
-k set keepalive option on socket
-l listen mode, for inbound connects
-n numeric-only IP addresses, no DNS
-o file hex dump of traffic
-p port local port number
-r randomize local and remote ports
-q secs quit after EOF on stdin and delay of secs
-s addr local source address
-T tos set Type Of Service
-t answer TELNET negotiation
-u UDP mode
-v verbose [use twice to be more verbose]
-w secs timeout for connects and final net reads
-z zero-I/O mode [used for scanning]
port numbers can be individual or ranges: lo-hi [inclusive];
hyphens in port names must be backslash escaped (e.g. 'ftp\-data').mine:
Code:
$ nc -h
OpenBSD netcat (Debian patchlevel 1.105-7ubuntu1)
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
[-P proxy_username] [-p source_port] [-q seconds] [-s source]
[-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
[-x proxy_address[:port]] [destination] [port]
Command Summary:
-4 Use IPv4
-6 Use IPv6
-b Allow broadcast
-C Send CRLF as line-ending
-D Enable the debug socket option
-d Detach from stdin
-h This help text
-I length TCP receive buffer length
-i secs Delay interval for lines sent, ports scanned
-j Use jumbo frame
-k Keep inbound sockets open for multiple connects
-l Listen mode, for inbound connects
-n Suppress name/port resolutions
-O length TCP send buffer length
-P proxyuser Username for proxy authentication
-p port Specify local port for remote connects
-q secs quit after EOF on stdin and delay of secs
-r Randomize remote ports
-S Enable the TCP MD5 signature option
-s addr Local source address
-T toskeyword Set IP Type of Service
-t Answer TELNET negotiation
-U Use UNIX domain socket
-u UDP mode
-V rtable Specify alternate routing table
-v Verbose
-w secs Timeout for connects and final net reads
-X proto Proxy protocol: "4", "5" (SOCKS) or "connect"
-x addr[:port] Specify proxy address and port
-Z DCCP mode
-z Zero-I/O mode [used for scanning]
Port numbers can be individual or ranges: lo-hi [inclusive]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 with IPv6 support <-- "nc6" only supports ipv6 (I think, he's installing it now for me to find out)
yay, platforms!
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 with IPv6 support <-- "nc6" only supports ipv6 (I think, he's installing it now for me to find out)
yay, platforms!
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! )
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! )
MooCow,
I tried to set up a new MN using ipv6. I see that there are some in the MN list that use ipv6, but mine did not work. I put the address in my masternode.conf file but I get this message kicked back:
"Invalid port detected in masternode.conf ...
must be 9999 for mainnet."
Of course I used the ipv6 address and port :9999 so there is just something missing. I was wondering if someone can show me the correct syntax in the masternode.conf file for a ipv6 address. MooCow, do you know?
Thanks!!!!!!!
use square brackets.
('dashman install' does this for you automatically.
) --> https://github.com/moocowmoo/dashmanmasternodeaddr=[ipv6goeshere]:9999
Jeztah
Active member
CentOS release 6.2 (Final)
Getting an error, the dashd port open line says NO however I did create iptables rules:
-A INPUT -m state --state NEW -p tcp -m multiport --dport "9998,9999" -j ACCEPT
-A OUTPUT -m state --state NEW -p tcp -m multiport --dport "9998,9999" -j ACCEPT
Thanks a bunch
Getting an error, the dashd port open line says NO however I did create iptables rules:
-A INPUT -m state --state NEW -p tcp -m multiport --dport "9998,9999" -j ACCEPT
-A OUTPUT -m state --state NEW -p tcp -m multiport --dport "9998,9999" -j ACCEPT
Thanks a bunch
Last edited by a moderator:
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:
Code:
dashman sync statusyou don't have to run sync every time, this hotfix is just between versions at the moment.
Specifially, 'dashman sync' will pull down my latest commits to master.
'dashman sync [command]' will do above, then run the command you want.
I'll bump the release version to .12 once I've 1) made sure the pending commits do what they're supposed to do and 2) collect enough bugfixes/enhancements to warrant a new sub-version release.
Last edited by a moderator:
Jeztah
Active member
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 for a few seconds (during their update) (another bug I need to squash)
In the meantime, try it by hand:
Code:
cd dashman
git fetch
git checkout master
git reset --hard origin/master
./dashman statusJeztah
Active member
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:
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:
Code:
cd dashman
git fetch
git remote update
git checkout master
git reset --hard origin/master
./dashman statusJeztah
Active member
Thank you for helping with my second mn setup! My other one is on an old Windows server.
It looks perfect except for that dashwhale stuff. Thanks so very much. I'll send you my last mn payment tonight as a small token of thanks.
Is that failure consistent or intermittent?
You're welcome! Glad I could help!
And, much appreciated!
Jeztah
Active member
