YAPi0 Installer Stretch Lite

[sdetweil]

@bdream said in YAPi0 Installer Stretch Lite:

pm2 show mm

correct,

its called MagicMirror

App name | id | version |
MagicMirror | 0 | 2.8.0 |

says its running…

show me pm2 logs

you can also use the id, instead of the name

pm2 start 0,
pm2 stop 0,
pm2 show 0…

etc

[bdream]

here you are
last 3 rows coming multiple times

[sdetweil]

@bdream ok, there are two logs… error and out…

maybe best to do

cd ~/MagicMirror
pm2 stop 0
npm start

[bdream]

pi@RasPiZeroW:~ $ cd ~/MagicMirror/
pi@RasPiZeroW:~/MagicMirror $ pm2 stop 0
[PM2] Applying action stopProcessId on app [0](ids: 0)
[PM2] [MagicMirror](0) ✓
┌─────────────┬────┬─────────┬──────┬─────┬─────────┬─────────┬────────┬─────┬────────┬──────┬──────────┐
│ App name    │ id │ version │ mode │ pid │ status  │ restart │ uptime │ cpu │ mem    │ user │ watching │
├─────────────┼────┼─────────┼──────┼─────┼─────────┼─────────┼────────┼─────┼────────┼──────┼──────────┤
│ MagicMirror │ 0  │ 2.8.0   │ fork │ 0   │ stopped │ 31      │ 0      │ 0%  │ 0 B    │ pi   │ disabled │
└─────────────┴────┴─────────┴──────┴─────┴─────────┴─────────┴────────┴─────┴────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@RasPiZeroW:~/MagicMirror $ npm start

> magicmirror@2.8.0 start /home/pi/MagicMirror
> sh run-start.sh

/home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! magicmirror@2.8.0 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.8.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-09-25T17_26_03_649Z-debug.log
pi@RasPiZeroW:~/MagicMirror $

[sdetweil]

@bdream

you MUST install the graphical UI desktop on the pi, right? MM uses graphics to display the screen.

[bdream]

hmm, I guess I have to investigate about this in a few weeks.

So far many thanks for your help here. Will have a look later today and see what can I handle. Otherwise later. I have to run for a meeting now.

[bdream]

@sdetweil said in YAPi0 Installer Stretch Lite:

graphical UI desktop on the pi
I wonder. I understood Pi0 don’t need to have UI installed. therefor I installed the light raspbian image - maybe I’m wrong :confounded_face:

Do I have to install lightdm or other?

And then I assume use raspi-config to boot to desktop?

[sdetweil]

@bdream you can do node serveronly , instead of npm start…

for pm2, edit installers/mm.sh and change npm start to node serveronly

then pm2 restart 0

others have had success at running UI on p0 as well…

make sure u change config/config.js to allow other machines to connect
to allow all

address: “”,
and
ipWhitelist: [],

[bdream]

Í’m back now and started to work further on my Pi0 with MM installation.

I tried to get UI desktop running by installing lightdm.
Then reconfigured Boot option to start Desktopn and Auotologin.
After reboot, wich looks good, PI starts an give Debian logon screen.

How to autologon?

After I put in my credentials pi and raspberry I stuck in login-loop.

[bdream]

Any idea what to do?
Maybe Pi0 is not the Hardware MM will run good. Especialy in regards to upcoming updates :dizzy_face:
But this small device will give more oportunities for nice looking projects based on MM :grinning_face_with_smiling_eyes:

[sdetweil]

@bdream others have made it work… you may have to reinstall the base raspian image to get the graphical desktop running properly…

I don’t have one of these pi0 devices to test with

[bdream]

@sdetweil many thanks for your guidance.
I thaught Pi0 must get installed without GUI :worried_face: my fault.
I will start again and see what happen.
I’ll let you know if success yur script!

[sdetweil]

@bdream U can run it in serveronly mode

Have to edit the installers/mm.sh
Or run_start.sh to do

node serveronly

The use browser from some other system

[bdream]

@sdetweil Raspbian Buster with desktop image already written to the sc-card.
will see the time I have to work on it next time.

Stuff arount serveronly and using other browser is to far from me at the moment :unamused_face:

[sdetweil]

@bdream ok… there is only one MM install… but two ways to run it… so, no problem

[bdream]

@sdetweil many thanks!!

[bdream]

@sdetweil may I come back to you :smiling_face_with_halo:
I run new installation from scratch on my Rpi0.
Raspian Buster with desktop
updated and upgraded and so on
run your script

 bash -c "$(curl -sL https://www.dropbox.com/s/rlh710ng0zwv3vp/raspberry.sh?dl=0)"

:
:
Node.js installation Done! version=v10.15.2
:
:
npm WARN npm npm does not support Node.js v10.15.2
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/bin/npx -> /usr/local/lib/node_modules/npm/bin/npx-cli.js
+ npm@6.12.0
added 430 packages from 839 contributors in 328.327s
npm installation Done! version=V6.12.0
:
:
Cloning MagicMirror Done!
Installing dependencies ...
npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.

> electron-chromedriver@1.8.0 install /home/pi/MagicMirror/node_modules/electron-chromedriver
> node ./download-chromedriver.js

successfully dowloaded and extracted!

> electron@3.0.13 postinstall /home/pi/MagicMirror/node_modules/electron
> node install.js

Downloading tmp-3996-1-SHASUMS256.txt-3.0.13
[============================================>] 100.0% of 4.79 kB (4.79 kB/s)

> magicmirror@2.9.0 install /home/pi/MagicMirror
> cd vendor && npm install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

added 82 packages from 57 contributors and audited 220 packages in 139.709s
found 5 vulnerabilities (4 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> magicmirror@2.9.0 postinstall /home/pi/MagicMirror
> sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts

We'll remove from the repository the css/custom.css
This script apply git update-index --skip-worktree css/custom.css
rm 'css/custom.css'
MagicMirror installation successful!

> magicmirror@2.9.0 install-fonts /home/pi/MagicMirror
> cd fonts && npm install

added 1 package from 1 contributor and audited 1 package in 29.697s
found 0 vulnerabilities

npm WARN grunt-stylelint@0.11.1 requires a peer of stylelint@^10.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN acorn-jsx@5.1.0 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.

added 1051 packages from 1314 contributors and audited 3475 packages in 1848.766s
found 28 vulnerabilities (1 low, 1 moderate, 26 high)
  run `npm audit fix` to fix them, or `npm audit` for details
Dependencies installation Done!
setting up initial config.js
Check plymouth installation ...
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.
Splashscreen: Theme copied successfully.
Splashscreen: Changed theme to MagicMirror successfully.
Do you want use pm2 for auto starting of your MagicMirror (y/N)?y
install and setup pm2
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules/pm2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

Created symlink /etc/systemd/system/multi-user.target.wants/pm2-pi.service → /etc/systemd/system/pm2-pi.service.
[PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
[PM2] PM2 Successfully daemonized
[PM2][WARN] Applications MagicMirror not running, starting...
[PM2] App [MagicMirror] launched (1 instances)
┌────┬─────────────────────────┬─────────┬─────────┬──────────┬────────┬──────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name                    │ version │ mode    │ pid      │ uptime │ ↺    │ status   │ cpu      │ mem      │ user     │ watching │
├────┼─────────────────────────┼─────────┼─────────┼──────────┼────────┼──────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror             │ 2.9.0   │ fork    │ 4228     │ 3s     │ 0    │ online   │ 0%       │ 2.4mb    │ pi       │ enabled  │
└────┴─────────────────────────┴─────────┴─────────┴──────────┴────────┴──────┴──────────┴──────────┴──────────┴──────────┴──────────┘
[PM2] Saving current process list...
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2
Do you want to disable the screen saver? (y/N)?y

We're ready! Run DISPLAY=:0 npm start from the ~/MagicMirror directory to start your MagicMirror.


pi@RasPiZeroW:~ $ cd MagicMirror/
pi@RasPiZeroW:~/MagicMirror $ DISPLAY=:0 npm start

> magicmirror@2.9.0 start /home/pi/MagicMirror
> sh run-start.sh

additional

pi@RasPiZeroW:~/MagicMirror $ npm audit fix
npm WARN acorn-jsx@5.1.0 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN grunt-stylelint@0.11.1 requires a peer of stylelint@^10.0.0 but none is installed. You must install peer dependencies yourself.

+ helmet@3.21.1
+ lodash@4.17.15
added 8 packages from 7 contributors, removed 5 packages and updated 22 packages in 808.897s
fixed 28 of 28 vulnerabilities in 3475 scanned packages

Do you want use pm2 for auto starting of your MagicMirror (y/N)?y

MM is not coming on the screen
I did:

pi@RasPiZeroW:~/MagicMirror $  pm2 ls
┌────┬─────────────────────────┬─────────┬─────────┬──────────┬────────┬──────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name                    │ version │ mode    │ pid      │ uptime │ ↺    │ status   │ cpu      │ mem      │ user     │ watching │
├────┼─────────────────────────┼─────────┼─────────┼──────────┼────────┼──────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror             │ 2.9.0   │ fork    │ 20451    │ 64s    │ 520  │ online   │ 0%       │ 2.5mb    │ pi       │ enabled  │
└────┴─────────────────────────┴─────────┴─────────┴──────────┴────────┴──────┴──────────┴──────────┴──────────┴──────────┴──────────┘
pi@RasPiZeroW:~/MagicMirror $  pm2 restart mm
Use --update-env to update environment variables
[PM2][ERROR] Process mm not found
pi@RasPiZeroW:~/MagicMirror $  cd installers/
pi@RasPiZeroW:~/MagicMirror/installers $  nano mm.sh
pi@RasPiZeroW:~/MagicMirror/installers $ cd ..
pi@RasPiZeroW:~/MagicMirror $ pm2 restart 0
Use --update-env to update environment variables
[PM2] Applying action restartProcessId on app [0](ids: 0)
[PM2][ERROR] Process 0 not found
pi@RasPiZeroW:~/MagicMirror $ cd installers/
pi@RasPiZeroW:~/MagicMirror/installers $ nano mm.sh
pi@RasPiZeroW:~/MagicMirror/installers $ pm2 start mm.sh
[PM2] Starting /home/pi/MagicMirror/installers/mm.sh in fork_mode (1 instance)
[PM2] Done.
┌────┬─────────────────────────┬─────────┬─────────┬──────────┬────────┬──────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name                    │ version │ mode    │ pid      │ uptime │ ↺    │ status   │ cpu      │ mem      │ user     │ watching │
├────┼─────────────────────────┼─────────┼─────────┼──────────┼────────┼──────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror             │ 2.9.0   │ fork    │ 16261    │ 61s    │ 4340 │ online   │ 0%       │ 2.5mb    │ pi       │ enabled  │
│ 1  │ mm                      │ 2.9.0   │ fork    │ 16293    │ 1s     │ 0    │ online   │ 0%       │ 2.5mb    │ pi       │ disabled │
└────┴─────────────────────────┴─────────┴─────────┴──────────┴────────┴──────┴──────────┴──────────┴──────────┴──────────┴──────────┘
pi@RasPiZeroW:~/MagicMirror/installers $ pm2 start mm.sh
[PM2][ERROR] Script already launched, add -f option to force re-execution

Can you please give me a hint what my failer in thinking is?
What is missing and what wxactly do I need to do?

Many thanks! :grinning_face:

[sdetweil]

@bdream ok, a few things…

1. i need to fix the words at the end of install, cause if you said yes to pm2, then don’t do npm start
2. then u went and did a manual add of another thing for pm2…

so,

 pm2 stop mm
 pm2 delete mm

then

pm2  stop MagicMirror

then lets try manually

cd ~/MagicMirror
npm start 

you should see the messages from the mirror running

please advise

[bdream]

Thias is you have to work on:
@sdetweil said in YAPi0 Installer Stretch Lite:

i need to fix the words at the end of install, cause if you said yes to pm2, then don’t do npm start

I do

pi@RasPiZeroW:~ $  pm2 stop mm
[PM2][ERROR] Process mm not found

not necasarry

pm2 delete mm

pi@RasPiZeroW:~ $ pm2  stop MagicMirror
[PM2] Applying action stopProcessId on app [MagicMirror](ids: 0)
[PM2] [MagicMirror](0) ✓
┌────┬────────────────────┬──────────┬──────┬──────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status   │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror        │ fork     │ 223  │ stopped  │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴──────────┴──────────┴──────────┘

pi@RasPiZeroW:~/MagicMirror $ npm start

> magicmirror@2.9.0 start /home/pi/MagicMirror
> sh run-start.sh

nothing happen

[sdetweil]

@bdream weird… now have same problem on two systems…

try this

cd ~/MagicMirror
node serveronly

the connection url will be shown

then connect to that url from a browser on another system