Read the statement by Michael Teeuw here.
Every few hours I get "ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service"
-
@tve weird
-
@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
-
@tve yeh, sorry on debug. lots of calendar stuff
-
@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…
-
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
-
@sdetweil This is really getting intersting - I have now re-enabled all the config changes so I’m back to my initial config and have been running for four days without a problem.
I even reproduced the problem on two differerent physical Pi’s (to eliminate HW) before starting to dissect the config…
So for now I can only conclude that something external was triggering these crashes!
I can now go back to the latest OS and start adding more stuff to my config (and keep my fingers crossed that I no longer encounter what-ever it was…)
Thank you for your help!
-
@tve interesting. keep us informed…
-
@TvE Do you use some wires at the GPIO? For example a PIR-sensor? Than may be interferences causes the issue when an electronic device is around your PI.
Or it is the temperature? Check it with
vcgencmd measure_temp -
@sdetweil Will do!
@thgmirror Nope no PIR sensor (as in “not yet”)
My setup is as basic “Hello World!” as it can be (IMHO)
(The full config can be seen - as a diff to the sample - earlier in this thread)The pi have been placed horisontally on my desk during all this testing.
It is in a cabinet though (the one from the “startet kit”).I have measured the temperature (with my hand) and not been alarmed
Now I can validate my assumption based on your tip, thanx!pi@mirror:~ $ vcgencmd measure_temp temp=63.4'C
I have read that it’s possible to get add a cooling fin to the CPU, which is something I’ll look in to later (as I am also working on making a replacement for this guy, an image grabber [1].
You can no longer purchase it (and I can make more captures pr second on my pi) for 1/2 the price, I only need to add this thingy [2]
I have HelloWorld! for this, I “just” need to add- Capture to RAM disk in stead of USB
- Auto upload to an ftp share (or maybe change this to scp…)
- Maybe get the pi’s to netboot as well (as I need 10+ of the system)
But that’s completely irellevant to my MM problem ;-)
[1 ]https://www.epiphan.com/wp-content/uploads/2014/07/epiphan-vga2ethernet-brochure.pdf
[2] https://www.epiphan.com/products/avio-4k/ -
@tve 63.4 C? Could be less!
You can generate a simple protocol by using
crontab -e and enter@reboot echo “---------- start ----------” >> proto.txt
*/5 * * * * date >> proto.txt
1-56/5 * * * * vcgencmd measure_temp >> proto.txtwhich will write a timestamp and a celsius amount every 5 minutes…and an eyecatcher at every boot. Look after a while into the file.