pull down to refresh

106 sats \ 8 replies \ @WeAreAllSatoshi 1 Dec \ on: Stacker Saloon
Sigh, my bot stopped working. I’ll have to check logs again
write
preview
100 sats \ 1 reply \ @jasonb 1 Dec
Do you mind sharing where or how you leaned to make bots?
reply
50 sats \ 0 replies \ @WeAreAllSatoshi 1 Dec
I’m a Software engineer by trade, so lots of experience in general. I also contributed a fair amount to stacker news itself last year, so i was pretty familiar with the API
reply
100 sats \ 5 replies \ @ek 1 Dec
235 days without an incident involving @hn 👀.
Let me know what the problem was once you found it.
reply
51 sats \ 4 replies \ @WeAreAllSatoshi 1 Dec
Will do. Probably another unnecessary field in my API calls that changed or was removed
Edit: or maybe my server died. Who knows lol
reply
142 sats \ 3 replies \ @WeAreAllSatoshi 1 Dec
Gah, issue calling braiins' API
Error: getaddrinfo EAI_AGAIN pool.braiins.com
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) {
     errno: -3001,
     code: 'EAI_AGAIN',
     syscall: 'getaddrinfo',
     hostname: 'pool.braiins.com'
}
Edit: seems to be a DNS issue on my server
reply
21 sats \ 2 replies \ @WeAreAllSatoshi 1 Dec
No idea why this randomly stopped working, but should be back in business now
reply
100 sats \ 1 reply \ @ek 1 Dec
does that mean your miner also stopped working?
reply
33 sats \ 0 replies \ @WeAreAllSatoshi 1 Dec
It was still sending shares to the pool, which is interesting. Maybe there’s some DNS resolution caching in the miner process
Also only one of my miners is connected to this server, so only one would have been impacted, fortunately
reply