Hi, I’m a newbie who has somehow worked out on installing a self-hosted n8n on AWS EC2 service. Without much background in software engineering, I have to admit that I’m not too sure about what I’m doing, but I try my best.
I have been able to have a running n8n v.0.236.3 through my own URL with something called like n8n.myDomain.com .
I tried to update the n8n to v1.0.5 through the console, with the following command:
sudo npm install -g [email protected]
And halfway through the installation, the console freezes here:
[ec2-user@ip-172-_______ .n8n]$ sudo npm install -g [email protected]
(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 C(#########⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: timing reifyNode:node_modules/n8n/node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64 Completed in 175ms
And then the console stopped being responsive.
I rebooted the instance, ran the following to clean up the previously failed installation.
sudo npm uninstall -g n8n # Uninstall the previously attempted installation
sudo npm cache clean -f # Clear the npm cache
sudo npm install -g npm
sudo npm install -g [email protected]
But it reached reached the same console freezing point again.
Interestingly, I had this same console freezing point when yesterday I tried updating my n8n to v.0.236.3, too (Unsure from which previous version).
Somehow it didn’t go well, so I did the same steps the next day, and somehow the issue was resolved and the installation to v.0.236.3 went smoothly.
Therefore I had thought that it was me doing some instructions wrong the other day, but today my console stopped at the same location despite me rebooting the instance two times.
The original n8n was installed using these code:
sudo yum install -y nodejs
node -v
sudo npm install -g n8n
Has anyone ran into something similar?
Edit: Half an hour after rebooting after this incident, the re-run of installation of the new version 1.0.5 was successful. It’s very strange that this took two tries, same as my experience before. Being once stuck at the msgpackr-extract-darwin was somewhat unavoidable. Quite strange.
[ec2-user@ip-172-___ ~]$ sudo npm install -g [email protected]
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
npm WARN deprecated [email protected]: Please switch to @apidevtools/json-schema-ref-parser
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
added 1331 packages in 3m
162 packages are looking for funding
run `npm fund` for details