On Thursday, December 22, 2016 at 9:36:20 PM UTC-5, Marc Aubry wrote: > > hi > it's rpi2 B+ so it should be 1G and the rpi is dedicated for weewx, i just > enable ssh and vncserver. > for the memory i have a lot of it according to 'top' command > > *top - 09:27:47 up 2:20, 2 users, load average: 0.07, 0.07, 0.07* > *Tasks: 143 total, 1 running, 142 sleeping, 0 stopped, 0 zombie* > *%Cpu(s): 0.8 us, 0.1 sy, 0.0 ni, 99.1 id, 0.0 wa, 0.0 hi, 0.0 si, > 0.0 st* > *KiB Mem: 947732 total, 358672 used, 589060 free, 42040 buffers* > *KiB Swap: 102396 total, 0 used, 102396 free. 182152 cached > Mem* > > below the output of ps aux | grep weewx > > *ps aux | grep weewx* > *root 608 6.1 3.4 86252 32480 ? Sl 07:08 8:41 python > /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf* > *pi 1425 0.0 0.1 4280 1852 pts/0 S+ 09:30 0:00 grep > --color=auto weewx* > > > i'll get back to strd skin but i had already this crash when i was setting > up and learning weewx so i doubt the skin is in cause. >> >> >> marc,
those memory numbers do not look unreasonable. you might want to look at the numbers for the standard skin versus the responsive skin. be sure to let weewx run for 5 or 6 archive intervals before you look at the memory numbers. i have been reviewing the driver code, and there is a chance that the driver is looping continuously, trying to get data from usb. please update to the latest wh23xx driver (v 0.8). update process is as you did before. this adds more logging that will help us determine if the usb comms are the problem. m -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
