Every few hours I get "ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service"

TvE

I initially posted this in the wrong categori (Modules -> Troubleshooting)
So if it looks familiar that’s why (sorry for the confusion…)

sdetweil

@tve the 1st two errors in the stderr log are shown as a bug in electron.

nothing we can do.

no idea on the rest.

which os image did u use?

lsb_release -a

I am using the legacy release on a pi3b and it has been running mm for 2 weeks now, uninterrupted.

TvE

@sdetweil Sorry - I forgot that (latest OS :-))

pi@magicmirror:~/MagicMirror/logs $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye
pi@magicmirror:~/MagicMirror/logs $

I was not worried about the two first errors as they are always there (if they were serious I suspect that I would not have been able to launch MM at all)

The legacy release - what’s that (I should try that release and see if I can get the same positive results as you)

…googled…
It must be this you’re referring to?
https://www.tomshardware.com/news/raspberry-pi-releases-legacy-os

I gotta try that OS tomorow and se if that’s better

sdetweil

@tve https://www.raspberrypi.com/software/operating-systems/

scroll down

TvE

@sdetweil
Test is now started on legacy PI OS - so by tomorrow I’ll know if I have a stable setup

Goal 1 = 4 h (my shortest runtime with bullseye)
Goal 2 = 16 h (my longest runtime with bullseye)
Goal 3 = 24 h (if I get here I can expect that it’ll continue for ever :-) )

TvE

Hmm - still unstable

After just 1,5 hours I get the same error

[1229:0301/105243.836236:ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service.

Start test at 08:28
[01.03.2022 08:28.26.868] [LOG]   Starting MagicMirror: v2.18.0
...
Problem kicks in at 10:52
[01.03.2022 10:52.43.788] [LOG]   Shutting down server...

Could it really be problematic that I have configured both wlan as well as the eth interface??? (that would be hard to accept…)

Currently I am using eth, but prepared wlan as that’s what I’ll use when I “go to production”.

sdetweil

@tve well, address:“0.0.0.0”

means listen on ALL interfaces.

I use it on my pi w both enabled, but only Ethernet connected. ( and wifi not configured)

never has ‘crashed’

you could change to just the ethernet address

address:“192.168.?.?”

whatever that address is.

ifconfig

will show u
or
ip addr

TvE

@sdetweil OK - good point, that’s worth trying
New test has started only listening on one IP :-)

TvE

Hmm crashed after 6,5h with the same error…

NB.: My symptom is the same as being reported here (though I’m not using a docker container)
https://github.com/electron/electron/issues/31675

Is there any way of increasing the verbosity in any logs to get more debugging info?

I’m now perforing a new test:

Reverting to the default MM config
And tcpdump’ing the network traffic so I can correlate and maybe identify what triggers the network service crash

If it no longer crashes I’ll revert to my own config and retest (as it then must be related to that specific network traffic [no matter how unfair that seems]

TvE

Test with default config looks good 11h without a crash

[02.03.2022 07:43.20.529] [LOG]   Starting MagicMirror: v2.18.0
...
[02.03.2022 18:35.01.238] [INFO]  Calendar-Fetcher: Broadcasting 10 events.
And still running

Thus I must deduce that one of the two services I had configured was triggering the problem

I must enable my two changes individually to identify which is “bad”