MMM-PublicTransportHafas: Service Temporarily Unavailable

evroom

I did the update and it is looking much better now.
I reverted back to db (npm run query dbis working again).
Only one thing I noticed:

On display (last update 11:15)
11:08 +1.0333333333333334
11:28 +0

The 11:08 entry is in the past (maxUnreachableDepartures: 2,).
The +1.0333333333333334 is a bit too much :-)

MZ-BER

@KristjanESPERANTO I missed the npm ci. Now it is working as expected. Thank you 😊

KristjanESPERANTO

@evroom said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

The +1.0333333333333334 is a bit too much :-)

I just released version 3.0.1 to fix this 😀

evroom

@KristjanESPERANTO said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

I just released version 3.0.1 to fix this 😀

At this moment I see an entry in the past with +0.5.
Also saw +0.6.
When turning on debug, I only see delay values of 0, 60 and null, so I wonder where the current 0.5 comes from.
The values for when and plannedWhen all have a difference of 0 or 1 minute.

It seems that it only affects the first entry in the list, which in my case is the first unreachable in the past.
And it does not really bother me, but it still is odd.

Volkae

@KristjanESPERANTO

I did the update

cd ~/MagicMirror/modules/MMM-PublicTransportHafas
git pull
npm ci

but it still does not work.

Any idea??

Volkae

@Volkae

pi@magicmirror-buero:~/MagicMirror/modules/MMM-PublicTransportHafas $ npm ci
npm warn deprecated vbb-translate-ids@3.1.0: Deprecated. Use vbb-translate-ids@latest.
npm warn deprecated hafas-client@2.10.4: Deprecated. Use hafas-client@latest.

KristjanESPERANTO

@Volkae Looks like you don’t use my fork. I recommend deleting the module and install this: https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas

sdetweil

@KristjanESPERANTO said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

deleting the module and install

I think to be more clear, deleting the module folder

Volkae

@KristjanESPERANTO

I deleted the modul folder and made a new install. Now it works.

Thanks a lot!!

othomys

@KristjanESPERANTO
Thank you for your support. I hope to find some time this weekend to implement your suggestion.

othomys

@KristjanESPERANTO , it works. Thanks a lot. :-)

rotorax

Hi, thanks for your update.
I installed your git version and I had to install undici additionally. Is that correct?

The MM works but ended starting up again and agin:
0|mm | <— Last few GCs —>
0|mm | [17870:0x2a530000] 119266 ms: Mark-Compact (reduce) 126.9 (128.6) -> 126.4 (128.1) MB, pooled: 0 MB, 791.61 / 0.00 ms (+ 0.9 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 816 ms) (average mu = 0.190, current[17870:0x2a530000] 120521 ms: Mark-Compact 126.9 (128.1) -> 126.5 (128.6) MB, pooled: 0 MB, 1201.60 / 0.00 ms (average mu = 0.113, current mu = 0.043) allocation failure; scavenge might not succeed
0|mm | <— JS stacktrace —>
0|mm | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
0|mm | ----- Native stack trace -----
0|mm | /home/mirror/MagicMirror/node_modules/electron/dist/electron exited with signal SIGABRT

Im using a raspberry pi zero with 512 MB RAM which worked fine in the past.

Also some system information:
0|mm | [2025-02-03 08:57:53.254] [INFO] System information:
0|mm | ### SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; virtual: false
0|mm | ### OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+
0|mm | ### VERSIONS: electron: 32.2.7; used node: 22.13.1; installed node: 22.13.1; npm: 10.9.2; pm2: 5.4.3
0|mm | ### OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

Anyone have the same problem?

sdetweil

@rotorax how big is the swap space?

free -m

Will list that

rotorax

@sdetweil

while running and short time before crashing:
user:~ $ free -m
total used free shared buff/cache available
Mem: 426 217 99 19 109 132
Swap: 871 250 621

sdetweil

@rotorax OK try this

  export NODE_OPTIONS=--max-old-space-size=4096

before the npm start

if using pm2 then this goes in the script it launches,
using my setup
MagicMirror/installers/mm.sh

4096 may need to be adjusted

rotorax

@sdetweil thanks for the idea. I already had this code seen. But never implemented in my pm2 startup file.
I tried up to 512 (limit of the raspberry I have).

Thats the log I got:
0|mm | <— Last few GCs —>
0|mm | [22565:0x47124000] 127560 ms: Mark-Compact (reduce) 127.2 (128.1) -> 126.7 (128.3) MB, pooled: 0 MB, 731.03 / 0.01 ms (+ 36.3 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 896 ms) (average mu = 0.169, curren[22565:0x47124000] 128545 ms: Mark-Compact (reduce) 127.2 (128.3) -> 126.4 (127.8) MB, pooled: 0 MB, 832.78 / 0.00 ms (+ 1.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 860 ms) (average mu = 0.162, current
0|mm | <— JS stacktrace —>
0|mm | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
0|mm | ----- Native stack trace -----
0|mm | /home/mirror/MagicMirror/node_modules/electron/dist/electron exited with signal SIGABRT

I rolled back to the old config before the change of the MMM-PublicTransprtHafas and it run hours (unfortunately I don’t get any live data anymore with the old version)…

More ideas? ;) Grateful for every hint :)

sdetweil

@rotorax i am certain you have to have at LEAST 4096, not smaller, maybe 8192