Every now and then the damus relay just dies and stops accepting posts. Through much debugging, expert analysis, tapping into my years of experience in maintaining software and getting to the bottom of complex computer science issues, my final solution is to just kill the process every hour. Hit that follow button for more state of the art #devops techniques.

Reply to this note

Please Login to reply.

Discussion

True and tried method among #devops , can confirm! 🐶🐾😂🫂

The good old turn it off and back on again

Have you tried using a hammer?

Iirc, you’re using strfry?

yes, when I have my spam policies enabled something eventually kills writes … maybe backpressure or bugs in the ratelimiting policy? Not sure.

Found the problem.

It’s not written in Rust, errrr Crab. 🙃

When it works it works! Nothing wrong with that!

非常棒的解决方案。可以每小时将中继取出,放水里冷却一分钟,效果会更好👍#DevOps

Will try this

Awesome 👏

带电放冷水中,可能效果会更好~(我乱说的😂)

lightning:cndx@btcdv.com 🐇ᥬ[🐕]᭄🌿

When I can't figure something out, I just turn it off, unplug the electricity for 2 weeks and then I'll try it again. #likeapro

„Ein Reboot tut immer gut“

how we say in German

I’d say regular reboots are one of the main success facors of #heroku.

I know of a multi-million dollar Enterprise software company who did exactly that, and shipped a maintenance release which only restarted the process regularly under the hood

Of course you couldn't find any of that in the release notes.

Ah the all powerful “unplug it and plug it back in” method. Genius.

I’ve been running roosofts relay for about two months with no hiccups. It doesn’t store any data yet and is very basic but for a high availability and battle tested run time that easily scales, elixir is the way to go. It could easily be extended and the code is very clean and well documented and test driven.

so, turning it off and on again

Be strong be proud of your work 📝

My PC’s Xorg logfiles never seem to prune right so I added an hourly ‘echo "" > logfile’ to my crontab

https://nostr.build/i/nostr.build_3e97670028c70c4825be6e13c43813942e6701b6e99536c6bc70808e3a9aa490.webp

Where there's a #[1] there's a way. Ingenious stuff.

Have you tried hitting it with a hammer?

I love it, sometimes the best solution is the simplest

Hahahaha