Not sure what you are asking here? 

sudo - shoul dnot be required to tail syslog, if running tail without sudo 
works then enjoy not having to type the 5 extra keystrokes, if it only 
works with sudo then so be it, you will have to type the extra 5 keystrokes 
each time :)

named[954] lines - not sure but looks like some sort of domain name server 
(DNS) issue. It may or may not be of consequence. Almost certainly not a 
weeWX issue.

weewx[18057] lines - this is exactly what you should be seeing; records 
added to database, reports being generated, images (plots) being generated. 
Copying 0 files is normal. This sequence should be repeated every 5 
minutes. As I said two posts back the only other check is to verify the 
generated files (and plots) are as they should be.

Gary

On Friday, 8 December 2017 21:17:07 UTC+10, Ray wrote:
>
> Tried the tail -f /var/log/syslog command again but with sudo:-
> ray@ray-Aspire-5735:~$ sudo tail -f /var/log/syslog
> [sudo] password for ray: 
> Dec  8 12:06:59 ray-Aspire-5735 named[954]: network unreachable resolving 
> './NS/IN': 2001:dc3::35#53
> Dec  8 12:06:59 ray-Aspire-5735 named[954]: network unreachable resolving 
> './NS/IN': 2001:7fe::53#53
> Dec  8 12:06:59 ray-Aspire-5735 named[954]: network unreachable resolving 
> './NS/IN': 2001:500:2::c#53
> Dec  8 12:06:59 ray-Aspire-5735 named[954]: DNS format error from 
> 198.97.190.53#53 resolving ./NS: non-improving referral
> Dec  8 12:06:59 ray-Aspire-5735 named[954]: FORMERR resolving './NS/IN': 
> 198.97.190.53#53
> Dec  8 12:10:42 ray-Aspire-5735 weewx[18057]: manager: Added record 
> 2017-12-08 12:10:00 CET (1512731400) to database 'weewx.sdb'
> Dec  8 12:10:42 ray-Aspire-5735 weewx[18057]: manager: Added record 
> 2017-12-08 12:10:00 CET (1512731400) to daily summary in 'weewx.sdb'
> Dec  8 12:10:42 ray-Aspire-5735 weewx[18057]: cheetahgenerator: Generated 
> 14 files for report StandardReport in 0.46 seconds
> Dec  8 12:10:43 ray-Aspire-5735 weewx[18057]: imagegenerator: Generated 12 
> images for StandardReport in 0.27 seconds
> Dec  8 12:10:43 ray-Aspire-5735 weewx[18057]: copygenerator: copied 0 
> files to /var/www/html/weewx
>  Of course *I* don't understand, but one of you experts may::?
>
> On Friday, 8 December 2017 12:06:56 UTC+1, Ray wrote:
>>
>> Don't understand much of the log entries but noticed this one - 
>> Dec  8 11:55:37 ray-Aspire-5735 weewx[18057]: fousb: unstable read: 
>> blocks differ for ptr 0x006da0
>> What's that about?
>> Ray
>>
>> On Friday, 8 December 2017 11:46:13 UTC+1, Ray wrote:
>>>
>>> Did all you suggested Gary then, with weewx running again tried to gedit 
>>> the syslog but got no display from$ sudo gedit syslog (as I THINK I did it 
>>> previously) so did :-
>>>
>>> ray@ray-Aspire-5735:~$  tail -f /var/log/syslog
>>> Dec  8 11:35:06 ray-Aspire-5735 weewx[18057]: engine: Starting up weewx 
>>> version 3.8.0
>>> Dec  8 11:35:07 ray-Aspire-5735 weewx[18057]: fousb: synchronising to 
>>> the weather station (quality=1)
>>> Dec  8 11:39:03 ray-Aspire-5735 gnome-session[1436]: 
>>> (zeitgeist-datahub:2572): Gtk-WARNING **: Attempting to read the recently 
>>> used resources file at '/home/ray/.local/share/recently-used.xbel', but the 
>>> parser failed: Failed to open file 
>>> '/home/ray/.local/share/recently-used.xbel': Permission denied.
>>> Dec  8 11:39:03 ray-Aspire-5735 gnome-session[1436]: (nautilus:1773): 
>>> Gtk-WARNING **: Attempting to read the recently used resources file at 
>>> '/home/ray/.local/share/recently-used.xbel', but the parser failed: Failed 
>>> to open file '/home/ray/.local/share/recently-used.xbel': Permission denied.
>>> Dec  8 11:39:15 ray-Aspire-5735 weewx[18057]: fousb: changing data 
>>> format from 1080 to 3080
>>> Dec  8 11:39:15 ray-Aspire-5735 weewx[18057]: manager: Added record 
>>> 2017-12-08 11:39:15 CET (1512729555) to database 'weewx.sdb'
>>> Dec  8 11:39:16 ray-Aspire-5735 weewx[18057]: manager: Added record 
>>> 2017-12-08 11:39:15 CET (1512729555) to daily summary in 'weewx.sdb'
>>> Dec  8 11:39:16 ray-Aspire-5735 weewx[18057]: engine: Starting main 
>>> packet loop.
>>> Dec  8 11:39:19 ray-Aspire-5735 weewx[18057]: fousb: station status 
>>> {'unknown': 0, 'lost_connection': 0, 'rain_overflow': 0} (0)
>>> Dec  8 11:39:27 ray-Aspire-5735 wpa_supplicant[942]: wlp3s0: WPA: Group 
>>> rekeying completed with 00:21:f2:0f:f6:b0 [GTK=CCMP]
>>> Dec  8 11:40:19 ray-Aspire-5735 weewx[18057]: manager: Added record 
>>> 2017-12-08 11:40:00 CET (1512729600) to database 'weewx.sdb'
>>> Dec  8 11:40:19 ray-Aspire-5735 weewx[18057]: manager: Added record 
>>> 2017-12-08 11:40:00 CET (1512729600) to daily summary in 'weewx.sdb'
>>> Dec  8 11:40:21 ray-Aspire-5735 weewx[18057]: cheetahgenerator: 
>>> Generated 14 files for report StandardReport in 1.38 seconds
>>> Dec  8 11:40:22 ray-Aspire-5735 weewx[18057]: imagegenerator: Generated 
>>> 36 images for StandardReport in 1.46 seconds
>>> Dec  8 11:40:22 ray-Aspire-5735 weewx[18057]: copygenerator: copied 9 
>>> files to /var/www/html/weewx
>>>
>>> that is now running in a separate terminal window ( I didn't EVEN know 
>>> that you could run more than one terminal!)
>>> Thanks again to ALL
>>>
>>> On Friday, 8 December 2017 10:39:45 UTC+1, gjr80 wrote:
>>>>
>>>> Ray,
>>>>
>>>> This is what we need to see, whether you use gedit, tail, nano or some 
>>>> other method as long as it works for you stick with it.
>>>>
>>>> The log extract shows that weeWX is not able to connect to your station 
>>>> for some reason. I am not a Fine Offset (and clones) whiz, though I know 
>>>> Fine Offset stations are prone to USB lockups (I am not sure if that is 
>>>> the 
>>>> case here). All I can suggest is you stop weeWX, unplug your stations USB 
>>>> cable, remove the power/batteries from the station, give it a minute or so 
>>>> and then re-apply power and plug in your the USB. Start weeWX and monitor 
>>>> syslog.
>>>>
>>>> Of course if Matthew or some other Fine Offset his has some ideas....
>>>>
>>>> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to