--- Log opened Thu May 11 00:00:58 2023 00:11 -!- Zenton [~user@user/zenton] has quit [Ping timeout: 264 seconds] 02:02 -!- berndj [~berndj@197.189.254.139] has quit [Quit: ZNC - http://znc.in] 02:02 -!- berndj [~berndj@197.189.254.139] has joined #c-lightning 03:00 -!- Zenton [~user@user/zenton] has joined #c-lightning 03:35 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds] 03:54 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 03:56 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning 03:58 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 04:01 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:23 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 04:26 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:29 -!- opsec_x122 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:29 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 04:47 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:48 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 04:50 -!- opsec_x12 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:51 -!- opsec_x122 [~opsec_x12@44.25.143.46] has quit [Ping timeout: 240 seconds] 04:59 -!- opsec_x122 [~opsec_x12@44.25.143.46] has joined #c-lightning 04:59 -!- opsec_x12 [~opsec_x12@44.25.143.46] has quit [Remote host closed the connection] 05:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:34 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 05:56 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 06:06 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 06:40 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has joined #c-lightning 06:41 < blue_line> hi, anybody there? 07:00 < vincenzopalazzo> blue_line: pong 07:10 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has quit [Remote host closed the connection] 07:10 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has joined #c-lightning 07:43 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has quit [Remote host closed the connection] 07:44 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has joined #c-lightning 08:19 -!- blue_line [~blue_line@195.181.160.173.adsl.inet-telecom.org] has quit [Remote host closed the connection] 09:46 -!- ctrlbreak [~ctrlbreak@fctnnbsc51w-159-2-215-98.dhcp-dynamic.fibreop.nb.bellaliant.net] has joined #c-lightning 09:47 < ctrlbreak> Hallo? Is IRC still a thing for this project? 09:47 < vincenzopalazzo> ctrlbreak: yep it is 09:48 < ctrlbreak> I'm trying to bring my oldest node to a version more current... and I've run into this unexpectedly, and was wondering if someone could point me in the right direction or give me the scoop! 09:48 < ctrlbreak> 2023-05-11T16:44:17.805Z INFO lightningd: Refusing to irreversibly upgrade db from version 199 to 216 in non-final version v23.02.2-modded (use --database-upgrade=true to override) 09:48 < vincenzopalazzo> yeah 09:48 < vincenzopalazzo> you need just to put the lightningd .. --database-upgrade=true 09:49 < vincenzopalazzo> when you are not running a not tagged version we make this explicit because otherwise you can not going back 09:49 < vincenzopalazzo> so I assume that you are running the master 09:49 < vincenzopalazzo> or some version before v23.* right? 09:51 < ctrlbreak> Actually tried to go from 0.12 something to 'git checkout v23.02.2'... 09:51 < ctrlbreak> just realized I missed 22.11.1 09:52 < ctrlbreak> Last successful start was on 0.12.1 09:54 < vincenzopalazzo> I think the v23.02.2 should contain a patch for the version check 09:54 < ctrlbreak> Should I just try to checkout and compile 22.11.1 as an intermediate... or is it "safe" to jump straight from 0.12.1 to say, 23.05 at this point? 09:55 < vincenzopalazzo> the version 12 is just one version bheaind 23 so it i s save also checkout the last one 09:55 < vincenzopalazzo> ah maybe ti is better 09:56 < ctrlbreak> Alright. I'll checkout 23.05, compile and try to run it. I'm assuming if it's *not* safe to load it with a version 199 db, it'll safely let me know. 09:57 < vincenzopalazzo> no the meaning of the --database-upgrade=true is to do not compile the master by mistake and so not run the old tagged version 09:58 < vincenzopalazzo> if you find something with out tagged release it is a bug, and the good place to report it is an issue 09:59 < ctrlbreak> Okay... I don't quite follow. I was at tagged release 0.12.1.... the I checked out and compiled tagged release 23.02.2.... and his that upgrade db warning. 10:01 < ctrlbreak> I guess what I'm asking right now, is can I check out tagged release v23.05 and will it safely upgrade my 0.12.1 db (version 199) 10:04 < ctrlbreak> ... well... that answers that: 2023-05-11T17:03:53.252Z INFO lightningd: Refusing to irreversibly upgrade db from version 199 to 219 in non-final version v23.05-modded (use --database-upgrade=true to override) 10:09 < ctrlbreak> Can anyone else advise here? Is it because I'm compiled '-modded' 10:18 < vincenzopalazzo> "Can anyone else advise here? Is..." <- right 10:18 < vincenzopalazzo> "I guess what I'm asking right..." <- well till now we did not have any issue 10:19 < vincenzopalazzo> maybe you want upgrade to the v23.02 that it is not the one released today 10:19 < ctrlbreak> I apologise. I think this is just a miscommunication of sorts as I don't understand what you are trying to say. 10:21 < ctrlbreak> Are you confirming that this warning is indeed because I'm compiled modded? Is that what you mean by " <- right" 10:27 < ctrlbreak> I really do not want to leave this node down any longer than I absolutely have to. I also don't want to completely break it. I have VM image backups, but you obviously realize the danger and risk with restoring chainstates. 10:29 < ctrlbreak> Can someone _please_ just advise on whether or not it's safe for me to leverage '--database-upgrade=true' if I've compiled tagged release v23.05 and it's attempting to load a db of version 199 from tagged release 0.12.1? 10:30 < vincenzopalazzo> ctrlbreak: https://lightning.readthedocs.io/lightningd-config.5.html?highlight=database-upgrade#general-options 10:33 < ctrlbreak> Ohkay... I understand the intention of the directive. Again, is the reason I'm getting this warning because I'm compiled modded? 10:33 < vincenzopalazzo> it is safe? Most of the time, yes, if you find an unknown bug, this was an unlucky upgrade. 10:33 < vincenzopalazzo> ctrlbreak: yes I think you had some dirty build directory or we have some bug somewhere 10:34 < vincenzopalazzo> that change our version name with the -modded 10:35 < ctrlbreak> : Thank you! I'm checking my notes and I believe the reason I'm still compiling modded is because I applied a patch back in 2018 to be able to export my hsm_secrets... 10:35 < ctrlbreak> (as part of a failsafe backup at the time) 10:36 < ctrlbreak> I'm really out of time for this today, so I'm just going to let it perform the db upgrade at 23.05. 10:39 < ctrlbreak> ... welp... and now I'm good and puckered "2023-05-11T17:38:27.266Z **BROKEN** lightningd: Forced database repair of psbt" 10:39 < ctrlbreak> I choose to believe this is a good thing. 10:39 < ctrlbreak> lol 10:40 -!- Zenton [~user@user/zenton] has quit [Read error: Connection reset by peer] 10:45 -!- ctrlbreak is now known as ctrlbreak_afk 10:52 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds] 10:52 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 10:59 < vincenzopalazzo> can you put an issue? 10:59 < vincenzopalazzo> I guess this is a regression 10:59 < vincenzopalazzo> but the db should rollback to the previous state 10:59 < vincenzopalazzo> so you are sane 10:59 < vincenzopalazzo> ps: I also suggested to upgrade to the v23.02 not the last one that was release today 11:19 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 13:28 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 14:44 -!- Zenton [~user@user/zenton] has joined #c-lightning 15:28 < ctrlbreak_afk> Yeah... I missed that about the recommendation to go 23.02. How screwed am I? 15:28 -!- ctrlbreak_afk is now known as ctrlbreak 15:29 < vincenzopalazzo> ctrlbreak_afk: not much I think the database if there is any error will not commit the upgrade (thanks SQL) 15:29 < vincenzopalazzo> so you should be fine to run the 23.02? 15:29 < vincenzopalazzo> but please report the previous crash :) so i can patch it 15:52 < ctrlbreak> "I missed that about the recommendation to go 23.02" I'm not on 23.02. I'm on 23.05 15:52 -!- ctrlbreak is now known as ctrlbreak_afk 15:56 < vincenzopalazzo> ctrlbreak: you was able to start the node? 15:56 < vincenzopalazzo> ah wait you are using another account :/ 15:56 < vincenzopalazzo> hahaha I already answer this 17:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:32 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 17:36 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning 18:07 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur] 23:34 -!- leohoo_sdu[m] [~leohoosdu@2001:470:69fc:105::3:56ef] has joined #c-lightning 23:34 -!- leohoo_sdu[m] [~leohoosdu@2001:470:69fc:105::3:56ef] has left #c-lightning [] 23:59 -!- early [~early@static.38.6.217.95.clients.your-server.de] has quit [Quit: Leaving] --- Log closed Fri May 12 00:00:59 2023