ENOTEMPTY when installing node from palette since nodered 3.0 (directory not empty)

Einstein8854 · 3 August 2022 11:42

hello,
my english is bad...
i have nodered in docker
since the new version (3.0.0) i can't add new palets or update existing palet.
i have this message in log

2022-08-03T11:41:30.188Z Install : node-red-contrib-rfxcom 2.11.3

2022-08-03T11:41:32.206Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-rfxcom@2.11.3
2022-08-03T11:41:33.958Z [err] npm
2022-08-03T11:41:33.959Z [err]  WARN 
2022-08-03T11:41:33.959Z [err] config production Use `--omit=dev` instead.
2022-08-03T11:41:56.942Z [err] npm
2022-08-03T11:41:56.942Z [err]  ERR!
2022-08-03T11:41:56.942Z [err]  code
2022-08-03T11:41:56.943Z [err]  ENOTEMPTY
2022-08-03T11:41:56.943Z [err] npm ERR!
2022-08-03T11:41:56.943Z [err]  syscall rename
2022-08-03T11:41:56.944Z [err] npm
2022-08-03T11:41:56.944Z [err]  ERR! path /data/node_modules/marked
2022-08-03T11:41:56.944Z [err] npm ERR! dest /data/node_modules/.marked-zxF1Vjah
2022-08-03T11:41:56.945Z [err] npm ERR! 
2022-08-03T11:41:56.946Z [err] errno -39
2022-08-03T11:41:56.949Z [err] npm ERR! ENOTEMPTY: directory not empty, rename '/data/node_modules/marked' -> '/data/node_modules/.marked-zxF1Vjah'
2022-08-03T11:41:56.954Z [err] 
2022-08-03T11:41:56.955Z [err] npm ERR! A complete log of this run can be found in:
2022-08-03T11:41:56.955Z [err] npm ERR!     /data/.npm/_logs/2022-08-03T11_41_33_829Z-debug-0.log
2022-08-03T11:41:57.026Z rc=217

plfinch · 4 August 2022 15:13

I am experiencing this as well both with node-red 2.2.2 and after upgrading to 3.0.2. Palette manager shows 2 nodes with available updates:
node-red-node-email from 1.15.1 to 1.17.0
node-red-node-snmp from 1.0.1 to 1.0.2

I receive similar ENOTEMPTY errors for both:

2022-08-04T15:09:29.165Z Install : node-red-node-email 1.17.0
2022-08-04T15:09:29.854Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-node-email@1.17.0
2022-08-04T15:09:30.884Z [err] npm
2022-08-04T15:09:30.885Z [err]  WARN
2022-08-04T15:09:30.885Z [err]  config production Use `--omit=dev` instead.
2022-08-04T15:09:32.149Z [err] npm ERR! code ENOTEMPTY
2022-08-04T15:09:32.149Z [err] npm
2022-08-04T15:09:32.149Z [err]  ERR! syscall rename
2022-08-04T15:09:32.150Z [err] npm 
2022-08-04T15:09:32.150Z [err] ERR! 
2022-08-04T15:09:32.150Z [err] path
2022-08-04T15:09:32.150Z [err]  /home/pi/.node-red/node_modules/node-red-node-email
2022-08-04T15:09:32.150Z [err] npm 
2022-08-04T15:09:32.150Z [err] ERR! dest /home/pi/.node-red/node_modules/.node-red-node-email-eJQ2YdZ0
2022-08-04T15:09:32.151Z [err] npm ERR!
2022-08-04T15:09:32.151Z [err]  errno -39
2022-08-04T15:09:32.153Z [err] npm ERR!
2022-08-04T15:09:32.154Z [err]  ENOTEMPTY: directory not empty, rename '/home/pi/.node-red/node_modules/node-red-node-email' -> '/home/pi/.node-red/node_modules/.node-red-node-email-eJQ2YdZ0'
2022-08-04T15:09:32.156Z [err] 
2022-08-04T15:09:32.157Z [err] npm 
2022-08-04T15:09:32.157Z [err] ERR! A complete log of this run can be found in:
2022-08-04T15:09:32.157Z [err] npm ERR!     /home/pi/.npm/_logs/2022-08-04T15_09_30_808Z-debug-0.log
2022-08-04T15:09:32.166Z rc=217

Here are system details:

HardwareRaspberry Pi 4 Model B Rev 1.2 CPU: 4xARMv7 RAM: 3930868kB
EEPROM Bootloader Thu 10 Mar 2022 11:57:12 AM UTC (1646913432)
EEPROM Firmware 000138a1
Linux Kernel Linux NetMon 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
Operating System Raspbian GNU/Linux 10 (buster) version 10.12
Node-RED Version v2.2.2
Node.js Version v16.16.0
npm Version 8.11.0
SQLite Version 3.34.0

Thoughts?

Peter

Colin · 4 August 2022 15:25

I don't know why this is happening recently, but I think if you delete that folder it will be ok.

HaroldPetersInskipp · 4 August 2022 15:39

Seems to be a trend here that I'm noticing.

Colin · 4 August 2022 15:55

Yes, something must be going on behind the scenes. Possibly an npm change.

dceejay · 4 August 2022 15:59

Most odd indeed. Weird it mostly seems to be around the email node.

Steve-Mcl · 4 August 2022 16:08

Yeah, I noticed that but then this OP's post makes me think something else going on...

I know marked is a dependency in node-red. So this is slightly different (and still odd)

dceejay · 4 August 2022 16:13

If it’s in the core then why is this in the user (data/) node_modules area ?

Steve-Mcl · 4 August 2022 16:16

Dont know Dave - just saying that I know marked is a dependency - so the whole situation of adding (the email node) may not be the cause.

I suppose the difference in the 2 posts in this thread is the OP's is a docker install and the 2nd issue is a PI install.

I cant piece it together from the info floating around.

dceejay · 4 August 2022 16:58

Indeed. Likewise. And of course “it worked for me”. Tricky. Just have to keep an eye open.

FireWizard52 · 4 August 2022 17:41

Hi,

I noticed exactly the same. when I updated the email node about 2 weeks ago from version 1.15.1 to 1.17.0. My NR instance doesn't run in a Docker container, but just on a Raspberry Pi.

The first try to update from the palette failed, so I moved to the CLI and tried again.
It ended with a same error as described above. A hidden .node-red-node-email-XXXXXX
My first thought was similar to what @Colin suggested. Delete that directory.
Tried again and it returned with an error and another hidden dierectory has to be deleted.
This happened a few times. A check turned out, that there were more hidden directories in the node_modules directory. So how many to go?

I decided to delete the node_modules directory and to re-install my modules.
Afterwards I could install the email node without problems.
It happened to me on one of my two Raspberries, where these nodes has been installed.

The second one did not contain hidden directories and there the email node installed without issues.

Regards

plfinch · 4 August 2022 17:57

Oddness... When I try to update node-red-node-snmp, it was still the same email node file that is complained about:

2022-08-04T17:14:41.066Z Install : node-red-node-snmp 1.0.2
2022-08-04T17:14:41.804Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-node-snmp@1.0.2
2022-08-04T17:14:42.814Z [err] npm
2022-08-04T17:14:42.815Z [err]  WARN
2022-08-04T17:14:42.815Z [err]  config production Use `--omit=dev` instead.
2022-08-04T17:14:45.377Z [err] npm
2022-08-04T17:14:45.377Z [err]  ERR!
2022-08-04T17:14:45.378Z [err]  
2022-08-04T17:14:45.378Z [err] code ENOTEMPTY
2022-08-04T17:14:45.378Z [err] npm 
2022-08-04T17:14:45.378Z [err] ERR! syscall rename
2022-08-04T17:14:45.379Z [err] npm
2022-08-04T17:14:45.379Z [err]  ERR! path /home/pi/.node-red/node_modules/node-red-node-email
2022-08-04T17:14:45.379Z [err] npm 
2022-08-04T17:14:45.379Z [err] ERR! dest /home/pi/.node-red/node_modules/.node-red-node-email-eJQ2YdZ0
2022-08-04T17:14:45.379Z [err] npm 
2022-08-04T17:14:45.380Z [err] ERR! 
2022-08-04T17:14:45.380Z [err] errno -39
2022-08-04T17:14:45.382Z [err] npm ERR!
2022-08-04T17:14:45.382Z [err]  ENOTEMPTY: directory not empty, rename '/home/pi/.node-red/node_modules/node-red-node-email' -> '/home/pi/.node-red/node_modules/.node-red-node-email-eJQ2YdZ0'
2022-08-04T17:14:45.385Z [err] 
2022-08-04T17:14:45.386Z [err] npm 
2022-08-04T17:14:45.386Z [err] ERR! A complete log of this run can be found in:
2022-08-04T17:14:45.386Z [err] npm ERR!     /home/pi/.npm/_logs/2022-08-04T17_14_42_748Z-debug-0.log
2022-08-04T17:14:45.395Z rc=217

I deleted directory /home/pi/.node-red/node_modules/.node-red-node-email-eJQ2YdZ0, rebooted, and then could run both node updates successfully.

I successfully updated the email and snmp nodes this way on both node-red 2.2.2 and 3.0.2. (I have my applications installed on both as I am still testing 3.0.2.)

Peter

Colin · 5 August 2022 08:19

Others are encountering this issue too.

github.com/npm/cli

[BUG] install global typescript got error: npm ERR! ENOTEMPTY: directory not empty

opened 07:41AM - 26 Nov 21 UTC

aladdin-add

Release 8.x Bug Needs Triage

### Is there an existing issue for this? - [X] I have searched the existing iss…ues ### This issue exists in the latest npm version - [X] I am using the latest npm ### Current Behavior ```bash ➜ create-config git:(feat/eslint-init) npm i typescript -g npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /Users/weiran/.npm-global/lib/node_modules/typescript npm ERR! dest /Users/weiran/.npm-global/lib/node_modules/.typescript-ffKYZhoU npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/Users/weiran/.npm-global/lib/node_modules/typescript' -> '/Users/weiran/.npm-global/lib/node_modules/.typescript-ffKYZhoU' npm ERR! A complete log of this run can be found in: npm ERR! /Users/weiran/.npm/_logs/2021-11-26T07_32_40_759Z-debug.log ``` ### Expected Behavior global typescript installed without error. ### Steps To Reproduce _No response_ ### Environment - npm: 8.1.4 - Node: v17.0.1 - OS: macOS 12.1 - platform: - npm config: ```ini ; copy and paste output from `npm config ls` here ; "user" config from /Users/weiran/.npmrc //git.dian.so/api/v4/packages/npm/:_authToken = (protected) //npm.xiaodiankeji.net/:_authToken = (protected) //registry.npmjs.org/:_authToken = (protected) home = "https://npm.taobao.org" http-proxy = "http://127.0.0.1:8118" https-proxy = "http://127.0.0.1:8118/" init-author-name = "weiran" ; package-lock = true ; overridden by project prefix = "/Users/weiran/.npm-global" proxy = "http://127.0.0.1:8118/" ; "project" config from /Users/weiran/repo/github/create-config/.npmrc package-lock = false ; node bin location = /usr/local/bin/node ; cwd = /Users/weiran/repo/github/create-config ; HOME = /Users/weiran ; Run `npm config ls -l` to show all defaults. ```

github.com/firebase/firebase-tools

npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools'

opened 04:12PM - 23 Mar 22 UTC

closed 06:09PM - 23 Mar 22 UTC

Tom3652

bug

### [REQUIRED] Environment info **firebase-tools:** 10.2.2 **Platform:** macOS ### [REQUIRED] Test case ``` (base) foxtom@MacBook-Pro-de-FoxTom myproject % sudo npm install -g firebase-tools Password: npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/firebase-tools npm ERR! dest /usr/local/lib/node_modules/.firebase-tools-ENG41nb9 npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools' -> '/usr/local/lib/node_modules/.firebase-tools-ENG41nb9' npm ERR! A complete log of this run can be found in: npm ERR! /Users/foxtom/.npm/_logs/2022-03-23T16_07_07_098Z-debug-0.log ``` ### [REQUIRED] Steps to reproduce ![Capture d’écran 2022-03-23 à 17 09 50](https://user-images.githubusercontent.com/32631467/159744742-379ad819-3e90-4c05-b122-cafd9c430247.png) As asked by the message, run ```sudo npm install -g firebase-tools``` (if you run without `sudo` you will get a permission denied error) ### [REQUIRED] Expected behavior Be able to update the CLI tools. ### [REQUIRED] Actual behavior ``` npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/firebase-tools npm ERR! dest /usr/local/lib/node_modules/.firebase-tools-ENG41nb9 npm ERR! errno -66 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/firebase-tools' -> '/usr/local/lib/node_modules/.firebase-tools-ENG41nb9' npm ERR! A complete log of this run can be found in: npm ERR! /Users/foxtom/.npm/_logs/2022-03-23T16_07_07_098Z-debug-0.log ``` I have to delete the directory manually to fix this and i would prefer to not do this by myself

github.com/homebridge/homebridge

Update to v4.45.0 failed

opened 12:52AM - 25 May 22 UTC

closed 04:04AM - 25 May 22 UTC

rupil10

question

### Current Situation When I updated to v4.43.3 I received a similar error to b…elow. I was able to get around it by updating it via terminal from some guide that I found online however just trying to update to v4.45.0 the same thing has happened again. Am I going to have to keep forcing it to happen via terminal or is there someway that I can fix this issue so that I can just update using the UI. I really don't understand the terminal side of things in great detail and feel like I might break my installation if I mess with it too much. USER: pi DIR: /usr/local CMD: sudo -E -n npm install -g homebridge-config-ui-x@latest npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/homebridge-config-ui-x npm ERR! dest /usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4 npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/homebridge-config-ui-x' -> '/usr/local/lib/node_modules/.homebridge-config-ui-x-3gtnOIj4' npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-05-24T22_06_22_459Z-debug.log Cleaning up npm cache, please wait... npm cache cleared, please try updating homebridge-config-ui-x again. Command failed. Please review log for details. Thanks ### Logs ```markdown none ``` ### Configuration ```json none ``` ### Environment - OS: - Software: - Node: - npm: ### Process Supervisor hb-service ### Additional Context _No response_

and numerous others, but so far have not found any information about what might be triggering it.

Einstein8854 · 5 August 2022 12:50

hy,
on complement off my post about this problem :
1/ my configuration is not on a Pi, it's on a PC with amd sempro 2 x 2100 with 6 go of ram and an hd of 250 Go ant os is ubuntu 22.04 lts
2/ nodered is in a container docker
3/ my problem is not only with palette rfxcom but for all new palette or update, since nodered was update in 3.0 with watchtower (other container of docker)

Colin · 5 August 2022 13:04

Is it ok once you delete the folder?

gbansen · 8 August 2022 17:17

Problem on all node updates in 3.0 and above.

2022-08-08T17:11:21.389Z Install : node-red-contrib-bigtimer 2.8.2

2022-08-08T17:11:21.196Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-bigtimer@2.8.2

2022-08-08T17:11:22.771Z [err] npm

2022-08-08T17:11:22.772Z [err]

2022-08-08T17:11:22.773Z [err] WARN

2022-08-08T17:11:22.773Z [err]

2022-08-08T17:11:22.773Z [err] config

2022-08-08T17:11:22.773Z [err] production Use --omit=dev instead.

2022-08-08T17:11:31.161Z [err] npm

2022-08-08T17:11:31.161Z [err]

2022-08-08T17:11:31.161Z [err] ERR!

2022-08-08T17:11:31.162Z [err]

2022-08-08T17:11:31.162Z [err] code

2022-08-08T17:11:31.162Z [err] ENOTEMPTY

2022-08-08T17:11:31.162Z [err] npm

2022-08-08T17:11:31.162Z [err]

2022-08-08T17:11:31.163Z [err] ERR!

2022-08-08T17:11:31.163Z [err]

2022-08-08T17:11:31.163Z [err] syscall

2022-08-08T17:11:31.163Z [err] rename

2022-08-08T17:11:31.163Z [err] npm

2022-08-08T17:11:31.163Z [err]

2022-08-08T17:11:31.163Z [err] ERR!

2022-08-08T17:11:31.163Z [err]

2022-08-08T17:11:31.164Z [err] path

2022-08-08T17:11:31.164Z [err] /config/node-red/node_modules/agent-base

2022-08-08T17:11:31.164Z [err] npm

2022-08-08T17:11:31.164Z [err]

2022-08-08T17:11:31.164Z [err] ERR!

2022-08-08T17:11:31.164Z [err]

2022-08-08T17:11:31.164Z [err] dest

2022-08-08T17:11:31.164Z [err] /config/node-red/node_modules/.agent-base-MyGAUl8n

2022-08-08T17:11:31.165Z [err] npm

2022-08-08T17:11:31.165Z [err]

2022-08-08T17:11:31.165Z [err] ERR!

2022-08-08T17:11:31.165Z [err]

2022-08-08T17:11:31.165Z [err] errno

2022-08-08T17:11:31.165Z [err] -39

2022-08-08T17:11:31.169Z [err] npm

2022-08-08T17:11:31.169Z [err]

2022-08-08T17:11:31.169Z [err] ERR!

2022-08-08T17:11:31.169Z [err] ENOTEMPTY: directory not empty, rename '/config/node-red/node_modules/agent-base' -> '/config/node-red/node_modules/.agent-base-MyGAUl8n'

2022-08-08T17:11:31.171Z [err]

2022-08-08T17:11:31.172Z [err] npm

2022-08-08T17:11:31.172Z [err]

2022-08-08T17:11:31.172Z [err] ERR!

2022-08-08T17:11:31.172Z [err] A complete log of this run can be found in:

2022-08-08T17:11:31.172Z [err] npm

2022-08-08T17:11:31.172Z [err]

2022-08-08T17:11:31.172Z [err] ERR!

2022-08-08T17:11:31.172Z [err] /root/.npm/_logs/2022-08-08T17_11_22_666Z-debug-0.log

2022-08-08T17:11:31.198Z rc=217

Colin · 8 August 2022 19:47

This is an npm problem that pops up occasionally and no one knows why. Delete the folder mentioned and try again. It should be ok.

Though why you are installing there I don't know.

Einstein8854 · 9 August 2022 10:18

no,
what folder i must delete and where he is ?
i don't find it......

Colin · 9 August 2022 10:48

It says it is /config/node-red/node_modules/.agent-base-MyGAUl8n but that is a bit odd I have to admit. What hardware/os are you running on and how did you install node-red?

gbansen · 9 August 2022 17:30

Yes sorry, node-red is installed in Home Assistant on a virtual machine. I know were that folder is and will rename it in case something goes wrong. I will test this tomorrow when I have some time. Thanks for your help.

Topic		Replies	Views
Cannot install nodes via palette manager General	7	316	4 January 2023
Nodered no npm Update possible General	5	839	29 September 2022
Node updates fail using Manage Palette General	4	347	16 November 2022
Can't install palette on docker stack General	1	471	27 February 2022
Update Problem with node-red-contrib-netatmo 0.3.0 General	3	469	31 January 2022

ENOTEMPTY when installing node from palette since nodered 3.0 (directory not empty)

Problem on all node updates in 3.0 and above.

Related topics