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

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”

sdetweil

@tve weird

TvE

@sdetweil Yep (but I get exposed to that type of behavior daily :-) )

I have also found the DEBUG setting in the conf file:

logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"], // Add "DEBUG" for even more logging

And am tcpdumping the traffic as well

sudo tcpdump -i wlan0 -w tcpdump-wlan.pcap && sudo tcpdump -i eth0 -w tcpdump-eth.pcap &

So let’s see what a bisect approach to disabling the “services” leads to

sdetweil

@tve yeh, sorry on debug. lots of calendar stuff

TvE

@sdetweil Don’t worry about “debug” I just had to read the config in stead of skipping over that part

I have now reverted to my original config and will enable the different service in bisect style.

/*
TvE test log (on legacy OS)
Re-configured services resulting in crash:
  1 calendar
  2 openweather_current
  3 openweather_forecast
  4 news

A: Sample config
    => 11h and still OK

B: Enable DEBUG log level

C: Disable 2+3 (openweather) Enable 1+4
    => 14 h and still OK

D: Enable 2+3 (openweather) + disable 1+4 (news & calendar)
    => ongoing
*/

So in a few days I should know what’s triggering the issue…

TvE

Hmm so my latest config ran for more than 2 days.

I’m now reverting to the initial config (enabling all four config-changes) and then time will tell