Cant get Balena local push to work

Project help
,
1

Hi All,

Im trying to push my app to a local pi5 and pi3 (both with local mode on) but it keeps getting stuck. anyone has an idea how to throubleshoot?
I’ve updated the Balena CLI, NPM, NodeJS to the latest and the supervisor version 15.2.0 for the pi5

The debug gives me the following (i’ve aborted the task after 30mins):

[debug] new argv=[C:\Program Files\balena-cli\client\bin\node.exe,C:\Program Files\balena-cli\client\bin\run,push,192.168.1.91,-c] length=5
[debug] Deprecation check: 2.78905 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[Debug]   Using build source directory: . 
[Debug]   Pushing to local device: 192.168.1.91
[Debug]   Checking we can access device
[Debug]   Sending request to http://192.168.1.91:48484/ping
[Debug]   Checking device supervisor version: 15.2.0
[Info]    Starting build on device 192.168.1.91
[Debug]   Loading project...
[Debug]   Resolving project...
[Debug]   docker-compose.yml file found at "."
[debug] Event tracking error: Timeout awaiting 'response' for 0ms
[Debug]   Creating project...
[Debug]   Tarring all non-ignored files...
[Debug]   Tarring complete in 117 ms
[Debug]   Fetching device information...
[Debug]   Sending request to http://192.168.1.91:48484/v2/local/device-info
[Debug]   Found build tasks:
[Debug]       homebridge: build [.]
[Debug]   Resolving services with [raspberrypi5|aarch64]
[Debug]   Found project types:
[Debug]       homebridge: Dockerfile.template
[Debug]   Probing remote daemon for cache images
[Debug]   Using 2 on-device images for cache...
[Debug]   Starting builds...
Task aborted on SIGINT signal

SIGINTError: Task aborted on SIGINT signal
    at process.sigintHandler (C:\Program Files\balena-cli\client\build\utils\helpers.js:276:20)
    at Object.onceWrapper (node:events:631:28)
    at process.emit (node:events:517:28)
    at process.emit (node:domain:489:12)
    at Interface.<anonymous> (C:\Program Files\balena-cli\client\build\utils\helpers.js:258:39)
    at Interface.emit (node:events:517:28)
    at Interface.emit (node:domain:489:12)
    at [_ttyWrite] [as _ttyWrite] (node:internal/readline/interface:1132:18)
    at ReadStream.onkeypress (node:internal/readline/interface:271:20)
    at ReadStream.emit (node:events:517:28)
    at ReadStream.emit (node:domain:489:12)
    at emitKeys (node:internal/readline/utils:371:14)
    at emitKeys.next (<anonymous>)
    at ReadStream.onData (node:internal/readline/emitKeypressEvents:64:36)
    at ReadStream.emit (node:events:517:28)
    at ReadStream.emit (node:domain:489:12)
1 Like
2

Greetings @matrover. We may be sharing a similar issue. My problem started in December before the holidays.

3

Hey @matrover, was this working before and something changed? What version of the Supervisor is running on the Pi3?

What version of balena CLI are you using? If there is a newer version available I would suggest you try that as well!

4

Try falling back to “balena-cli”: “17.4.6” (8-Dec-2023). That is the last version of CLI that properly works for me.

5

Thanks for reporting @matrover. This problem sounds like GitHub issue 2715. It is a regression in balenaCLI introduced in v17.4.7. We are working on a fix in PR 2719.

6

Thanks for coming back to me @kb2ma will keep an eye out for the update.

7

@matrover We have published balenaCLI 17.4.12 to roll back the change that caused the local push failure. The problem was an error with a particular version of a node module we use in a few projects. We have a solution to leapfrog the error, and should implement that soon. Any changes will be transparent to a user of the CLI.

8

@kb2ma Great news! thanks