@sdetweil for which chromium or which chromium-browswer I get nothing returned.
Read the statement by Michael Teeuw here.
Posts
-
RE: cannot get Raspberry pi 2 to run
-
RE: cannot get Raspberry pi 2 to run
lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster -
RE: cannot get Raspberry pi 2 to run
@sdetweil After I run the install script, what do I do. Since the script disables the screen saver and configures the Mirror to autostart I thought I would not need to do anything else. However, pm2 status all reveals that there is nothing running. I run pm2 status all and it is blank.
I am not sure if I should follow the process in the link below.
https://howchoo.com/g/ntcymzbimjv/how-to-install-magic-mirror-on-your-raspberry-piWhen I reboot the mirror I get the magicmirror2 logo showing up and it seems to be booting up but then the screen goes blank and I have nothing. It is almost like it reboots the pi.
-
RE: cannot get Raspberry pi 2 to run
@sdetweil Thanks for all the help. I have several pi4s I just want to use the model 2 because the mirror is a perfect application for the older computer.
-
RE: cannot get Raspberry pi 2 to run
@sdetweil Oh wow. Sorry for all the trouble. What a pain.
-
RE: cannot get Raspberry pi 2 to run
@sdetweil ```
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye -
RE: cannot get Raspberry pi 2 to run
/usr/bin/chromium-browser Illegal Instruction -
RE: cannot get Raspberry pi 2 to run
@theaddies The way I want to run the mirror is that it automatically opens and displays the mirror at boot. I sometimes see things for serveronly and I am not sure if that is what is being configured. I don’t think that is what I want.
-
RE: cannot get Raspberry pi 2 to run
@sdetweil I get this.
Ready to go! Please point your browser to: http://localhost:8080 Starting chromium browser now, have patience, it takes a minute ./run-start.sh: line 147: 1281 Illegal instruction "$b" -noerrdialogs -kiosk -start_maximized --new-window --site-per-process --no-zygote --no-sandbox --disable-infobars --app=http://localhost:$port --ignore-certificate-errors-spki-list --ignore-ssl-errors --ignore-certificate-errors --user-data-dir=$r 2> /dev/null -
RE: cannot get Raspberry pi 2 to run
@sdetweil It is slow, but I have been working on this for 12 hours so there is ample time for something to have worked.
pi@raspberrypi:~ $ pm2 logs --lines=50 [PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2 [PM2] PM2 Successfully daemonized [TAILING] Tailing last 50 lines for [all] processes (change the value with --lines option) /home/pi/.pm2/pm2.log last 50 lines: PM2 | 2023-04-07T18:26:05: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:26:45: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:27:25: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:28:09: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:28:57: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:29:49: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:30:28: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:31:08: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:31:08: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:31:09: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:31:48: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:31:48: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:31:49: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT] PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] starting in -fork mode- PM2 | 2023-04-07T18:32:28: PM2 log: App [MagicMirror:0] online PM2 | 2023-04-07T18:33:09: PM2 log: pm2 has been killed by signal, dumping process list before exit... PM2 | 2023-04-07T18:33:09: PM2 log: Deleting process 0 PM2 | 2023-04-07T18:33:09: PM2 log: Stopping app:MagicMirror id:0 PM2 | 2023-04-07T18:33:10: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGTERM] PM2 | 2023-04-07T18:33:12: PM2 log: pid=10286 msg=process killed PM2 | 2023-04-07T18:33:12: PM2 log: Exited peacefully PM2 | 2023-04-07T18:36:32: PM2 log: =============================================================================== PM2 | 2023-04-07T18:36:33: PM2 log: --- New PM2 Daemon started ---------------------------------------------------- PM2 | 2023-04-07T18:36:33: PM2 log: Time : Fri Apr 07 2023 18:36:33 GMT-0400 (Eastern Daylight Time) PM2 | 2023-04-07T18:36:33: PM2 log: PM2 version : 5.3.0 PM2 | 2023-04-07T18:36:33: PM2 log: Node.js version : 16.13.0 PM2 | 2023-04-07T18:36:33: PM2 log: Current arch : arm PM2 | 2023-04-07T18:36:33: PM2 log: PM2 home : /home/pi/.pm2 PM2 | 2023-04-07T18:36:33: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid PM2 | 2023-04-07T18:36:33: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock PM2 | 2023-04-07T18:36:33: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock PM2 | 2023-04-07T18:36:33: PM2 log: Application log path : /home/pi/.pm2/logs PM2 | 2023-04-07T18:36:33: PM2 log: Worker Interval : 30000 PM2 | 2023-04-07T18:36:33: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2 PM2 | 2023-04-07T18:36:33: PM2 log: Concurrent actions : 2 PM2 | 2023-04-07T18:36:33: PM2 log: SIGTERM timeout : 1600 PM2 | 2023-04-07T18:36:33: PM2 log: =============================================================================== -
RE: cannot find module
@sdetweil Thanks for the reply. I started over. I just made a posts where I ran your script and can’t get it to work. I don’t know how I ever got this thing working in the first place. I have 3 of them running and now I can’t anything to go. My other post is awaiting approval.
-
cannot get Raspberry pi 2 to run
Super frustrating experience trying to get MagicMirror up and running on a raspberry pi model 2 b. I tried to do the manual installation and got the error:
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash - ## Installing the NodeSource Node.js 16.x repo... ## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.or >So I went ahead and ran the script below:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"Everything seemed to work well and I get the message below.
[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 pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.when I type ‘pm2 start MagicMirror’ It says process started successfully, displays the table with id, name, node, etc and then just returns the prompt. Nothing happens. I’m super frustrated. I am going through all this due to a corrupted SD card but I didn’t have this kind of trouble getting it to work originally
I appreciate any help.
-
RE: cannot find module
Does duplicating the card duplicate the flaw or is the copy good? Or is there a way I can make a copy of the important parts of the OS without duplicating the card?
-
RE: cannot find module
@sdetweil My girfriends daughter pulls the plug on it. So yea, a power failure.
-
cannot find module
Everything worked fine and I don’t think I did anything. Then I get the error below.
pm2 status node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module './ranges/ltr' Require stack: - /usr/lib/node_modules/pm2/node_modules/semver/index.js - /usr/lib/node_modules/pm2/lib/Common.js - /usr/lib/node_modules/pm2/lib/Client.js - /usr/lib/node_modules/pm2/lib/API.js - /usr/lib/node_modules/pm2/lib/binaries/CLI.js - /usr/lib/node_modules/pm2/bin/pm2 at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/usr/lib/node_modules/pm2/node_modules/semver/index.js:39:13) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/usr/lib/node_modules/pm2/node_modules/semver/index.js', '/usr/lib/node_modules/pm2/lib/Common.js', '/usr/lib/node_modules/pm2/lib/Client.js', '/usr/lib/node_modules/pm2/lib/API.js', '/usr/lib/node_modules/pm2/lib/binaries/CLI.js', '/usr/lib/node_modules/pm2/bin/pm2' ] }I appreciate any help getting this sorted.
-
RE: EADDRINUSE: address already in use 127.0.0.1:8090
@sdetweil thanks for the reply but I have no idea what I see did
-
RE: EADDRINUSE: address already in use 127.0.0.1:8090
@sdetweil I suppose this makes sense but I killed it and it immediately restarted. I don’t know how to remove it.
-
RE: EADDRINUSE: address already in use 127.0.0.1:8090
@sdetweil I found /usr/bin node serveronly.
is that the culpirit?
-
RE: EADDRINUSE: address already in use 127.0.0.1:8090
@sdetweil Thanks for the reply. I think I did have 2 instances at one time, but I deleted the other one. It does not show up on pm2 status. Is there anything else to remove? Thansk.