Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    aleqx
    @aleqx
    a workaround is to first create the second account suing grin-wallet account -c myname and then run grin-wallet scan ... the 2nd account will always have m/1/0 path anyway (so transactions and whatnot aren't affected) but it screws up my scripts I had which were looking for myname instead of account_1
    another question I had is: is there a way to preserve my transactions, i.e. to see all their details with grin-wallet txs if I wipe the db folder and restore with grin-wallet scan? I still have the saved_txs folder -- can the be imported somehow? Shouldn't it be reimported automatically when doing a scan on an empty db? Now my txs list is empty (apart from the last two utxos)
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    Is the cuckaroom make command 'make cuda29' or 'make cuda29.0?... or somethng else?
    John Tromp
    @tromp
    in cuckoo/src/cuckaroom it's make cuda29
    but that's not what grin-miner uses
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER

    in cuckoo/src/cuckaroom it's make cuda29

    Great thanks!

    but that's not what grin-miner uses

    Oh really What does grin-miner use to mine cuckaroom? :)

    John Tromp
    @tromp
    specifies its targets in cuckoo-miner/src/cuckoo_sys/plugins/CMakeLists.txt
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER

    specifies its targets in cuckoo-miner/src/cuckoo_sys/plugins/CMakeLists.txt

    but I should still run the 'make cuda29' command to mine cuckaroom?

    John Tromp
    @tromp
    no, in grin-miner you run cargo build --release to build the plugins
    and you run grin-miner to run them (i.e. mine)
    cuda29 is for standalone testing of the solver; doesn't use the plugin interface
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER

    Oh well this is going to save me some time thanks.

    make cuda29 is for standalone testing of the solver; doesn't use the plugin interface

    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    mimblewimble/grin#2110 does anyone have fix for this?
    Quentin Le Sceller
    @quentinlesceller
    Usually the fix is to wipe the chain data and resync.
    Weird that it's not working with you
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER

    I wiped chain data with rm '-rf ~/.grin/main/chain_data' rebooted and tried 'grin' again and got the same error. Perhaps I missed a step Maybe we can fixed the bug? I guess its been on the list for a while now.

    Weird that it's not working with you --yes indeed :)

    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    So I removed grin and reinstalled. Now when I start grin I get suck on connecting to peers. I deleted peer data and am still not connecting to any peers. Could this line of code have anything to do with it? It will not go above 90% INFO grin_servers::common::types - DandelionEpoch: next_epoch: is_stem: true (90%), relay: None
    Antioch Peverell
    @antiochp
    no that's entirely unrelated (and the 90% is set in the config file, it won't change)
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    @antiochp Thanks! any ideas? am I the only person with this issue lol
    Antioch Peverell
    @antiochp
    if you are failing to connect to peers then its likely either a firewall issue (not allowing outbound connections for some reason) or possibly you are banned by other peers including the seeds
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    Funny thing is that I had the grin#2110 error listed above so I reinstalled grin using snap. I cannot connect to any peers or download the headers. But I installed grin on another computer in a different location using github last night and I also could not connect to any peers.
    Antioch Peverell
    @antiochp
    can you post the logs here from starting the node up?
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    20200121 12:42:30.043 WARN grin::cmd::server - Starting GRIN in UI mode...
    20200121 12:42:30.043 INFO grin_servers::grin::server - Starting server, genesis block: 40adad0aec27
    20200121 12:42:30.070 INFO grin_servers::grin::server - Starting rest apis at: 127.0.0.1:3413
    20200121 12:42:30.070 WARN grin_api::handlers - Starting HTTP Node APIs server at 127.0.0.1:3413.
    20200121 12:42:30.070 WARN grin_api::handlers - HTTP Node listener started.
    20200121 12:42:30.070 INFO grin_servers::grin::server - Starting dandelion monitor: 127.0.0.1:3413
    20200121 12:42:30.070 WARN grin_servers::grin::server - Grin server started.
    20200121 12:42:30.071 INFO grin_servers::common::types - DandelionEpoch: next_epoch: is_stem: true (90%), relay: None
    20200121 12:42:30.633 INFO grin_store::lmdb - Resized database from 1048576 to 134217728
    20200121 12:52:40.139 INFO grin_servers::common::types - DandelionEpoch: next_epoch: is_stem: true (90%), relay: None
    @antiochp
    Antioch Peverell
    @antiochp
    ahh, can you turn on debug logging via the two lines in the config file -
    #log level for stdout: Error, Warning, Info, Debug, Trace
    stdout_log_level = "Debug"
    
    #log level for file: Error, Warning, Info, Debug, Trace
    file_log_level = "Debug"
    and then grab the logs?
    it should give some more insight into what its doing with the initial seed nodes
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    Where is the config file located?
    I don't recall exactly but we may not create the config file by default any more, it may just use defaults unless the config file exists
    grin server config
    will create a config file in current dir that you can use, if you run grin from that dir
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER

    log level for stdout: Error, Warning, Info, Debug, Trace

    stdout_log_level = "Debug"

    whether to log to a file

    log_to_file = true

    log level for file: Error, Warning, Info, Debug, Trace

    file_log_level = "Debug"
    @antiochp from my grin-server.toml

    20200121 13:23:22.970 WARN grin_servers::grin::server - Grin server started.
    20200121 13:23:22.970 INFO grin_servers::common::types - DandelionEpoch: next_epoch: is_stem: true (90%), relay: None
    20200121 13:23:22.970 DEBUG grin_servers::grin::seed - Retrieving seed nodes from dns mainnet.seed.713.mw
    20200121 13:23:22.985 DEBUG grin_servers::grin::seed - Retrieving seed nodes from dns mainnet.seed.grin.lesceller.com
    20200121 13:23:23.000 DEBUG grin_servers::grin::seed - Retrieving seed nodes from dns mainnet.seed.grin.prokapi.com
    20200121 13:23:23.000 DEBUG grin_servers::grin::seed - Retrieving seed nodes from dns grinseed.yeastplume.org
    20200121 13:23:23.000 DEBUG grin_servers::grin::seed - Retrieved seed addresses: [PeerAddr(V4(47.88.11.190:3414)), PeerAddr(V4(46.4.91.48:3414)), PeerAddr(V4(37.187.124.202:3414)), PeerAddr(V4(157.230.142.11:3414)), PeerAddr(V4(94.130.229.193:3414)), PeerAddr(V4(67.207.70.122:3414)), PeerAddr(V4(159.65.11.32:3414)), PeerAddr(V4(5.135.184.54:3414)), PeerAddr(V4(35.223.12.108:3414)), PeerAddr(V4(35.181.35.93:3414)), PeerAddr(V4(145.239.4.27:3414)), PeerAddr(V4(95.216.163.175:3414)), PeerAddr(V4(35.211.201.137:3414)), PeerAddr(V4(157.230.48.217:3414)), PeerAddr(V4(18.204.166.78:3414)), PeerAddr(V4(5.9.152.75:3414)), PeerAddr(V4(34.207.234.131:3414)), PeerAddr(V4(159.69.37.136:3414)), PeerAddr(V4(109.74.202.16:3414))]
    20200121 13:23:23.001 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:23:23.100 INFO grin_store::lmdb - Resized database from 1048576 to 134217728
    20200121 13:23:23.110 DEBUG grin_p2p::peer - connect: handshaking with Ok(V4(35.181.35.93:3414))
    20200121 13:23:23.199 DEBUG grin_p2p::peer - connect: handshaking with Ok(V4(18.204.166.78:3414))
    20200121 13:23:23.317 DEBUG grin_p2p::peer - connect: handshaking with Ok(V4(47.88.11.190:3414))
    20200121 13:23:25.001 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:23:29.002 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:23:31.326 DEBUG grin_p2p::peer - connect: handshaking with Err(Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }) failed with error: Connection(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })
    20200121 13:23:31.326 DEBUG grin_p2p::peer - Error shutting down conn: Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }
    20200121 13:23:37.003 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:23:53.005 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:24:13.007 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    20200121 13:24:33.010 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:3414, 0 connected (0 most_work). all 0 = 0 healthy + 0 banned + 0 defunct
    Antioch Peverell
    @antiochp
    you get seed addresses via DNS successfully and then try and hand/shake with those seeds but it looks like those connections are unsuccessful
    Connection reset by peer suggests you are banned
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    Why would they ban me? IP problem?
    it says 0 banned?

    code: 104, what can I do about this? Like I said it happened last night on a different install than this morning using different internet.

    Connection reset by peer suggests you are banned

    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    I just tried to connect through a vpn and I am still not getting any connections. Anyway thanks for your help I think I will open an issue. @antiochp
    BLOCKCHAINSMOKER
    @BLOCKCHAINSMOKER
    Update vpn connection worked so there is clearly banning based on my IP address. Unless you have another idea.
    jorgeelmundoso
    @jorgeelmundoso
    i am using grin-miner with cuckaroom_cuda_29.cuckooplugin, but for some reason it does not send any solutions to the mining pool

    logs say

    Jan 21 14:03:00.064 DEBG Mining: Plugin 0 - Device 0 (GeForce GTX 1080 Ti) at Cuckarood29 - Status: OK : Last Graph time: 0.278447551s; Graphs per second: 3.591 - Total Attempts: 39

    is it possible that the plugin is somehow not ok, should it say something along cuckaroom29?

    we should update it to say room
    jorgeelmundoso
    @jorgeelmundoso
    @tromp i am still having the issue that grin-miner does not find any solutions, see mimblewimble/grin-miner#241
    John Tromp
    @tromp
    can you rebuild after removing -DSQUASH_OUTPUT=1 in cuckoo-miner/src/cuckoo_sys/plugins/CMakeLists.txt ?
    then log file should report all cycles it finds