-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReferenceError: primordials is not defined #69
Comments
same error: `evalmachine.:43 ReferenceError: primordials is not defined |
Same error here...
|
Instructions say that this error was solved, but me too get all these "primordials is not defined" errors, even with the 'force' option. |
ok will look at shortly |
Correction: After running the following script |
@papinist can you show me the output of lsb_release -a |
Fresh Pi Image using latest software - straight to install script:
|
Install will work if you run the node 20 installer script first, but throws repeated: "(node:7940) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit" |
yes I see the maxlisteners thing too. but I fixed the install and upgrade again to include the node20.. |
Indeed - it does seem to be working normally again, other than the maxlisteners thing. |
Found and fixed my Mirror completely. Only weird thing is that PM2 will start up with everything stopped... |
Now it worked for me too, thank you! |
Same problem here, even when running the node20 script before and when applying force to the upgrade script.
And the error:
|
where did u get bookworm from? I don't see that on the download page. is this 64bit? post output of |
I did an in-place-upgrade. I've forgotten that raspbian (or now raspberry pi os) isn't debian, I am mostly just used to debian itself... |
download the node20_install.sh script curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh >node20_install.sh
to
and run it locally let me know do NOT try to run my upgrade script as it is still forcing node20... lets get thru this first... |
Thanks, node18 now installed, pm2 logs says:
Looks like the same as before. |
ok, now do this
then
|
Hi, in my MagicMirror directory there isn't a node_modules file or folder and nom run install-mm gives the already known error:
|
yeah you're failing on install. man I don't understand why they make this so hard. |
I'll try to get some time to make a new raspbian install, new MM install and try to swap the actual settings to the new install to see if it makes a difference. |
@nibblerrick there is another 'test' thing to try which ever exists
then
|
Sure. (graceful-fs instead of graceful_fs, right?)
/usr/lib/node_modules/npm:
(makes no difference if I use sudo) |
so another piece of advice is wrong. sorry, have to rebuild the SD card |
I'll do that, hopefully this weekend. |
So some news: I made a new SD-Card and then ran your install-script. Same error. node20 script and then install, same. |
I do not add aarch64, only arm64. |
this is the issue I opened in the node distro project |
Sorry, was arm64, not aarch64. |
I checked the raspberry imager and for 64 bit I need to explicitly choose that. So I was confused, because I should have running a 32 bit system, but uname -m states aarch64. |
interesting.. I don't use the pi imager as it crashes on my amd desktop.. so I use the balana etcher and download the image manually I only get the 64 bit kernel when I specifically flash that image |
If I understand correctly it not only happens when flashing with the rpi-imager but can also happen when just apt update && apt upgrade.
64bit:
Probably |
thanks.. |
I have to thank you for these excellent scripts which have saved me much time and are so convenient! |
see these updated scripts too.. |
Your "testit" branch has fixed the problem described earlier, which I also experienced. MM is now back online and working smoothly. Thank you! |
@camillemarius @nibblerrick the testit branch has been merged back to master.. |
can we close this now? |
Sorry for getting back so late, from my end this can be closed, thank you very much! |
install.log
The text was updated successfully, but these errors were encountered: