|
Post by pagerman on Apr 21, 2021 11:51:49 GMT -8
pi@SwitchDocLabs:~ $ sudo vcgencmd measure_temp temp=43.3'C pi@SwitchDocLabs:~ $
|
|
|
Post by pagerman on Apr 21, 2021 12:04:59 GMT -8
Does the file /etc/resolvconf.conf have 127.0.0.1 commented out? It should - if not it will always overwrite the the resolv.conf file. GNU nano 3.2 /etc/resolvconf.conf # Configuration for resolvconf(8) # See resolvconf.conf(5) for details resolv_conf=/etc/resolv.conf # If you run a local name server, you should uncomment the below line and # configure your subscribers configuration files below. #name_servers=127.0.0.1 # Mirror the Debian package defaults for the below resolvers # so that resolvconf integrates seemlessly. dnsmasq_resolv=/var/run/dnsmasq/resolv.conf pdnsd_conf=/etc/pdnsd.conf unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
|
|
|
Post by pagerman on Apr 24, 2021 11:19:13 GMT -8
Well, thought this was sorted. It ran perfect for 3 days, however the AQI stopped reporting. So I did a restart. Not power off/on, a restart from the Pi menu. It totally crashed again within 2 hours. I had to go out and pull power and reapply. This is maddening.
|
|
|
Post by pagerman on Apr 24, 2021 12:57:01 GMT -8
I have ordered a new 3.5A power supply. That's the only thing that hasn't been changed. We will see.
|
|
|
Post by pagerman on Apr 27, 2021 17:12:18 GMT -8
New PS installed.
|
|
|
Post by pagerman on Apr 28, 2021 2:55:39 GMT -8
And. IT HAS CRASHED YET AGAIN. I am at my wits end. EVERYTHING has been replaced. I need help. When it crashes it no longer updates WeartherSTEM and this is what I get when I try to access via VNC or a web browser: Attachments:
|
|
|
Post by pagerman on Apr 28, 2021 5:27:21 GMT -8
Constant crashes today. I believe I will give up. Does anyone want to buy this station from me?
|
|
|
Post by Jason on Apr 28, 2021 7:09:59 GMT -8
I'll buy it. Let's work out details in DM.
Thanks,
Jason
|
|
|
Post by SDL on Apr 28, 2021 7:15:22 GMT -8
And. IT HAS CRASHED YET AGAIN. I am at my wits end. EVERYTHING has been replaced. I need help. When it crashes it no longer updates WeartherSTEM and this is what I get when I try to access via VNC or a web browser: We replied to your PM. We need to swap out the SkyWeather2 board too. If you aren't running SkyWeather2 at all, does the Pi crash? I'm wondering if it has something to do with your router and the Raspberry Pi 4 OS Interaction. While we haven't seen hard crashes, we have seen some weird interactions with access point and the Raspberry Pi 4B WiFi. Do you have an older Pi to try? BP
|
|
dow4hurst
Full Member
SkyWeather2 Newbie
Posts: 117
|
Post by dow4hurst on Apr 28, 2021 16:32:58 GMT -8
Pagerman, I don't know if you want to try anything else until you switch out the SkyWeather2 board or sell the device. But, I was thinking it might be helpful to know if you have any specific messages showing up in /var/log/messages or /var/log/kern.log after the crash occurs. If you have a ssh session running, the kernel may continue passing packets and allow you to examine these files. If you run
tail -f /var/log/messages in an ssh session, after the pi is rebooted, you will have at least the last messages showing on your screen when it crashes. I'm wondering if you are getting a firmware transaction error like I was having, or if you experience something different. A new connection may not be possible if the kernel is crashed. Of the four major log files in /var/log:
daemon.log syslog messages kern.log
the messages log file was the most pertinent in what is showed for my particular problem, but any of those files may have information that would show something related to the crash. Dow Hurst
|
|
|
Post by pagerman on Apr 29, 2021 5:34:25 GMT -8
Ok. Here we go again. NEW SD card with NEW fresh install of V15 and updated to Version 025 of the software. Setup: On WiFi for now so I don't muck up any of the code. Connected fine. Sees all the sensors. Updating dash_app, WeatherSTEM and Wunderground at this time. Started at 8:21:55 local time. I'll keep checking on it.
ISSUES SO FAR: Neither SkyWeather2 or dash_app will start on reboot by themselves. I have edited the rc.local file as follows:
GNU nano 3.2 /etc/rc.local
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing.
# Print the IP address #_IP=$(hostname -I) || true #if [ "$_IP" ]; then # printf "My IP address is %s\n" "$_IP" #fi
#cd /home/pi/SDL_Pi_SkyWeather2 nohup sudo python3 /home/pi/SDL_Pi_SkyWeather2/SkyWeather2.py & chmod 666 nohup.out #cd dash_app nohup sudo python3 /home/pi/SDL_Pi_SkyWeather2/dash_app/index.py & chmod 666 nohup.out
exit 0
Yes, I tried it using the "cd" commands first, still no auto start.
Other than that, let's see how long it runs.
|
|
dow4hurst
Full Member
SkyWeather2 Newbie
Posts: 117
|
Post by dow4hurst on Apr 29, 2021 8:39:12 GMT -8
Pagerman, I think the nohup.out has to exist and be writable before that script runs properly. I had that same problem.
touch nohup.out
in each directory will at least create the file and have it owned by the pi user. The root user, which runs the scripts on boot, will be able to write to each nohup.out. Create the nohup.out files, reboot, and let us know if that worked. Dow
|
|
|
Post by SDL on Apr 29, 2021 14:18:21 GMT -8
Ha! There is a timing problem here. Dow, good job with that find.
Put a "sleep 5" between the two (and between the index and chmod) and get rid of the race there too.
Dow's solution will work too. I would suggest you uncomment the "cd" commands so the nohup.out is in the correct directory.
BP
|
|
|
Post by pagerman on Apr 29, 2021 16:34:15 GMT -8
Trying now.
|
|
|
Post by pagerman on Apr 29, 2021 16:39:29 GMT -8
Ha! There is a timing problem here. Dow, good job with that find. Put a "sleep 5" between the two (and between the index and chmod) and get rid of the race there too. Dow's solution will work too. I would suggest you uncomment the "cd" commands so the nohup.out is in the correct directory. BP That worked!!! Now, let's see how long it keeps running! Thank you.
|
|