Read the statement by Michael Teeuw here.
Every few hours I get "ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service"
-
@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'CI 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.
-
@thgmirror A cron based measuring is a good approach I’ll keep that in mind if I start to suspect temperature (or when I perform a load test my grabber-PI).
For now I do not think it can be temperature related as it’s very reliable around 60 degrees centigrade
pi@mirror:~ $ vcgencmd measure_temp temp=59.6'C -
@tve but see his post
https://forum.magicmirror.builders/topic/16485/temperature-of-a-rpi3
60 is bad if u can do 30!
-
@sdetweil said in Every few hours I get "ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service":
@tve but see his post
https://forum.magicmirror.builders/topic/16485/temperature-of-a-rpi3
60 is bad if u can do 30!
Great post(!)
(And here I thought that 60 was the normal/expected working temperature)
I think I’ll add a passive solution (or maybe even an active - but then there is a fan that will die)
(I have some other - rather expensive - equipment that died due to a dead fan, and unfortunately there was no way to measure the temperature - bad design…)I see these two obvious options:
- https://uk.rs-online.com/web/p/raspberry-pi-hats-add-ons/8679039
- https://uk.rs-online.com/web/p/raspberry-pi-hats-add-ons/2020449
The active solution might even add enough cooling even when the fan dies (as it seems that there is a passive “path for the heat” from the CPU
I should try both :-)What is to gain?:
I am aware that the warmer the chip the shorter it’s life
(I have complained to a vendor that one of their products got so warm that I burn myself if I touch the enclosure, but they insist that it’s expected - even though I have had to get at least three of my nine devices replaced!
I think it’s due to a bad design - hence my heat complaint…)The rule of thumb is something like this:
By increasing the device temperature by just 10°C, we have reduced the lifetime by over 2x
BTW: I have not seen any more network-service-instance-crashes, it’s still going strong after 8 days, really weird (but good!)…
-
63.4 C? Could be less!
I have now added one of these [1] to my RPI 3 and returned it to the enclosure (the “starter kit cabinet”).
The temperature is now 48-49 degrees centigrade after 30 min usage of MM.
So it reduces the temperature with ~14K - thats nice (if you don’t mind listening to a spinning fan which is actually fairly loud in at least 2 meters distance)…!I’ll try passive cooling later…
Oh! - and I had a 14 day uptime before powering off (the original reason for this thread :-)
[1] https://uk.rs-online.com/web/p/raspberry-pi-hats-add-ons/2020449
-
@TvE said in Every few hours I get "ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service":
Oh! - and I had a 14 day uptime before powering off (the original reason for this thread
nice!!
