BBB 2.5 - Running bigbluebutton-html5/deploy_to_usr_share.sh fails

[Szymon C]

Trying to deploy html5 from freshly created docker-dev bb25 container. After running the command i get these errors:

npm WARN logfile }
(node:7831) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
rebuilt dependencies successfully
npm WARN logfile Error: EACCES: permission denied, scandir '/root/.npm/_logs'
npm WARN logfile  error cleaning log files [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
npm WARN logfile   errno: -13,
npm WARN logfile   code: 'EACCES',
npm WARN logfile   syscall: 'scandir',
npm WARN logfile   path: '/root/.npm/_logs'
npm WARN logfile }
(node:7842) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /root/.npm/_cacache/tmp
npm ERR! errno -13
npm ERR!
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR!
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 997:996 "/root/.npm"

npm ERR! Log files were not written due to an error writing to the directory: /root/.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
npm ERR! code 243
npm ERR! path /usr/share/meteor/bundle/programs/server
npm ERR! command failed
npm ERR! command sh -c -- node npm-rebuild.js

1105 timing reify:save Completed in 31ms
1106 timing reify Completed in 11586ms
1107 timing command:i Completed in 13541ms
1108 notice
1108 notice New major version of npm available! 8.19.3 -> 9.3.1
1108 notice Changelog: https://github.com/npm/cli/releases/tag/v9.3.1
1108 notice Run npm install -g n...@9.3.1 to update!
1108 notice
1109 verbose stack Error: command failed
1109 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27)
1109 verbose stack     at ChildProcess.emit (node:events:513:28)
1109 verbose stack     at maybeClose (node:internal/child_process:1100:16)
1109 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
1110 verbose cwd /usr/share/meteor/bundle/programs/server
1111 verbose Linux 5.10.16.3-microsoft-standard-WSL2
1112 verbose node v16.19.0
1113 verbose npm  v8.19.3
1114 error code 243
1115 error path /usr/share/meteor/bundle/programs/server
1116 error command failed
1117 error command sh -c -- node npm-rebuild.js
1118 verbose exit 243
1119 timing npm Completed in 13620ms
1120 verbose code 243
1121 error A complete log of this run can be found in:
1121 error     /root/.npm/_logs/2023-01-18T10_50_57_258Z-debug-0.log

Also scripts from this directory are wiped out

bigbluebutton@bbb25:/usr/share/meteor/bundle$ ls -lah
total 32K
drwxr-xr-x 4 meteor meteor 4.0K Jan 18 11:02 .
drwxrwxrwx 3 meteor meteor 4.0K Jan 18 11:02 ..
-r--r--r-- 1 meteor meteor  243 Jan 18 11:02 main.js
-r--r--r-- 1 meteor meteor    9 Jan 18 11:02 .node_version.txt
drwxr-xr-x 5 meteor meteor 4.0K Jan 18 11:02 programs
-r--r--r-- 1 meteor meteor  535 Jan 18 11:02 README
drwxr-xr-x 2 meteor meteor 4.0K Jan 18 11:02 server
-r--r--r-- 1 meteor meteor  604 Jan 18 11:02 star.json

Any help?

[Szymon C]

Is the problem related to node version? Shouldn't it be node v14.*? I see that this script is using node from /usr/bin/node, while other scripts use node from /usr/share/node-v14.21.1-linux-x64/bin

[Anton Georgiev]

Hey Szymon,

Which step of the script is the error happening on?

There seems to be an error about npm and root file ownership... Could you confirm which user you run the script as? `whoami`

Yes, we're on node v14.21.1 on BBB 2.5 right now, do you see any indication of a different node version being picked? (npm is not exactly the same as node)

-Anton