I’ve justing installed openBalena for testing and I’ve even joined a balenaOS device previously used on my balenaCloud subscription and deployed a new application. But now I’m experiencing some strange problems…
After some time my balena CLI stops to work and I get the following error when I try to log again:
Logging in to fleet.timelapse.in FetchError: request to https://api.fleet.timelapse.in/login_ failed, reason: read ECONNRESET at ClientRequest.<anonymous> (/usr/lib/node_modules/balena-cli/node_modules/node-fetch/index.js:133:11) at ClientRequest.emit (events.js:189:13) at ClientRequest.EventEmitter.emit (domain.js:441:20) at TLSSocket.socketErrorListener (_http_client.js:392:9) at TLSSocket.emit (events.js:189:13) at TLSSocket.EventEmitter.emit (domain.js:441:20) at emitErrorNT (internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at process._tickCallback (internal/process/next_tick.js:63:19)
Here are some logs from the HAProxy container:
[NOTICE] 119/171236 (9) : New worker #1 (11) forked [WARNING] 119/171236 (11) : Server backend_api/resin_api_1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. [ALERT] 119/171236 (11) : backend 'backend_api' has no server available! [WARNING] 119/171240 (11) : Server backend_api/resin_api_1 is UP, reason: Layer4 check passed, check duration: 0ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue. [ALERT] 119/173605 (9) : Current worker #1 (11) exited with code 139 (Segmentation fault) [ALERT] 119/173605 (9) : exit-on-failure: killing every workers with SIGTERM [WARNING] 119/173605 (9) : All workers exited. Exiting... (139)
Issuing a “compose stop” followed by a “compose start” does repair the toy, but only for some minutes.
Any suggestion for further troubleshooting?