--- Log opened Tue Apr 21 00:00:58 2020
01:02 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has joined #joinmarket
01:16 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
01:17 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has joined #joinmarket
01:26 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
01:27 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has joined #joinmarket
01:53 < lessismore> Hey, today the JM quit with "bad command  f". My last tumblers were fine. Are there any information regarding this "bad command f"?
01:56 < waxwing> this is the Qt app right?
01:57 < waxwing> did the Qt app crash with that message appearing on the console? or what exactly happened?
02:14 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
02:15 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has joined #joinmarket
02:17 < lessismore> Thanks waxwing! No the app did not crash. Message in the bottom status bar was something like "Commitments sourced ok". The message in log window was "DEBUG: Bad command f". Thats it. 
02:19 < waxwing> lessismore, ah ok. i've seen that before, and in theory it should not be something you need to care about. iirc it just means someone sent your bot a message on irc using a command which is not valid for joinmarket.
02:19 < waxwing> are you saying that immediately after that line, the tumbler process stopped and didn't continue?
02:20 < lessismore> there was no more activity for approx. 60-90mins after that message.
02:20 < waxwing> and there's no "traceback" (long list of function calls) with an error, i.e. it didn't crash. but it just stopped?
02:20 < lessismore> no crash, no further log entries.
02:20 < waxwing> and that is not expected according to the transaction schedule?
02:20 < lessismore> just sitting there and idling or doing nothing.
02:21 < waxwing> well, if it happened immediately after 'commitments sourced ok', that does sound wrong. but 60-90 minute wait doesn't say much on its own; it depends on the wait times in the schedule.
02:22 < waxwing> the schedule is in logs/TUMBLE.schedule, the wait times are shown in minutes.
02:23 < lessismore> usually the wait time is around 45mins (45.28minutes according to the log)
02:23 < waxwing> if indeed it has stopped and we don't know why, you can restart: you restart the Qt app, then load the wallet, then in multijoin tab click 'load schedule' and load the ~/.joinmarket/logs/TUMBLE.schedule file and it will automatically recognize an incomplete tumbler run and ask you if you want to restart it.
02:24 < waxwing> is there definitely nothing else in the J5**.log after 'bad command f'. or before it that might help? i feel sure i've occasionally seen that and it didn't have any effect (and i have no idea why it would, if it's what i think)
02:24 < waxwing> sorry not "restart" as in start from the beginning but rather "continue" - it will continue the schedule from where it left off.
02:25 < lessismore> i will send you the log entries per pm.
02:27 < waxwing> thanks
02:48 -!- lessismore is now known as lessismore_butaw
03:01 -!- lessismore_butaw is now known as lessismore
03:08 -!- lessismore is now known as lessismore_butaw
03:25 -!- lessismore_butaw is now known as lessismore
03:38 -!- lessismore is now known as lessismore_butaw
03:42 -!- lessismore_butaw is now known as lessismore
04:13 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds]
04:24 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket
04:32 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Ping timeout: 240 seconds]
04:35 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Read error: Connection reset by peer]
04:35 -!- Zenton [~user@unaffiliated/vicenteh] has joined #joinmarket
04:55 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket
05:37 -!- lessismore is now known as lessismore_butaw
06:24 -!- lessismore_butaw is now known as lessismore
06:31 -!- kristapsk_ is now known as kristapsk
06:35 -!- lessismore is now known as lessismore_butaw
07:02 -!- lessismore_butaw is now known as lessismore
07:05 -!- openoms [~quassel@195.140.215.182] has quit [Quit: No Ping reply in 180 seconds.]
07:08 -!- openoms [~quassel@195.140.215.182] has joined #joinmarket
08:52 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket
08:53 -!- lessismore [~lessismor@p200300FDC701A39DF1C1322DFAE5A7DB.dip0.t-ipconnect.de] has quit [Quit: Textual IRC Client: www.textualapp.com]
09:11 -!- MaxSan [~four@185.156.175.171] has quit [Ping timeout: 260 seconds]
09:45 -!- MemeFarmer [sid414248@gateway/web/irccloud.com/x-uzgrgamceuhuyihl] has quit [Ping timeout: 246 seconds]
09:47 -!- MemeFarmer [sid414248@gateway/web/irccloud.com/x-wzhhdcyphgodroyt] has joined #joinmarket
10:43 < coconutanna> a bitcoin node being shut down causes a huge unhandled exception in the yg and then it returns 0 anyway. there are multiple things wrong with this.
11:12 < kristapsk> coconutanna, https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/442
11:23 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has quit [Remote host closed the connection]
11:23 -!- sosthene [~sosthene@gateway/tor-sasl/sosthene] has joined #joinmarket
12:51 < coconutanna> kristapsk: cheers. the error looks a little different here but good to know it's a known issue.
16:41 -!- M1 [~Michail@michail.com] has quit [Read error: Connection reset by peer]
16:45 -!- M1 [~Michail@michail.com] has joined #joinmarket
17:04 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
17:12 -!- belcher_ [~user@unaffiliated/belcher] has joined #joinmarket
17:50 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.8]
17:57 -!- DSRelBot [~DSRelBot@p5DE4A299.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
17:58 -!- HackRelay [~jmrelayha@p5DE4A299.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
18:11 -!- DSRelBot [~DSRelBot@p5DE4A5CB.dip0.t-ipconnect.de] has joined #joinmarket
18:13 -!- HackRelay [~jmrelayha@p5DE4A5CB.dip0.t-ipconnect.de] has joined #joinmarket
23:08 -!- opal [~wowaname@volatile/founder/wowaname] has quit [Remote host closed the connection]
23:09 -!- opal [~wowaname@volatile/founder/wowaname] has joined #joinmarket
--- Log closed Wed Apr 22 00:01:00 2020