#Openclaw update hanging

1 messages · Page 1 of 1 (latest)

grizzled mantle
#

Working directory is clean (110ms)
│
◇ ✓ Fetching latest changes (24.71s)
│
◇ ✓ Upstream branch exists (14ms)
│
◇ ✓ Resolving upstream commit (10ms)
│
◇ ✓ Enumerating candidate commits (11ms)
│
◇ ✓ Preparing preflight worktree (2.17s)
│
◇ ✓ preflight checkout (bc97182d) (187ms)
│
◇ ✓ preflight deps install (bc97182d) (34.92s)
│
◇ ✓ preflight build (bc97182d) (81.69s)
│
◇ ✗ preflight lint (bc97182d) (1201.14s)
status: null,
signal: 'SIGKILL',
output: [ null, null, null ],
pid: 231547,
stdout: null,
stderr: null
}
Node.js v22.22.0
[oxlint:core] finished

clever stagBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

harsh portal
#

same issue here

harsh portal
#

stuck here... Running as unit: run-p3773-i4073.scope; invocation ID: 02fbf2bb85814939bc1cbd8c01ede066
Updating OpenClaw...

│
◇ ✓ Working directory is clean (60ms)
│
◇ ✓ Fetching latest changes (10.77s)
│
◇ ✓ Upstream branch exists (7ms)
│
◇ ✓ Resolving upstream commit (6ms)
│
◇ ✓ Enumerating candidate commits (7ms)
│
◇ ✓ Preparing preflight worktree (26.82s)
│
◇ ✓ preflight checkout (2daf3d33) (143ms)
│
◇ ✓ preflight deps install (2daf3d33) (59.46s)
│
◇ ✓ preflight build (2daf3d33) (82.13s)
│
◒ preflight lint (2daf3d33)

grizzled mantle
#

Yeah same

harsh portal
#

what config you have ?

grizzled mantle
#

VPS server
Using GIT, just moved away from npm last week

#

I just got this error

✗ preflight lint (2d97dceb) (673.55s)
status: null,
signal: 'SIGKILL',
output: [ null, null, null ],
pid: 234007,
stdout: null,
stderr: null
}
Node.js v22.22.0
[oxlint:extensions] finished

harsh portal
#

◇ ✗ preflight lint (2daf3d33) (1223.98s)
[oxlint:core] starting
[oxlint:extensions] starting
[oxlint:scripts] starting
[oxlint:scripts] finished
│
◓ preflight checkout (3c7a641b).

torpid oracle
#

@grizzled mantle @harsh portal

it will never finish and no matter how much RAM you give it (for WSL) it will consume 100% every time , you can update it by these steps ...

**STEPS TO UPDATE OPENCLAW IN WSL2.

1.** cd /home/user/openclaw-main #(move to root dir of openclaw).

2. git stash -u #(save personal folders)

3. mv ~/openclaw-main/hello ~/hello_backup #(backup the workspace)

4. git remote add origin https://github.com/openclaw/openclaw.git (set repo link).

5. git remote -v (verify the link).

6. git fetch origin #(update directly via git bypassing openclaw internal update simulation which drink RAM like water)

7. git reset --hard origin/main #(register the version).

8. pnpm install #(build pnpm)

9. pnpm run build #(build the binary)

10. git stash pop #(bring back your folders).

11. mv ~/hello_backup ~/openclaw-main/hello #(bring back workspace).

12. openclaw --version #(check the version).
harsh portal
#

he stuck my cpu and ram 100% and crash before with the openclaw update command

torpid oracle
#

exactly basically what it does is to create a virtual simulation before updating so that new update won't blast your system means don't break things .... but seems it's broken atm

harsh portal
#

I feel like every time I update Open Claw I always get a surprise lol.

torpid oracle
#

lol

grizzled mantle
#

Should i wait for a fix or do this manual workaround?

torpid oracle