Read the statement by Michael Teeuw here.
Installation Problems
-
I’m attempting (again) to get MM working well on a Pi Zero W.
After flashing the card with the Legacy 32-bit OS, I connected via ssh and executedbash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"
and this was the result:Updating packages ... [ <=> ]Installing helper tools ... Check current Node installation ... Node.js is not installed. Installing Node.js ... Node.js installation Done! version=v20.9.0 Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V10.1.0 Installed npm version: V10.1.0 No npm upgrade necessary. Cloning MagicMirror ... Cloning into 'MagicMirror'... remote: Enumerating objects: 399, done. remote: Counting objects: 100% (399/399), done. remote: Compressing objects: 100% (314/314), done. remote: Total 399 (delta 78), reused 185 (delta 70), pack-reused 0 (from 0) Receiving objects: 100% (399/399), 457.00 KiB | 797.00 KiB/s, done. Resolving deltas: 100% (78/78), done. Cloning MagicMirror Done! Installing dependencies ... (node:8329) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (Use `node --trace-warnings ...` to show where the warning was created) (node:8329) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (node:8329) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (node:8329) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit npm notice npm notice New minor version of npm available! 10.1.0 -> 10.8.3 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3 npm notice Run npm install -g npm@10.8.3 to update! npm notice npm ERR! code ETIMEDOUT npm ERR! errno ETIMEDOUT npm ERR! network request to https://registry.npmjs.org/ignore failed, reason: npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/dvg/.npm/_logs/2024-09-28T18_28_59_417Z-debug-0.log Unable to install dependencies!
I have a blazing fast internet connection at home, and am not behind any sort of proxy or firewall.
Any thoughts on how to resolve? And what’s with all the
MaxListenersExceededWarning
warnings? -
@davidgagne timeout is a network problem. do you have a pihole server on your network? others experiencing similar problems have reported that cause.
-
@davidgagne the maxlisteners problem is a bug in npm we can’t suppress
-
@sdetweil No, I am not running a pihole or any other service or hardware which would cause a network delay, and the device is fairly close to the WiFi router. There’s no reason I can imagine for a network timeout.
-
@davidgagne i have never experienced timeout on my pi0w
-
@davidgagne did you make any progress?