#Installing is stuck

1 messages · Page 1 of 1 (latest)

fading flume
#

Installing on a Linus VPS with 96GB Ram and 18vCPU, using the command from the install docs, it is stuck on "Installing Openclaw v2026.4.14"

turbid wrenBOT
toxic troutBOT
#

Yep, that sounds genuinely stuck.

That exact line is right before the npm install step, so if it sits there for more than a few minutes, I’d re-run with verbose output so we can see what npm is waiting on:

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard --verbose

Then paste the last 50 to 100 lines here, plus:

node -v
npm -v
command -v openclaw && openclaw --version

If you want, also include your distro:

fading flume
#
  • cmd+=(--no-fund --no-audit install -g "$spec")
  • local cmd_display=
  • printf -v cmd_display '%q ' env SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm --loglevel notice --no-fund --no-audit install -g openclaw@latest
  • LAST_NPM_INSTALL_CMD='env SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm --loglevel notice --no-fund --no-audit install -g openclaw@latest'
  • [[ 1 == \1 ]]
  • env SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm --loglevel notice --no-fund --no-audit install -g openclaw@latest
  • tee /tmp/tmp.2lEuWiOL18
    npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
    npm warn deprecated npmlog@5.0.1: This package is no longer supported.
    npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
    npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
    npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
    npm warn deprecated gauge@3.0.2: This package is no longer supported.
    npm warn deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
    npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead

v22.22.2
10.9.7

PRETTY_NAME="Ubuntu 24.04.4 LTS"

#

Hello

toxic troutBOT
#

Hey 👋

When you’ve got it, paste the output of that direct npm install -g run and I’ll keep digging.

fading flume
#

npm error code ENOENT
npm error syscall open
npm error path /root/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/root/package.json'
npm error enoent This is related to npm not being able to find a file.

toxic troutBOT
#

Ah, that helps.

That error means npm didn’t get the package target, so it fell back to looking for a local package.json in /root.

Try this exact command, all on one line:

SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g openclaw@latest --foreground-scripts --loglevel verbose --no-fund --no-audit

If you want the simpler version first:

npm install -g openclaw@latest

So, the /root/package.json error is good news in a weird way, it means we have a copy/paste/command parsing issue, not an OpenClaw-specific crash yet.