1st Slave produces an Error on start up #40
Comments
Random! |
|
2025-02-27T23:47:30Z FTL Sync failed error="sync configs: http://10.0.0.101/api/config: Patch "http://10.0.0.101/api/config\": dial tcp 10.0.0.101:80: connect: connection refused" changed the order.. its the first Slave that's gets the error! |
rockrabbit
changed the title
|
pi@200:~/nebula_beta $ docker logs 28caabf7ff70 tried another.. first slave gets the error and shuts down Nebula |
|
It seems like the teleport import and/or config patch sometimes require a restart and that will render the API unresponsive temporarily. pi-hole/FTL#2301 We will have to figure out a way to "healthcheck" the pihole or (hopefully not) just simply wait a bit before making consecutive requests. |
|
use /Auth |
|
@rockrabbit This should be fixed now: #51 I went with a naive retry solution, it will attempt to retry at most X times with a delay in between. I think this should be good enough, but might want to implement a real health check in the future. |
|
2025-03-02T11:43:22Z INF Starting nebula-sync v0.4.1 Love it! Appears to be fixed! Thank you! |
this is an odd one as this error doesn't always show up on cron sync but its the only one.
It's a Pi 4
ERR Sync failed error="sync configs: http://10.0.0.200/api/config: Patch "http://10.0.0.200/api/config\": dial tcp 10.0.0.200:80: connect: connection refused"
Does not happen all the time, just here and there... any ideas?
The text was updated successfully, but these errors were encountered: