nodejs / nodejs/build

Out of space on www server

Open
#3,157 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

build-agenda incident infra
Dominant language
Jinja
Stars
541
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

Reported by @RafaelGSS when trying to promote 19.5.0:

# Promoting v19.5.0...
... Checking assets
... Expecting a total of 39 assets for v19.x
... 39 assets waiting in staging
... 0 assets already promoted
 ✓  Complete set of expected assets in place for v19.x
Are you sure you want to promote the v19.5.0 assets? [y/n] y
Promoting v19.5.0/docs...
...
Promoting v19.5.0/win-x86...
/home/nodejs/queue-cdn-purge.sh: line 13: echo: write error: No space left on device

This is a different disk (/dev/vda1) to https://github.com/nodejs/build/issues/3125 and is not the disk that holds the downloads.

Filesystem      Size  Used Avail Use% Mounted on
udev            7.9G     0  7.9G   0% /dev
tmpfs           1.6G  3.8M  1.6G   1% /run
/dev/vda1       315G  302G     0 100% /
tmpfs           7.9G   76K  7.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda        3.9T  1.7T  2.0T  47% /home
/dev/sdb        2.0T  1.8T   27G  99% /mnt/nodejs_org_home_old
tmpfs           1.6G     0  1.6G   0% /run/user/0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the root filesystem usage on the www server and the command at /home/nodejs/queue-cdn-purge.sh line 13. Confirm what is consuming /dev/vda1, then verify that promoting v19.5.0 completes without the no-space error; the issue is done when the promotion can run reliably with adequate root-disk space.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
infrastructure, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.