I have a Debian server running with Plesk.
This server hosts the pedagogical platform I created.
This platform uses WebSocket technology to allow teachers and students interactions in real time.
From the side server, a nodejs script started by PM2 manages all this.
My problem is that in a totally random way and without anyone doing anything, PM2 "uninstall" alone and the WebSocket server stops working ...
I can solve the problem easily using:
NPM Install -G PM2 and restart the script.
The hours are never the same and do not match with a cron task:
First time early December in the morning
Wednesday, December 22 in the morning
(I then create a monitoring with Uptime Robot)
Thursday January 13 at 5:12 am (GMT+1)
Wednesday, January 26 at 15:57 pm (GMT+1)
I can't find anything in log files ...
It's really problematic because we have many users and a continuity of service to ensure.
Any ideas ?
Thank you
The problem seems to be caused by Plesk which deletes the elements installed globally in /opt/plesk/node/17/bin
I changed approach. I installed PM2 locally in an other folder.
Problem solved.
Related
After I upgraded to macOS 13. I found a problem with command in nextjs first. I tried to run my project with: npm run dev
This is result:
> dev
> next dev
It stucked on this log very very long time.
and I tried to create another project using:
npx create-next-app#latest
Result same to nextjs
About my computer:
Macbook pro 2018 13-inch 4 ports
I used Oh My Zsh on terminal
my node.js version is 16.18.0 (16.9.1 on this question created)
UPDATED 27/10/22
After I asked in this community. I tried many way to solve this issues.
This is way I tried:
Reinstall macOS Ventura and not working
Change node.js version to 16.18.0 => 19.0.0 and downgraded to 16.18.0 and not working
And now this problem is still. I still can't resolve this problem :(
I also had the same problem when I tried to run the nestjs application. Also failed to install packages, I got this error every time
It turned out that this could be a problem related to the IPv6 configuration. I disabled this setting and everything started working fine
Maybe it will also help you.
UPDATES
You can find this settings
Updated 28/10/2022 This problem I can resolved!!!!!
Today, I tried to clean install macOS Ventura (by backup internal storage => erase internal storage => install macOS Ventura by bootable drive and recovery data from backup hard disk)
All commands worked normally!
If you found a problem like this, you can resolve by clean install macOS!
I'm just getting back into trying some front end projects for the first time in a few years. Many npm-based javascript projects I try out end up taking a long time to start up in development mode even for Hello World-ish examples. In particular I'm trying out Nuxt.js.
Dev server startup takes about 100 seconds, and nothing seems to get cached so restarts (not hot reloads) take the same amount of time. My research into the project and known npm issues did not turn up any definitive root cause or ways to improve this yet.
I'm using emacs 26.1 in terminal mode on a 2018 13" MacBook Pro with a core i5, 8 GB of ram, and an SSD.
When I run npm run dev to startup the nuxt dev server I get repeated error in process filter: Args out of range: "\342", -1 errors related to some unusual characters they are using to try to make the output pretty. If I try the same thing in a vanilla Mac OS terminal the server startup goes 10x faster. Why do those errors occur, and why is it so much slower in an emacs terminal?
It turns out the repeated error in process filter issue may be caused by a bug in term mode that was recently fixed but might still be an issue in my version of emacs.
As a workaround, the following can get the nuxt dev server running in ~10s instead of ~100s in an emacs terminal on my mac by filtering out the repeated lines about the modules being built:
$ npm run dev | grep -v modules
Note that I tried using npm's options to adjust the log level but none seem to filter this output. If anyone knows a more "official" way of filtering this, or even better, if you know how to make it such that it doesn't try to rebuild the modules on every dev server start up, I'd be interested to know.
Edit: it might make sense to adjust the dev script command in the package.json file to include the grep filter, that way you can still just type npm run dev and get the workaround.
It's second time i was install SQL server 2017 on window 10
Getting stuck on installation progress error as below
sql_inst_mpyConfigAction_Install_Confignonrc_Cpu64
Had the same issue just now. Waiting for about 30 min worked for me. I assume it was downloading Python or R packages under the hood, so disabling those options from installation could help.
Some thing has happened in the last day with Uwamp not starting up Apache, but when I manually go into the httpd.exe folder and run it from a command line apache starts fine and I can access localhost easily. Any thing come to mind? I was playing with clipboard apps yesterday but how could they affect Uwamp starting httpd.exe??
After 2 days, still can't find out what's wrong. Developer is not answering this question. Yes, he knows this question exists.
i have had the same problem, but it looks like it could be down to the mscvr1110.dll issue Visual c++ 2012 runtime, you must install the 32 bit version along side with the 64 bit [if you are running a 64bit windows] and I would personally install the 32 bit first [then the 64bit - if applicable]
the one problem I have noticed is if you are selecting php 7 then it loads httpd.conf rather than the httpd_uwamp.conf, so at the moment I wouldn't select that option.
Let me know if that helps
I have been trying to install IonCube for the past 2 days on my localhost, and it just won't show up. Today I tried changing the PHP versions to force some sort of hard refresh, and MAMP is not changing versions.
By the looks of this, in my opinion, Apache is not restarting at all, how can I force it to stop with a Terminal command or something?
Thanks in advance.
The short and sweet is to restart your machine entirely, fine for if you're just a local developer.