Summary first
I wanted to put out a current status update on things.
@LUVshares and @Hivebits (HBIT) are both down. That means the @Wusang game is down too.
- I currently don't know what the problem is.
- I currently don't have a solution going forward.
When LUV was first made (almost three years ago now!), I drew this gif to illustrate my attempts to get it running. This is where I am again.
How we got here
The LUVbot (and HBIT/Wusang bot) have been running great for months. Then, on October 20, for some reason at roughly the same time, they didn't. The screenshots below show the log files in the LUV/HBIT Discord server's log channels.
At first, I wasn't particularly concerned. This type of thing has happened before. Usually, it has been an API node having a glitch. After switching to a different node, or just waiting, the problem has been resolved. This time, it did not resolve. Hmm.
I asked on the Hive Discord and got a couple of replies.
- API node? I said I'd tried three with the same result.
- If same result from all three, likely is on my end.
Hmm.
On my end? I hadn't done anything in weeks, maybe months. To change things on my end, I must SSH in (that is, connect to the virtual server and do whatever), and I hadn't done that in some time. Looking at my GitHub history, the two main files involved hadn't been altered in six months and one month.
The only other "end" is the virtual server, the VPS. Was there a change there? Did the VPS get an update or pick up something somewhere that's throwing a wrench in the engine?
This seems to be where the issue is.
The traceback points to a sock.connect(sa) issue.
The help at https://stackoverflow.com/questions/67159193/stuck-in-process-sock-connectsa-or-making-connections seemed closest to my issue. A conflict with ipv6 and ipv4 may be the problem. That sounded plausible, though I'm not sure why it would have simply appeared suddenly.
I tried unsuccessfully to follow their steps.
So, I'm stuck.
Going forward
I'm likely going to simply wipe the VPS and start over from scratch.
My, ahem, "coding" skills are limited. My experience with coding has been to eat the low hanging fruit first, then grasp at the apple just beyond my fingertips, to jump and stretch and maybe latch onto it, then try again with an apple just a bit higher. Wiping the VPS and starting over would be chopping down the apple tree altogether and replanting...a big step and one that I may not be able to do.
That's a drastic step, but, if it's totally broken and there's no apparent hope, then why not?
So, what I'm saying is, the future is uncertain for LUV and HBIT/Wusang.
I'd like to get LUV going because the goal is to spread love on the Hive chain and I just think that's a good thing. And regarding HBIT, I made a commitment that every single HBIT is backed by the guarantee that somebody "mined" it with conscience effort. Currently, that can't happen and won't happen unless it's fixed. Until that happens, the HBIT supply is effectively frozen.
Likely I won't be able to do anything for a while. Company is coming tomorrow so there's business to attend to. Maybe an epiphany will occur to me along the way.
You ask, "What's Hive?" Watch the animation I made: The Hive Story Animation and you'll learn about this Web3 chain. The top benefits of the Hive blockchain: (1) no ONE person/group runs it, (2) YOU own and control your content, and (3) YOU earn the rewards that your content generates. Learn more or consider using my referral link to get your free account here and I'll support you as you begin. Alternately, you can see other sign-up options here. All my links: https://linktr.ee/crrdlx.