Scp096 node down
Posted over 2 years ago by SCP-096
2023
Monday 16th October 2:00UTC Node was online for most of Sunday and is stable, however unusually slow bitcoin block validation keeps happening for now. So far always synced and is not affectin LND thx to custom extended chain backend healthcheck. Far from ideal tho.
Sunday 15th October 8:40UTC My node is down for several hours and not clear for how long it will stay that way. For some unknown reason my bitcoin stopped syncing or is syncing extremely slowly and strted to lag and LN healthcheck shut node down. Reboots are not helping. Reason not known at this point.
Thursday 10th August 23 12:00UTC Some kind of serious connectivity issue & memory maxing out (never had this particular problem before), had to do hard reset. but lnd was shutdown at that point so node will hopefully be up again in 1-2h
Monday 7th August 23 01:00UTC I have "accidentally" rebooted my node and unfortunately have the same issue as month ago... That is due to bug in bitcoin core 25.0 which should be fixed in 25.1...
https://github.com/bitcoin/bitcoin/issues/27722
Since my reboot already happened, its reindexing from much lower block height and I expect ~2-3hours to be back online.. Apologies..
Saturday 1st July 23 05:59UTC My node is down for the last 6-7 hours and will be down for another approx 4-6hours. I have been doing routine reboots, but for some reason bitcoin havent shut down properly before reboot and as a result it started to synchronize from considerable lower block height. Im synchronizing the same height epoch for the third time, fuck. This never happened to me ever before so I guess it is related to some bug in recent update? Idk. I will have to think of actually ensuring graceful bitcoin shutdown manually before future reboot so I dont have to be re-synchronizing for half a day again..
Monday 29th May 23 21:40UTC Node went down for major upgrade. Could stay down for a few hours. Forwarding was disabled in advance. Edit. Up again since 30th 8:20UTC
Friday 13th Jan 23 09:15utc. Something went wrong during node update/reboot few hours ago. I worked remotely and Im out of town. Most likely wont be able to intervene with server physically until tonight. Sorry for that.
14th Jan 23 07:19utc. Node recovered. Failed/replaced os disk drive.
2022
Lnd crashed 16th Jan 22, recovered day later.
edit: 13th Feb 22, 06:20UTC update to
edit 15th Feb 22 15:05UTC reindexing blockchain is taking significantly longer than expected.
edit 19th Feb 22 9:29UTC My node went back up yesterday around 15-16UTC, so it was well over 5 days offline..
Monday 16th October 2:00UTC Node was online for most of Sunday and is stable, however unusually slow bitcoin block validation keeps happening for now. So far always synced and is not affectin LND thx to custom extended chain backend healthcheck. Far from ideal tho.
Sunday 15th October 8:40UTC My node is down for several hours and not clear for how long it will stay that way. For some unknown reason my bitcoin stopped syncing or is syncing extremely slowly and strted to lag and LN healthcheck shut node down. Reboots are not helping. Reason not known at this point.
Thursday 10th August 23 12:00UTC Some kind of serious connectivity issue & memory maxing out (never had this particular problem before), had to do hard reset. but lnd was shutdown at that point so node will hopefully be up again in 1-2h
Monday 7th August 23 01:00UTC I have "accidentally" rebooted my node and unfortunately have the same issue as month ago... That is due to bug in bitcoin core 25.0 which should be fixed in 25.1...
https://github.com/bitcoin/bitcoin/issues/27722
Since my reboot already happened, its reindexing from much lower block height and I expect ~2-3hours to be back online.. Apologies..
Saturday 1st July 23 05:59UTC My node is down for the last 6-7 hours and will be down for another approx 4-6hours. I have been doing routine reboots, but for some reason bitcoin havent shut down properly before reboot and as a result it started to synchronize from considerable lower block height. Im synchronizing the same height epoch for the third time, fuck. This never happened to me ever before so I guess it is related to some bug in recent update? Idk. I will have to think of actually ensuring graceful bitcoin shutdown manually before future reboot so I dont have to be re-synchronizing for half a day again..
Monday 29th May 23 21:40UTC Node went down for major upgrade. Could stay down for a few hours. Forwarding was disabled in advance. Edit. Up again since 30th 8:20UTC
Friday 13th Jan 23 09:15utc. Something went wrong during node update/reboot few hours ago. I worked remotely and Im out of town. Most likely wont be able to intervene with server physically until tonight. Sorry for that.
14th Jan 23 07:19utc. Node recovered. Failed/replaced os disk drive.
2022
Lnd crashed 16th Jan 22, recovered day later.
edit: 13th Feb 22, 06:20UTC update to
edit 15th Feb 22 15:05UTC reindexing blockchain is taking significantly longer than expected.
edit 19th Feb 22 9:29UTC My node went back up yesterday around 15-16UTC, so it was well over 5 days offline..
5 Comments
HODLmeTight wrote over 2 years ago
Ping here on Telegram if you need help, good luck!
SCP-096 wrote over 2 years ago
It seems that my node is up again, first forwards happened ftw. I had to flash new os image and reinstall few things as I couldnt figure other solution, I will study logs later.
Plus there may be some kind of networking issue (during restarting LND) that I am not sure is completely away, but otherwise all seem ok.
The worst part is how late I figured my node is down. I had ping notifications to my router, but not (expecting) for spontaneously crashed LND, so I will upgrade notification process asap. Being more than a day offline really suck, it will take long time to repair reputation now.
I am very sorry for this to all my peers, however I would also like to say that atm I dont have ambitions to be professional grade operator. This is mostly my hobby and attempt to help community. I am trying to act responsibly, but dont expect the kind of 'commercial level' guarantees from me. I am learning and will try to prevent such excess in the future, but cant give 100% promise..
Plus there may be some kind of networking issue (during restarting LND) that I am not sure is completely away, but otherwise all seem ok.
The worst part is how late I figured my node is down. I had ping notifications to my router, but not (expecting) for spontaneously crashed LND, so I will upgrade notification process asap. Being more than a day offline really suck, it will take long time to repair reputation now.
I am very sorry for this to all my peers, however I would also like to say that atm I dont have ambitions to be professional grade operator. This is mostly my hobby and attempt to help community. I am trying to act responsibly, but dont expect the kind of 'commercial level' guarantees from me. I am learning and will try to prevent such excess in the future, but cant give 100% promise..
μpleb wrote about 2 years ago
My node went down today. Was unfortunate that I was away. Sorry, the force close would be my fault
Yankee Hotel Foxtrot wrote about 2 years ago
Bummer!! Unfortunately our channel force closed :(
Happy to reopen once you get things worked out, you've been a great peer!
Happy to reopen once you get things worked out, you've been a great peer!
needleInTheHay wrote about 2 years ago
Hey once you come back strong, I will initiate the channel to you
Please login to post comments.
Latest news