Hi thanks for your help.
i have desactivate ipv6 on the rapsberry by adding
net.ipv6.conf.all.disable_ipv6=1
in /etc/sysctl.conf
i hope it will be enough. i don't see any ip6 address on ifconfig but can
still see something in sudo netstat -lntp
tcp6 0 0 :::80 :::* LISTEN
612/apache2
tcp6 0 0 :::22 :::* LISTEN
499/sshd
i have as well change the address of my mysql server in weewx.conf to put
the ip address instead of the domain name address, just in case i have
problem with my local DNS server.
i will monitor tonight and let you know.
if i can't find anything i can alway cron reboot my rpi onece every hour.
it should at least hide the problem :)
On Saturday, December 24, 2016 at 3:31:51 PM UTC+7, Glenn McKechnie wrote:
There's certainly a network problem, and with your database on a remote
> machine ( Database host: minux.cubadak ) then something has to give ...
>
> [...]
>
> Dec 24 08:35:19 weatherstation weewx[606]: manager: added record
> 2016-12-24 08:35:00 WIB (1482543300) to database 'weewx'
> Dec 24 08:35:19 weatherstation weewx[606]: manager: added record
> 2016-12-24 08:35:00 WIB (1482543300) to daily summary in 'weewx'
> Dec 24 08:35:19 weatherstation weewx[606]: forecast: MainThread:
> Zambretti: starting thread
>
> [...]
>
> Dec 24 08:38:03 weatherstation weewx[606]: wh23xx: read_record: cmdbuf: 02
> 02 04 04 (len=4)
> Dec 24 08:39:31 weatherstation dhcpcd[433]: eth0: DHCPv6 REPLY: No Binding
> Dec 24 08:44:40 weatherstation dhcpcd[433]: eth0: DHCPv6 REPLY: No Binding
> Dec 24 08:46:28 weatherstation dhcpcd[433]: eth0:
> fe80::ba27:ebff:fe6d:f9db router available
> Dec 24 08:51:26 weatherstation dhcpcd[433]: eth0:
> fe80::ba27:ebff:fe6d:f9db router available
> Dec 24 08:51:27 weatherstation dhcpcd[433]: eth0:
> fe80::ba27:ebff:fe6d:f9db router available
> Dec 24 08:52:35 weatherstation dhcpcd[433]: eth0: failed to renew DHCPv6,
> rebinding
> Dec 24 08:52:35 weatherstation dhcpcd[433]: eth0:
> fe80::ba27:ebff:fe6d:f9db: DHCPv6 REPLY missing IA Address
> Dec 24 08:52:35 weatherstation dhcpcd[433]: eth0: no useable IA found in
> lease
>
>
>
> The above log snippets show the 8:37 failure you mention.
>
> From there you reboot at 11:35 and it comes up again and appears to start
> working, storing data successfully from 11:40:16 through to 13:10:28
>
> I can't see the failure you mention between 8:37 to 1:30 ie: - "the weewx
> has stop working from 8:37 to 1:30 until i reboot the rpi."
>
> That confusion aside, I'd be delving into the network side of your setup
> as that's definitely a problem, especially when using a remote database as
> you are.
>
> FWIW I've run into difficulties before with ipv6 running in tandem with
> ipv4. I don't insist on it for networking. If I get a lease on my internal
> network using ipv4 alone I'm happy, as is the network.
> Having said that, your network problems could be due to anything.
>
> Happy hunting
>
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 24 December 2016 at 17:27, Marc Aubry <marco...@gmail.com <javascript:>
> > wrote:
>
>> this morning crash syslog (see attachfile)ed
>> the weewx has stop working from 8:37 to 1:30 until i reboot the rpi.
>> maybe i have a network issue...
>> i'll try to use a fix ip instead of static address delivered by my dhcp
>> ...
>> which going to be the same nbut form my ddwrt routr i prefer to use the
>> dhcp/dnsmasq to atribute even the fix ip.
>>
>> On Friday, December 23, 2016 at 3:18:51 PM UTC+7, Marc Aubry wrote:
>>>
>>> ok
>>> driver updated with the following:
>>>
>>> wget -O weewx-wh23xx.zip
>>> https://github.com/matthewwall/weewx-wh23xx/archive/master.zip
>>> sudo wee_extension --install weewx-wh23xx.zip
>>> sudo service weewx stop
>>> sudo service weewx start
>>>
>>> please find attached the wee_debug file
>>>
>>>
>>>
>>> On Friday, December 23, 2016 at 3:00:01 PM UTC+7, Marc Aubry wrote:
>>>>
>>>> ok, i'll update the driver
>>>> please find attached the syslog file of the last crash 14:05
>>>>
>>>>
>>>>
>>>> n Friday, December 23, 2016 at 9:52:14 AM UTC+7, mwall wrote:
>>>>
>>>>> 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 weewx-user+...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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.
