Bitcoin Forum
May 04, 2024, 03:13:17 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Crowdcoin masternode setup issue - SENTINEL test fails  (Read 250 times)
new2mn (OP)
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 06, 2018, 05:53:17 AM
 #1

hi guys, i am new to the masternode setup. trying to setup a Crowdcoin masternode. Followed all install steps as per the guide.. all succeeded except the Sentinel Test at the end..
Not sure if this means the core server is not up or not able to communicate.. below is the error message when i run the Sentinel test -

Please help..

command executed from the Sentinel folder -
./venv/bin/py.test ./test


error message -

address = ('127.0.0.1', 9998), timeout = 30, source_address = None

    def create_connection(address, timeout=_GLOBAL_DEFAULT_TIMEOUT,
                          source_address=None):
        """Connect to *address* and return the socket object.

        Convenience function.  Connect to *address* (a 2-tuple ``(host,
        port)``) and return the socket object.  Passing the optional
        *timeout* parameter will set the timeout on the socket instance
        before attempting to connect.  If no *timeout* is supplied, the
        global default timeout setting returned by :func:`getdefaulttimeout`
        is used.  If *source_address* is set it must be a tuple of (host, port)
        for the socket to bind as a source address before making the connection.
        A host of '' or port 0 tells the OS to use the default.
        """

        host, port = address
        err = None
        for res in getaddrinfo(host, port, 0, SOCK_STREAM):
            af, socktype, proto, canonname, sa = res
            sock = None
            try:
                sock = socket(af, socktype, proto)
                if timeout is not _GLOBAL_DEFAULT_TIMEOUT:
                    sock.settimeout(timeout)
                if source_address:
                    sock.bind(source_address)
                sock.connect(sa)
                return sock

            except error as _:
                err = _
                if sock is not None:
                    sock.close()

        if err is not None:
>           raise err
E           error: [Errno 111] Connection refused

/usr/lib/python2.7/socket.py:575: error
================================= 1 failed, 22 passed in 0.78 seconds =================================
1714835597
Hero Member
*
Offline Offline

Posts: 1714835597

View Profile Personal Message (Offline)

Ignore
1714835597
Reply with quote  #2

1714835597
Report to moderator
Whoever mines the block which ends up containing your transaction will get its fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714835597
Hero Member
*
Offline Offline

Posts: 1714835597

View Profile Personal Message (Offline)

Ignore
1714835597
Reply with quote  #2

1714835597
Report to moderator
1714835597
Hero Member
*
Offline Offline

Posts: 1714835597

View Profile Personal Message (Offline)

Ignore
1714835597
Reply with quote  #2

1714835597
Report to moderator
1714835597
Hero Member
*
Offline Offline

Posts: 1714835597

View Profile Personal Message (Offline)

Ignore
1714835597
Reply with quote  #2

1714835597
Report to moderator
jki123
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
February 06, 2018, 09:57:02 PM
 #2

Hi new2mn,
there is probably something wrong with your rpc-configuration - or your crowdcoin-daemon is not running. Do you get an output from
Code:
crowdcoin-cli getinfo
?
new2mn (OP)
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 07, 2018, 05:10:00 AM
 #3

Here's what i get from crowdcoin-cli getinfo

...# ./crowdcoin-cli getinfo
{
  "version": 120106,
  "protocolversion": 70206,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 47837,
  "timeoffset": 0,
  "connections": 14,
  "proxy": "",
  "difficulty": 305.9925585467279,
  "testnet": false,
  "keypoololdest": 1517892591,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Thanks for looking into it.
jki123
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
February 07, 2018, 07:08:17 AM
 #4

so your daemon is up and running...
have you checked your crowdcoin.conf file? Is there a line determining all rpc-parameters (port, username, password, allowed IP address)? And: is in your sentinel.conf file a line pointing to your crowdcoin.conf file?
new2mn (OP)
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 07, 2018, 08:35:48 AM
 #5

yes. I have the crowdcoin.conf updated with the parameters and sentinel.conf is pointing to the crowdcoin.conf.. 
when i tried to check the ports being used here's what i found..

.... :~/.crowdcoincore/sentinelLinux# lsof -i -P -n | grep LISTEN
sshd      1079 root    3u  IPv4  14355      0t0  TCP *:22 (LISTEN)
sshd      1079 root    4u  IPv6  14364      0t0  TCP *:22 (LISTEN)
crowdcoin 1599 root    9u  IPv6  16319      0t0  TCP *:11998 (LISTEN)
crowdcoin 1599 root   11u  IPv6  16322      0t0  TCP *:12875 (LISTEN)
crowdcoin 1599 root   12u  IPv4  16323      0t0  TCP *:12875 (LISTEN)

it seems like sentinel is trying to get the listener at 9998 but the server is listening at 11998. Not sure if my understanding is correct.. does that make sense ?
jki123
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
February 07, 2018, 04:31:03 PM
 #6

that looks all good - But as far as I understand the error-message it means that the sentinel can not connect via rpc-call to your crowdcoin-daemon. Do you have a firewall on your server?
new2mn (OP)
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 07, 2018, 05:22:39 PM
 #7

yes. i do. the basic firewall..

i have the following ports allowed - 12875, 9998, 11998

Here's the ports listening -

xxxx:~/.crowdcoincore/sentinelLinux# lsof -i -P -n | grep LISTEN
sshd        810 root    3u  IPv4  17480      0t0  TCP *:22 (LISTEN)
sshd        810 root    4u  IPv6  17482      0t0  TCP *:22 (LISTEN)
crowdcoin 23416 root    9u  IPv6  50085      0t0  TCP [::1]:11998 (LISTEN)
crowdcoin 23416 root   10u  IPv4  50087      0t0  TCP 127.0.0.1:11998 (LISTEN)
crowdcoin 23416 root   12u  IPv6  50088      0t0  TCP *:12875 (LISTEN)
crowdcoin 23416 root   13u  IPv4  50089      0t0  TCP *:12875 (LISTEN)
new2mn (OP)
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
February 07, 2018, 06:05:57 PM
 #8

hey jki123, thanks a lot for taking time to help me out. i figure out the issue...
it was a port mismatch.. my rpc was defaulting to 11998 and sentinel was looking for it at 9998
i added the 'rpcport' parameter to crowdcoin.conf and volla!! sentinel tests passed !!

waiting on the wallet reindex and hopefully will get out of the watchdog_expired status finally!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!