Read the statement by Michael Teeuw here.
MMM-NewsFeedTicker.
-
@ankonaskiff17 remember that we deleted old libraries in 2.16 , many modules didn’t document that they were needed, and SO, we end up with a crash
see the messages where u start MM, and look for ‘module not found’ and then npm install those in the MM folder …
probably one of
request
rrule-alt
valid-url -
-
@greedyvegan show me the messages from mm npm start
-
@sdetweil show me the message from npm start
after starting mm v2.26.0 it says
loading config…
[DEBUG] config template file not exists, no envsubst
loading module helpers…
no helper found… initializing new module helper
then… -
@greedyvegan that says you have an instance running already, do
pm2 status
then
pm2 stop all
then
pm2 start xx
xx is the number or name on the row
-
@sdetweil
which row? -
@greedyvegan share the output of
pm2 status -
@sdetweil
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ fork │ 29 │ stopped │ 0% │ 0b │
│ 2 │ mm │ fork │ 0 │ stopped │ 0% │ 0b │
│ 1 │ run-start │ fork │ 0 │ stopped │ 0% │ 0b │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
-
@greedyvegan hm…
run thisps -ef | grep MagicMirror | awk '{print $2}` | xargs sudo kill -9
the. try. npm start
-
nothing happened after that, it returned “>” and the cursor