Read the statement by Michael Teeuw here.
Cannot find module 'node-fetch' error with MMM-SoccerLiveScore
-
@sdetweil
Thank you for the quick reply.
Found that solution already in the forum.
Result is though:up to date, audited 1 package in 2s found 0 vulnerabilitiesAfter restarting the docker container, the error remains.
-
@codac then you didnt do the npm install in the correct module folder
and I assume you have to restart MM of the container to pick up the change -
root@04492d039b9f:/opt/magic_mirror/modules# cd MMM-SoccerLiveScore root@04492d039b9f:/opt/magic_mirror/modules/MMM-SoccerLiveScore# npm install node -fetch@2 up to date, audited 1 package in 1s found 0 vulnerabilitiesHow would I restart MM of the container?
pm2 is not set up.DISPLAY=:0 npm restart…results in
> magicmirror@2.26.0 restart > npm stop --if-present && npm start > magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js sh: 1: ./node_modules/.bin/electron: not found -
@codac seen this happening more
in the container again
in the MagicMirror folder donpm install electron@27.2.0 -
@sdetweil
sorry for the hussle, but this seems to never end :anguished_face:after running
npm install electron@27.2.0I tried to restart MM:
root@04492d039b9f:/opt/magic_mirror# DISPLAY=:0 npm restart > magicmirror@2.26.0 restart > npm stop --if-present && npm start > magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js /opt/magic_mirror/node_modules/electron/dist/electron: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory -
@codac yeh, seems that electron needs something from the container
do you know which container you are using?@karsten13 can u look at this
-
he must restart the container, this cannot be done from inside the container
so how was the container started? With
docker composeoderdocker run ...or? -
@karsten13 this
libgobject-2.0.so.0: cannot open shared object file: No such file or directorywill be fixed by container restart ?
-
I don’t now, the old electron process is still running
but we now nothing, how he started, in server only or with electron, which architecture, which host os, which hardware …
-
docker run -
@sdetweil
This error only comes up when trying to restart MM inside the docker.
When restarting the docker, this error wont show up. -
@karsten13
This is a server only setup. Docker runs on “Container Manager” of Synology. The Synology is a DS420+ running on an INTEL Celeron J4025. The OS is DSM of course. -
and how do you start/stop the container? With a WebUI or per command line?
-
@karsten13 WebUI
-
@codac and I think the electron error is just noise, as you must be running server only mode, whcih doesn’t use electron
-
I don’t know this WebUI, you have to restart the container or stop and start again, whatever the WebUI provides
-
and I think the electron error is just noise, as you must be running server only mode, whcih doesn’t use electron
yes, there is no electron installed
-
@karsten13 well restarting / stopping / starting is no problem. But the error just remains and doesnt go away…
-
@codac which error? the node-fetch or the lib error?
(@karsten13 we installed electron, my mistake… in docker, doah! )
-
@sdetweil the node-fetch error
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login