After removing batteries from Envoy console and unplugging it....and then 
sudo reboot of Rpi this is what I get.

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available
Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console
Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable to 
wake up Vantage console (<class 'weewx.WakeupError'>)
Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 26 12:14:50 raspberrypi weewx[494]:     ****  Exiting...
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
connected: 10.1.1.155::38928 (TCP)
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions)
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
Jan 26 12:14:54 raspberrypi kernel: [   29.111831] Under-voltage detected! 
(0x00050005)
Jan 26 12:15:01 raspberrypi kernel: [   35.351863] Voltage normalised 
(0x00000000)
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.68
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.106.65.219
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 202.78.240.38
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.69
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 203.86.206.43
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.185.18
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.177.18
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 202.46.179.18
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.34
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
2407:f100:0:4::3
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.48
Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 130.217.226.51
Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed
Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.e1bd49e9 does not match aorg 0000000000.00000000 from 
server@103.239.8.22 xmt 0xdff6172a.80071bf6
Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 
59.082661s random time.
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.e1af360e does not match aorg 0000000000.00000000 from 
server@202.46.185.18 xmt 0xdff6172a.80d85adc
Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
27min 28.579939s random time.
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.d7adc312 does not match aorg 0000000000.00000000 from 
server@130.217.226.51 xmt 0xdff6172a.7d37a242
Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)

Next should I try deleting future records as recommended in the "generated 
but not updated" section of the user guide. 

pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx version 
3.8.2
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8'
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up console
Jan 26 12:25:05 raspberrypi weewx[1810]: import of driver failed: Unable to 
wake up Vantage console (<class 'weewx.WakeupError'>)
Jan 26 12:25:05 raspberrypi weewx[1810]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 26 12:25:05 raspberrypi weewx[1810]:     ****  Exiting...
Jan 26



On Saturday, 26 January 2019 11:51:41 UTC+13, gjr80 wrote:
>
> Yes, you appear to be getting loop packets. Corrupt station memory usually 
> results in loop packets continuing to come through but there are no archive 
> records coming from the logger. If you are using hardware record generation 
> then WeeWX gets no archive records, nothing is saved to database but 
> reports are still generated and anything 'loop based' still goes on. The 
> proof will be a longer console output (are there any archive records?) or a 
> longer log extract.
>
> If corrupt station memory it will be unrelated to any perceived RPi power 
> issues.
>
> Gary
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to