--- Day changed Sat Apr 21 2018 00:21 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 02:26 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 248 seconds] 03:07 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 264 seconds] 03:15 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 04:01 < AgoraRelay> [agora-irc/AlexCato] @raedah : sounds like you maybe forgot to "source jmvenv/bin/active" ? 04:02 < waxwing> s/active/activate/ but yeah that's a possible reason 05:14 -!- lnostdal [~lnostdal@85.118.83.96] has joined #joinmarket 05:50 -!- lnostdal [~lnostdal@85.118.83.96] has quit [Ping timeout: 256 seconds] 07:24 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket 07:29 -!- AgoraRelay [~jmrelayfn@p5DE4A291.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 07:49 -!- AgoraRelay [~jmrelayfn@p548663EF.dip0.t-ipconnect.de] has joined #joinmarket 07:55 -!- newguy [7a798b5d@gateway/web/freenode/ip.122.121.139.93] has joined #joinmarket 07:58 < newguy> hello, I'm getting 'taker not continuing after receipt of orderbook' after running the tumbler script. I tried using the --restart, but i keep getting that message. Is it an error? 08:05 < waxwing> newguy, hmm difficult to say. it happens for a few different reasons iirc. is there any further message after that? i think one case is where it has to wait for more confirmations. if it's not that it might be something to do with the size of the amount being too small or too large. 08:05 < waxwing> i'll check the code to remember the exact set of conditions 08:06 < waxwing> newguy, if you check the file TUMBLE.schedule you should be able to see how many of the transactions have already gone through. can you tell us? (or perhaps just, whether 1 or more txs have already gone through, or none have) 08:06 < newguy> Under TUMBLE.log it says restarting with this schedule, then lists the schedule. 08:06 < newguy> 2 went through iirc 08:07 < newguy> they were deleted when i ran with --restart? 08:10 < waxwing> newguy, yes that's correct, although i agree with your implicit comment, that that's slightly annoying .. 08:10 < waxwing> hmm so in the TUMBLE.log, which does not wipe iirc between runs, you might be able to find some log messages when it happened 08:11 < waxwing> search for the 'not continuing..' message there 08:12 < newguy> no nothing in the log about not continuing 08:13 < newguy> two txs went through. says 'completed successfully this entry' for those. then the waiting period followed by RESTARTING. it lists the schedule and thats it 08:13 < newguy> next line is TUMBLE RESTARTING when i manually ran with --restart 08:14 < newguy> i succfessully did a tumble about 24hrs ago. im doing a much larger amount this time though so maybe rrelated to that as you said 08:15 < waxwing> ok. are there no other messages at all (such as messages about commitment utxos) when you restarted? 08:15 < waxwing> i'd suggest setting logging to DEBUG in joinmarket.cfg if you haven't done so already 08:15 < waxwing> [LOGGING] 08:15 < waxwing> console_log_level=DEBUG 08:16 < waxwing> put that ^ in the file if you don't have it yet 08:16 < waxwing> large amount is certainly a possibility, in particular if there aren't very many makers, because the default settings are joins between 5 and 7 counterparties. 08:17 < waxwing> you can try e.g. -N 3 0 ; that would be exactly 3 counterparties each time. second number is standard deviation of the number to be chosen each time. 08:17 < waxwing> it's also possible to edit the schedule by hand but best not really. 08:20 < waxwing> yes, hmm, i've just noticed that if it fails for that specific reason - there are insufficient counterparties that match your requirement, then the only error messages that are shown are specifically DEBUG type. 08:21 < waxwing> basically it says something like "ERROR Insufficient liquidity .." etc etc in that case newguy 08:21 < newguy> well i notcied in the joinmarket.cfg file it said that all the stuff in the logs folder is already DEBUG, so im looking through those to find the right one 08:22 < waxwing> yes that's true, good point, forgot :) just do a ls -lart or whatever to find the latest log file, that'll be the right one :) 08:22 < waxwing> the latest J5.. of course 08:23 < waxwing> yeah that ought to be promoted to an warning or error level message since it is actually a failure of the protocol, if not of the software. 08:28 < newguy> you were right. it errored due to not enough liquidity in orderbook 08:28 < newguy> is there a way to view the orderbook? 08:29 < waxwing> newguy, well you can either do it locally (best) or go to https://joinmarket.me/ob/ 08:29 < newguy> if in the logs that message "ABORT:Could not find orders to complete transaction" was changed to INFO instead of DEBUG that might be useful 08:29 < waxwing> locally means running the obwatcher.py script which is in the obwatch directory 08:30 < waxwing> newguy, yeah i just said the same thing (warning/error) above :) i'll do that now, no reason not to 08:33 -!- GitHub169 [GitHub169@gateway/service/github.com/x-ssejjgtywzrlugsz] has joined #joinmarket 08:33 < GitHub169> [joinmarket-clientserver] AdamISZ pushed 1 new commit to master: https://git.io/vpYo6 08:33 < GitHub169> joinmarket-clientserver/master 00d747d AdamISZ: promote insufficient liquidity error message to warning 08:33 -!- GitHub169 [GitHub169@gateway/service/github.com/x-ssejjgtywzrlugsz] has left #joinmarket [] 08:34 < waxwing> doh that's not exactly correct (missed taker info callback). will fix. 08:37 -!- GitHub103 [GitHub103@gateway/service/github.com/x-qoncpmvreaepiydo] has joined #joinmarket 08:37 < GitHub103> [joinmarket-clientserver] AdamISZ force-pushed master from 00d747d to 7860fe1: https://git.io/v5bgz 08:37 < GitHub103> joinmarket-clientserver/master 7860fe1 AdamISZ: promote insufficient liquidity error message to warning... 08:37 -!- GitHub103 [GitHub103@gateway/service/github.com/x-qoncpmvreaepiydo] has left #joinmarket [] 08:42 < newguy> if I run the yg-pe script should I be able to see my orders in the orderbook? 09:07 < newguy> thanks for the help 09:08 -!- newguy [7a798b5d@gateway/web/freenode/ip.122.121.139.93] has quit [Quit: Page closed] 09:08 < waxwing> newguy, yes, although the public site i mentioned is not always accurate. run it locally for better results, or directly connect to the IRC channels. 09:54 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 240 seconds] 12:33 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has joined #joinmarket 12:36 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has quit [Max SendQ exceeded] 12:44 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has joined #joinmarket 14:34 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has quit [Ping timeout: 264 seconds] 14:48 -!- deafboy [quasselcor@cicolina.org] has quit [Quit: No Ping reply in 180 seconds.] 14:50 -!- MaxSan [~user@86.105.9.67] has quit [Read error: Connection reset by peer] 14:51 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket 15:36 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 276 seconds] 16:22 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 17:21 -!- core [~core@unaffiliated/core] has joined #joinmarket 20:14 -!- AgoraRelay [~jmrelayfn@p548663EF.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds] 20:25 -!- AgoraRelay [~jmrelayfn@p54866D1C.dip0.t-ipconnect.de] has joined #joinmarket 22:25 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 264 seconds] 22:56 -!- Giszmo [~leo@ip-181-237-219-201.nextelmovil.cl] has joined #joinmarket 23:17 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 23:17 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #joinmarket