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 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!!
-
@sdetweil Yeah - that’s perfect (and expected)
I really have (now stopped) wondering what happened initially :-)@thgmirror
I made a quick test where I have removed the power to the fan to see how much that changes the temperature (aka a passive cooling test).- After ca. one hour the temperature rises to a max of 57-58 degrees centigrades
- For the next hour the temperature is not rising any more
- Thus a reduction of ~6K
NB.: I have now removed the lid to see how big (small) a difference that makes
-
So - without the lid I get another 2K as - after 15 min - the temperature stabilized around 54-55 degrees centigrades
* Passive cooling lid on : 63 -> 58 = -5 * Passive cooling lid off : 63 -> 55 = -8 * Active cooling lid on : 63 -> 49 = -14 * Active cooling lid off : 63 -> 42 = -21 -
@TvE I am in the same spot as you.
Raspberry Pi 3b+
Fresh installed Raspbian Bullseye 11
Fresh install of MM with vanilla config and modules - crashes every minute and restarts itself. Are you saying that the config might be the problem?0|MagicMirror | Launching application. 0|MagicMirror | [18725:0322/102613.376542:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization 0|MagicMirror | [18766:0322/102613.700219:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process. 0|MagicMirror | [22.03.2022 10:26.16.088] [LOG] 0|MagicMirror | Create new calendarfetcher for url: http://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics - Interval: 300000 0|MagicMirror | [22.03.2022 10:26.16.175] [LOG] 0|MagicMirror | Create new newsfetcher for url: https://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000 0|MagicMirror | [22.03.2022 10:26.16.248] [INFO] 0|MagicMirror | Checking git for module: default 0|MagicMirror | [22.03.2022 10:26.17.014] [INFO] 0|MagicMirror | Newsfeed-Fetcher: Broadcasting 61 items. 0|MagicMirror | [22.03.2022 10:26.17.522] [INFO] 0|MagicMirror | Calendar-Fetcher: Broadcasting 10 events. 0|MagicMirror | [22.03.2022 10:27.33.823] [LOG] Shutting down server... 0|MagicMirror | [22.03.2022 10:27.33.833] [LOG] Stopping module helper: updatenotification 0|MagicMirror | [22.03.2022 10:27.33.835] [LOG] Stopping module helper: calendar 0|MagicMirror | [22.03.2022 10:27.33.848] [LOG] Stopping module helper: newsfeed 0|MagicMirror | [18692:0322/102733.909781:ERROR:zygote_communication_linux.cc(276)] Failed to send GetTerminationStatus message to zygote 0|MagicMirror | [18692:0322/102733.942607:ERROR:zygote_communication_linux.cc(276)] Failed to send GetTerminationStatus message to zygote 0|MagicMirror | [18692:0322/102733.958362:ERROR:network_service_instance_impl.cc(916)] Network service crashed, restarting service. 0|MagicMirror | [18692:0322/102733.974458:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=1002 0|MagicMirror | [18692:0322/102733.982862:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=1002 0|MagicMirror | [18692:0322/102733.989821:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=1002 0|MagicMirror | [18692:0322/102733.998527:ERROR:gpu_process_host.cc(962)] GPU process launch failed: error_code=1002 0|MagicMirror | > magicmirror@2.18.0 start 0|MagicMirror | > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js 0|MagicMirror | [22.03.2022 10:27.42.385] [LOG] 0|MagicMirror | Starting MagicMirror: v2.18.0 0|MagicMirror | [22.03.2022 10:27.42.407] [LOG] 0|MagicMirror | Loading config ... 0|MagicMirror | [22.03.2022 10:27.42.421] [LOG] 0|MagicMirror | Loading module helpers ... 0|MagicMirror | [22.03.2022 10:27.42.427] [LOG] 0|MagicMirror | No helper found for module: alert. 0|MagicMirror | [22.03.2022 10:27.42.463] [LOG] -
@TvE That is my experimental setup:
