When asking a question of Tom AI, I get the following message: "Unable to reach SparkBox chat service: getaddrinfo EAIAGAIN api.tomsparkbox.com"
6 replies
Chris wrote:
Thanks for reporting this. I checked the public chat address and it is responding now, so this points to a DNS lookup problem from the box at that moment, not your licence. Please run sudo sparkbox doctor on the box, then reply with only the Container Egress result and the EAIAGAIN code if it appears again. Please do not post your licence key.
Zeotrope wrote:
[Container Egress] [OK] Apps can reach webhook.tomsparkbox.com over sbproxy (their real network) [OK] Docker's default bridge can reach tomsparkbox.com (dashboard Update button)
Chris wrote:
Those are both clean results, thank you. They show that the app network and Docker’s default bridge can currently reach their test addresses, so there is no general container-egress failure showing there. Please try Tom AI again when convenient. If the EAIAGAIN error returns, reply with the time it happened and the full error text, but no licence key. That will let us distinguish a one-time DNS lookup failure from a repeatable chat issue.
Zeotrope wrote:
Message appeared at 8.51am: Unable to reach SparkBox chat service: getaddrinfo EAIAGAIN api.tomsparkbox.com
Chris wrote:
I’ve logged this and our team is investigating the repeated lookup failure. The public chat address is answering now, and your clean Container Egress result means that broader test is not catching this dashboard-specific request. Please run sudo sparkbox upgrade — it updates SparkBox itself, unlike update, which only refreshes app images — then try Tom AI once more. If it recurs, reply with the time and exact error again, but no licence key.
Chris wrote:
SparkBox v1.6.661 is now available. Tom AI now retries brief DNS lookup failures such as the EAIAGAIN error you reported. Update SparkBox and try Tom AI again. This helps temporary failures; if the error persists, please reply with its time and exact text, without your licence key.