Running a test network

chaeplin said:
use a cmd at `michael@ubuntuserver16`

dash-cli masternode status

to check masternode status which sentinel checks.
Click to expand...

dash-cli -testnet masternode status
{
"vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service": "71.244.122.102:19999",
"status": "Not capable masternode: Could not connect to 71.244.122.102:19999"
}

but I am definitely listening on 19999 externally, if I run the following at a different site:

telnet 71.244.122.102 19999
Trying 71.244.122.102...
Connected to 71.244.122.102.
Escape character is '^]'.

however, if I run that inside the same LAN as my dash VM

telnet 71.244.122.102 19999
Trying 71.244.122.102...

no connection

Does my dash VM need to be external facing? Right now the VM is on a LAN with an internal IP address. port 19999 forwarded from my router to the VM

Is that my issue?

I'm a little confused on the moving parts...

Could I keep dashd running like it is on the LAN, and move to wallet offsite so that it sees dashd on the external IP and not on 127.0.0.1 or the LAN IP?
 
Last edited:
Strange thing, I just installed dash-qt (win64) on to a windows7 machine, fresh install and when I try to run it with the flag -testnet or even -testnet=1 it will crash. if I add testnet=1 to the dash.conf it will crash in exactly the same way. The only log of the crash comes in eventViewer. It runs without the flag, but of course I want it to connect to testnet, is there anything else I need to do?

Report.wer

Version=1
EventType=APPCRASH
EventTime=131723873483056000
ReportType=2
Consent=1
UploadTime=131723873483326000
ReportIdentifier=7d0be381-661d-11e8-9155-00248ca86aa6
IntegratorReportIdentifier=7d0be380-661d-11e8-9155-00248ca86aa6
Response.BucketId=2265294346
Response.BucketTable=296796575
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=dash-qt.exe
Sig[1].Name=Application Version
Sig[1].Value=0.12.2.3
Sig[2].Name=Application Timestamp
Sig[2].Value=58684680
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_37a8
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.24117
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5add228d
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000bf6b2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=37a8
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=37a8105c60e1a3b2b9c4134e03eaf5e9
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1706
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=1706612f58d44b349e7fce3dddbe946c
UI[2]=C:\Program Files\DashCore\dash-qt.exe
UI[3]=dash-qt.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\DashCore\dash-qt.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\system32\CRYPT32.dll
LoadedModule[9]=C:\Windows\system32\MSASN1.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.dll
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[17]=C:\Windows\system32\NSI.dll
LoadedModule[18]=C:\Windows\system32\WINNSI.DLL
LoadedModule[19]=C:\Windows\system32\ole32.dll
LoadedModule[20]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[21]=C:\Windows\system32\SHELL32.dll
LoadedModule[22]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[23]=C:\Windows\system32\WINMM.dll
LoadedModule[24]=C:\Windows\system32\WS2_32.dll
LoadedModule[25]=C:\Windows\system32\apphelp.dll
LoadedModule[26]=C:\Windows\AppPatch\AppPatch64\AcXtrnal.DLL
LoadedModule[27]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[28]=C:\Windows\system32\rsaenh.dll
LoadedModule[29]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[30]=C:\Windows\system32\uxtheme.dll
LoadedModule[31]=C:\Windows\system32\profapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-2029672950/nBucketTable=296796575/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=dash-qt.exe
AppPath=C:\Program Files\DashCore\dash-qt.exe
Click to expand...

I tried with another Windows7 machine and it worked, but still can't get it going on this machine, weird.
 
Last edited:
Just tried again with latest test build, 12.3.0-RC2 and the same issue persists.

dash_crash.PNG
 
You must log in or register to reply here.
Back
Top