@frustrated said in MagicMirror/node_modules/electron/dist/electron exited with signal SIGBUS:

I did do a reboot just to be sure everything updates.

yes, for sure… but did it work BEFORE rebooting??

anyhow…

you also have a backup of your mm, right?

if not, see
https://github.com/sdetweil/MagicMirror-backup-restore

and can be versioned with git …

@dathbe said in UnhandledPromiseRejectionWarning: TypeError: fetch failed:

Platform: Raspbian 12

Node Version: 18.19.0

MagicMirror Version: 2.27

Description:
I am seeing the following errors in my logs, though I’m not necessarily seeing any problems on my display (at least not regularly).

0|mm | 024-05-16 14:10:44.296] [ERROR] 2024-05-16T14:10:44 <error> (node:26446) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 97) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:11:12.283] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) UnhandledPromiseRejectionWarning: TypeError: fetch failed 0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11) 0|mm | (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:11:12.291] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 119) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | /home/username/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT 0|mm | [2024-05-16 14:12:49.844] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) UnhandledPromiseRejectionWarning: TypeError: fetch failed 0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11) 0|mm | 0|mm | (Use `electron --trace-warnings ...` to show where the warning was created) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:12:49.851] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:13:09.544] [ERROR] 2024-05-16T14:13:09 <error> (node:28645) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (/home/username/MagicMirror/node:internal/process/warning:60 writeOut)

It seems to come up most often when I load the MMM-Pinfo module in my config, though I have seen it at other times as well. The problem is that I don’t see enough information in these logs to find a source myself.

Steps to Reproduce: Load MM, usually with MMM-Pinfo module enabled.

If anyone has any ideas, that would be great.

pinfo doesn’t use fetch…

Sadly, best way is to comment out, or disabled:true
each module til you find the culprit

@Pade2204 i’m surprized that its running…

just to check

output of

grep version ~/MagicMirror/node_modules/electron/package.json

@sdetweil I am running raspbian (debian 11 bullseye) with no pending updates on a pi3B+.
I have cd’d into MagicMirror/fonts, run npm install and restarted the MM. No change. Still displays a square where there should be an icon.

@Dresch360

The Pi5 has new GPIO hardware. It is not compatible with software written for earlier Pi models.

So look at what gpio library is being called by the modules you are wanting to use.

I’ve been rewriting my own code to use gpiozero .
gpiozero works and isrecommend by raspberry pi foundation and works on older pis too.

Lgpio works on rpi5
Gpiod works on rpi5

Pigpio WILL NOT WORK
RPi.GIPO WILL NOT WORK

I haven’t tried rpi-lgpio which supposed to be a drop in replacement for rpi.gpio.

@OldSunGuy 1st image, round up current time, 6:49+21 mins = 7:10, sunrise time

second image, round up time 7:13, +10:05
=17:18. sunset time

@sdetweil Just letting you know that this fix corrected my issue where my calendar module (setup for iCal) would not show repeating events. The repeating events are showing again. Thanks.

@pencilsharpener I saw. thank you

@davismorehead I updated the installer (raspberry.sh) to use the

systemctl get-default

command instead of looking at the file…

thanks for the info

@sdetweil Thank you for all the help.
The mirror is at my family’s house. So I have to find a way to VPN connect myself to that.

I will come back to you asap.

@jbat66 I opened this issue, with a sample testcase

returned date incorrect caused by TZ rollover #610

@tacotaco

I know this is an old issue, but I had this happen to me while setting up MM on a Le Potato board.

Seems like a GPU issue, and you can bypass this by adding this snippet right before you call npm start:

export ELECTRON_DISABLE_GPU=1

In my case, I’m using PM2 to manage startup, so my ~/mm.sh file looks like this:

cd ./MagicMirror export ELECTRON_DISABLE_GPU=1 DISPLAY=:0 npm start

I don’t know the full extent of the issue, but I know that this works and allows me to run MM.

Hopefully this helps you and anyone else looking for this in the future.

@sdetweil “one event with recurring for f/s/s will be 3 events. 1 for each day”

Totally fine with that. That’s what I have now, but now I have much less typing.

@BKeyport generally a missing module will cause a black screen if it’s used in the node helper, which is where request would be used

@mumblebaj
As of version 2.24, Somebody added to spit this error message out when the 2nd parameter is not a callback function.

However, the following codes correct the missing parameter anyway, so it is unnecessary to regard it as ERROR, unless that self-correction logic is removed.
Even if there is a plan to drop out that correction logic, it’s still better to flag it as a “WARN” rather than an “ERROR”, I think so.

Anyway, the error message is just annoying, and not related to real “ERROR” . You can ignore it.

@ankonaskiff17 I use alt-spacebar every day

x64, pi, odoid, … under VMware… native…

never use vnc.

the windows key on my keyboard opens the menu too

@sdetweil Thanks Sam. I found the problem. It is related to a module I am running. Been debugging and when I disabled that module the display takes up the whole screen as it should.

The error is fix with : https://github.com/MichMich/MagicMirror/issues/3147

@videogame95 solved