@drx1984 if u used the installer, it should have setup a pm2 module to auto start mm in boot.
From your shell, can you try
pm2 list
@drx1984 if u used the installer, it should have setup a pm2 module to auto start mm in boot.
From your shell, can you try
pm2 list
@humdinger44 do
pm2 show
Find the name of the app
Then do
pm2 stop ????
Where ??? Is the app name
Then do the
npm start dev
from a terminal window
@Natacha now that u upgraded node, you have to go back and redo
npm install
in the MM folder and all module folders if they have a package.json file
you don’t change the clock.js u change the css or the config.js…
anyhow… open the developers window, ctrl-shift-i, and find the console tab,
scroll up to find any errors (usually red text)…
also can put clock into the filter box
@poopyurinal the shell script cannot find the command ‘source’.
so THAT is the 1st problem
try changing line 1 to
#!/bin/bash
to use bash instead of sh
I see the same problem here using sh
@poopyurinal edit the script again and add a new 1st line
#!/bin/sh
Because it is executable, the 1st line will be checked, and if the script processor is defined, it will be used
The default is also /bin/sh
@poopyurinal edit a new file, add the two lines to it, and save.
The do
chmod +x ????
Where ??? is the name of the file you just created
Then make that file name the name of the exec script.
@poopyurinal ok, make a two line script to execute both commands, and use that script as the exec script in the service