mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
installation error - Error: ENOTEMPTY: directory not empty, rmdir './dist-backup' #475
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#475
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @troublestarter on GitHub (Oct 25, 2021).
Is it a duplicated question?
Seems not
Describe your problem
Downloading dist⠂⠂⠂⸩ ⠏ : timing npm:load:cleanupLog Completed in 2ms
https://github.com/louislam/uptime-kuma/releases/download/1.9.1/dist.tar.gz
https://github-releases.githubusercontent.com/382496361/c32cc68f-f041-441e-a1cc-8feecd17beea?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211025%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211025T233100Z&X-Amz-Expires=300&X-Amz-Signature=ff1a107626b6be559c8e94bb313fd8936bd8bbe60b40e89ce8a2f3c56850fde5&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=382496361&response-content-disposition=attachment%3B%20filename%3Ddist.tar.gz&response-content-type=application%2Foctet-stream
Extracting dist...⠂⸩ ⠏ : timing npm:load:cleanupLog Completed in 2ms
fs.js:114
throw err;
^
Error: ENOTEMPTY: directory not empty, rmdir './dist-backup'
at Object.rmdirSync (fs.js:684:3)
at ClientRequest.https.get (/root/uptime-kuma/extra/download-dist.js:24:24)
at Object.onceWrapper (events.js:286:20)
at ClientRequest.emit (events.js:198:13)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:111:17)
at TLSSocket.socketOnData (_http_client.js:451:20)
at TLSSocket.emit (events.js:198:13)
at addChunk (_stream_readable.js:288:12)
at readableAddChunk (_stream_readable.js:269:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! uptime-kuma@1.9.1 setup:
git checkout 1.9.1 && npm ci --production && npm run download-distnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the uptime-kuma@1.9.1 setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-10-25T23_31_47_039Z-debug.log
Info
Uptime Kuma Version:
Using Docker?: Yes/No
Docker Version:
Node.js Version (Without Docker only):
OS: Debian 10
Browser:
@troublestarter commented on GitHub (Oct 25, 2021):
root@status:
/uptime-kuma# cat /root/.npm/_logs/2021-10-25T23_31_47_039Z-debug.logpresetup: uptime-kuma@1.9.10 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.24.0
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'setup' ]
7 info using npm@5.8.0
8 info using node@v10.24.0
9 verbose run-script [ 'presetup', 'setup', 'postsetup' ]
10 info lifecycle uptime-kuma@1.9.1
11 info lifecycle uptime-kuma@1.9.1
setup: uptime-kuma@1.9.1setup: unsafe-perm in lifecycle true12 verbose lifecycle uptime-kuma@1.9.1
13 verbose lifecycle uptime-kuma@1.9.1
setup: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/uptime-kuma/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binsetup: CWD: /root/uptime-kuma14 verbose lifecycle uptime-kuma@1.9.1
15 silly lifecycle uptime-kuma@1.9.1
setup: Args: [ '-c',setup: Returned: code: 1 signal: null15 silly lifecycle 'git checkout 1.9.1 && npm ci --production && npm run download-dist' ]
16 silly lifecycle uptime-kuma@1.9.1
17 info lifecycle uptime-kuma@1.9.1~setup: Failed to exec setup script
18 verbose stack Error: uptime-kuma@1.9.1 setup:
git checkout 1.9.1 && npm ci --production && npm run download-dist18 verbose stack Exit status 1
18 verbose stack at EventEmitter. (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)
18 verbose stack at EventEmitter.emit (events.js:198:13)
18 verbose stack at ChildProcess. (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack at ChildProcess.emit (events.js:198:13)
18 verbose stack at maybeClose (internal/child_process.js:982:16)
18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
19 verbose pkgid uptime-kuma@1.9.1
20 verbose cwd /root/uptime-kuma
21 verbose Linux 4.19.0-18-amd64
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "setup"
23 verbose node v10.24.0
24 verbose npm v5.8.0
25 error code ELIFECYCLE
26 error errno 1
27 error uptime-kuma@1.9.1 setup:
git checkout 1.9.1 && npm ci --production && npm run download-dist27 error Exit status 1
28 error Failed at the uptime-kuma@1.9.1 setup script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]
@louislam commented on GitHub (Oct 25, 2021):
You need Node.js 14.
Please read the requirement.