Re: [weewx-user] WMR300 Driver Problems

[Thomas Keffer]

Hello, Alberto

The same suggestions apply. Try reverting to the old driver. Try running on
different hardware.

Also, please post your log, preferably with debug=1. There may be some
differences.

-tk

On Mon, Sep 4, 2017 at 7:44 AM, Alberto Sánchez  wrote:

> I believe that I have the same problem, with the same version of weewx
> 3.7.1 and WMR300.
>
>
> I thought it was a heating issue, and so the raspberry was blocked. I also
> use updated raspbian.
>
> --
> 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.
>

-- 
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.

Re: [weewx-user] WMR300 Driver Problems

[Alberto Sánchez]

I believe that I have the same problem, with the same version of weewx 3.7.1 
and WMR300.


I thought it was a heating issue, and so the raspberry was blocked. I also use 
updated raspbian.

-- 
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.

Re: [weewx-user] WMR300 Driver Problems

[mot23 mot23]

Thanks for your response,

I'm going on holidays now for two weeks, after that I will test those 
things out.

Tom 

-- 
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.

Re: [weewx-user] WMR300 Driver Problems

[Thomas Keffer]

The WMR300 driver initializes differently starting with v3.7.0. It's
possible this broke something. You could try reverting to the old v3.6.2
driver

and see if that has an affect.

If you can successfully run weewx on a different computer and/or a
different kernel, that would certainly suggest that it is an OS/kernel
problem and not a problem with your WMR300 hardware or driver.

-tk


On Wed, Aug 9, 2017 at 12:59 PM, mot23 mot23  wrote:

> Thanks for your fast response.
>
> In the first place, i was thinking about a hardware problem. So I already
> bought a new PI with a new power supply and usb cabel. The new PI has the
> same problem as the old one. The pi’s are running the same new linux
> kernels. I regularly update my system too avoid vulnerabilities. Before i
> updated my old Pi to 3.7.1, i was running 3.6.2. Yes, I also updated
> raspbian os when i was updating weewx.
>
>
> Is it maybe an option to run the simulation software on the old PI with
> the same linux kernel that we are running now on the new PI?
> I was also thinking about running the software on a standard PC whit a
> other debian distribution, to make clear that not raspbian os is causing
> the problems. What do you think about that?
>
>
> I am looking forward to your response.
>
> Regards Tom
>
> --
> 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.
>

-- 
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.

Re: [weewx-user] WMR300 Driver Problems

[mot23 mot23]

 

Thanks for your fast response.

In the first place, i was thinking about a hardware problem. So I already 
bought a new PI with a new power supply and usb cabel. The new PI has the 
same problem as the old one. The pi’s are running the same new linux 
kernels. I regularly update my system too avoid vulnerabilities. Before i 
updated my old Pi to 3.7.1, i was running 3.6.2. Yes, I also updated 
raspbian os when i was updating weewx. 


Is it maybe an option to run the simulation software on the old PI with the 
same linux kernel that we are running now on the new PI?
I was also thinking about running the software on a standard PC whit a 
other debian distribution, to make clear that not raspbian os is causing 
the problems. What do you think about that? 


I am looking forward to your response.

Regards Tom

-- 
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.

Re: [weewx-user] WMR300 Driver Problems

[Thomas Keffer]

What version of weewx were you running before v3.7.1?

Did you change the operating system when you upgraded? I ask because the
kernel you are running, 4.9.28-v7, is a relatively recent one.

My hunch is that this is a usb or power supply problem. If you have another
power supply, try that. If you have a different usb cable, try that.

Does weewx run successfully using the simulator? To try this, you'll want
to set aside your database so you don't taint it with simulated data.

-tk





On Tue, Aug 8, 2017 at 12:10 PM, mot23 mot23  wrote:

> Dear Weewx users,
>
>
>
> System: Debian, raspbian os.
> Station: WMR300.
> Version: 3.7.1
>
> Since i have been updated weewx to version 3.7.1, i have some problems.
> After the servers(and weewx) has been up for a few days, the problems
> arise.
>
> Sometimes the server and weewx runs a few days and then go down together.
> Sometimes the system runs for a few days and then weewx stops and a few
> hours later the server goes also down.
> When I restart the system, everything works fine for another 2 or 3 days,
> and then the problem starts again.
>
> The biggest problem is that i can't find anything in the server syslog.
>
> In an attempt to eliminate all the problems, I have completely
> reinstalled the server. However, this did not solve the problems.
>
> Some time ago, the problem resembles, and as always I looked in the log.
> To my great surprise, I found the following in the syslog:
>
> Jul 24 17:30:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:30:00 CEST (1500910200) to daily summary in 'weewx.sdb'
> Jul 24 17:30:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7
> files for report StandardReport in 1.72 seconds
> Jul 24 17:30:18 raspberrypi weewx[747]: imagegenerator: Generated 12
> images for StandardReport in 1.15 seconds
> Jul 24 17:30:18 raspberrypi weewx[747]: copygenerator: copied 0 files to
> /var/www/weewx
> Jul 24 17:35:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:35:00 CEST (1500910500) to database 'weewx.sdb'
> Jul 24 17:35:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:35:00 CEST (1500910500) to daily summary in 'weewx.sdb'
> Jul 24 17:35:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7
> files for report StandardReport in 1.71 seconds
> Jul 24 17:35:18 raspberrypi weewx[747]: imagegenerator: Generated 12
> images for StandardReport in 1.14 seconds
> Jul 24 17:35:18 raspberrypi weewx[747]: copygenerator: copied 0 files to
> /var/www/weewx
> Jul 24 17:40:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:40:00 CEST (1500910800) to database 'weewx.sdb'
> Jul 24 17:40:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:40:00 CEST (1500910800) to daily summary in 'weewx.sdb'
> Jul 24 17:40:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7
> files for report StandardReport in 1.70 seconds
> Jul 24 17:40:18 raspberrypi weewx[747]: imagegenerator: Generated 12
> images for StandardReport in 1.15 seconds
> Jul 24 17:40:18 raspberrypi weewx[747]: copygenerator: copied 0 files to
> /var/www/weewx
> Jul 24 17:45:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:45:00 CEST (1500911100) to database 'weewx.sdb'
> Jul 24 17:45:15 raspberrypi weewx[747]: manager: Added record 2017-07-24
> 17:45:00 CEST (1500911100) to daily summary in 'weewx.sdb'
> Jul 24 17:45:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7
> files for report StandardReport in 1.70 seconds
> Jul 24 17:45:18 raspberrypi weewx[747]: imagegenerator: Generated 12
> images for StandardReport in 1.14 seconds
> Jul 24 17:45:18 raspberrypi weewx[747]: copygenerator: copied 0 files to
> /var/www/weewx
> Jul 24 17:47:03 raspberrypi kernel: [151341.782182] Unable to handle
> kernel paging request at virtual address 071128d5
> Jul 24 17:47:03 raspberrypi kernel: [151341.786067] pgd = b718
> Jul 24 17:47:03 raspberrypi kernel: [151341.787996] [071128d5]
> *pgd=
> Jul 24 17:47:03 raspberrypi kernel: [151341.789962] Internal error: Oops:
> 5 [#1] SMP ARM
> Jul 24 17:47:03 raspberrypi kernel: [151341.791958] Modules linked in:
> bnep hci_uart btbcm bluetooth ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl
> ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4
> nf_log_ipv4 nf_log_comm$
> Jul 24 17:47:03 raspberrypi kernel: [151341.808720] CPU: 2 PID: 747 Comm:
> python Not tainted 4.9.28-v7+ #998
> Jul 24 17:47:03 raspberrypi kernel: [151341.811366] Hardware name: BCM2835
> Jul 24 17:47:03 raspberrypi kernel: [151341.813968] task: b72aac40
> task.stack: b8d64000
> Jul 24 17:47:03 raspberrypi kernel: [151341.816628] PC is at
> __kmalloc+0x9c/0x274
> Jul 24 17:47:03 raspberrypi kernel: [151341.819246] LR is at
> __kmalloc+0x1d8/0x274
> Jul 24 17:47:03 raspberrypi kernel: [151341.821823] pc : [<8025dcb4>]
> lr : [<8025ddf0>]psr: 2013
> Jul 24 17:47:03 raspberrypi kernel: [151341.821823] sp : b8d65c20  ip :
> b8d65c20  fp : b8d65c64
> 

[weewx-user] WMR300 Driver Problems

[mot23 mot23]

Dear Weewx users,

 

System: Debian, raspbian os.
Station: WMR300.
Version: 3.7.1

Since i have been updated weewx to version 3.7.1, i have some problems.
After the servers(and weewx) has been up for a few days, the problems 
arise. 

Sometimes the server and weewx runs a few days and then go down together. 
Sometimes the system runs for a few days and then weewx stops and a few 
hours later the server goes also down.
When I restart the system, everything works fine for another 2 or 3 days, 
and then the problem starts again. 

The biggest problem is that i can't find anything in the server syslog. 

In an attempt to eliminate all the problems, I have completely reinstalled 
the server. However, this did not solve the problems.

Some time ago, the problem resembles, and as always I looked in the log. To 
my great surprise, I found the following in the syslog:

Jul 24 17:30:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:30:00 CEST (1500910200) to daily summary in 'weewx.sdb'
Jul 24 17:30:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7 files 
for report StandardReport in 1.72 seconds
Jul 24 17:30:18 raspberrypi weewx[747]: imagegenerator: Generated 12 images 
for StandardReport in 1.15 seconds
Jul 24 17:30:18 raspberrypi weewx[747]: copygenerator: copied 0 files to 
/var/www/weewx
Jul 24 17:35:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:35:00 CEST (1500910500) to database 'weewx.sdb'
Jul 24 17:35:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:35:00 CEST (1500910500) to daily summary in 'weewx.sdb'
Jul 24 17:35:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7 files 
for report StandardReport in 1.71 seconds
Jul 24 17:35:18 raspberrypi weewx[747]: imagegenerator: Generated 12 images 
for StandardReport in 1.14 seconds
Jul 24 17:35:18 raspberrypi weewx[747]: copygenerator: copied 0 files to 
/var/www/weewx
Jul 24 17:40:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:40:00 CEST (1500910800) to database 'weewx.sdb'
Jul 24 17:40:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:40:00 CEST (1500910800) to daily summary in 'weewx.sdb'
Jul 24 17:40:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7 files 
for report StandardReport in 1.70 seconds
Jul 24 17:40:18 raspberrypi weewx[747]: imagegenerator: Generated 12 images 
for StandardReport in 1.15 seconds
Jul 24 17:40:18 raspberrypi weewx[747]: copygenerator: copied 0 files to 
/var/www/weewx
Jul 24 17:45:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:45:00 CEST (1500911100) to database 'weewx.sdb'
Jul 24 17:45:15 raspberrypi weewx[747]: manager: Added record 2017-07-24 
17:45:00 CEST (1500911100) to daily summary in 'weewx.sdb'
Jul 24 17:45:17 raspberrypi weewx[747]: cheetahgenerator: Generated 7 files 
for report StandardReport in 1.70 seconds
Jul 24 17:45:18 raspberrypi weewx[747]: imagegenerator: Generated 12 images 
for StandardReport in 1.14 seconds
Jul 24 17:45:18 raspberrypi weewx[747]: copygenerator: copied 0 files to 
/var/www/weewx
Jul 24 17:47:03 raspberrypi kernel: [151341.782182] Unable to handle kernel 
paging request at virtual address 071128d5
Jul 24 17:47:03 raspberrypi kernel: [151341.786067] pgd = b718
Jul 24 17:47:03 raspberrypi kernel: [151341.787996] [071128d5] *pgd=
Jul 24 17:47:03 raspberrypi kernel: [151341.789962] Internal error: Oops: 5 
[#1] SMP ARM
Jul 24 17:47:03 raspberrypi kernel: [151341.791958] Modules linked in: bnep 
hci_uart btbcm bluetooth ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_comm$
Jul 24 17:47:03 raspberrypi kernel: [151341.808720] CPU: 2 PID: 747 Comm: 
python Not tainted 4.9.28-v7+ #998
Jul 24 17:47:03 raspberrypi kernel: [151341.811366] Hardware name: BCM2835
Jul 24 17:47:03 raspberrypi kernel: [151341.813968] task: b72aac40 
task.stack: b8d64000
Jul 24 17:47:03 raspberrypi kernel: [151341.816628] PC is at 
__kmalloc+0x9c/0x274
Jul 24 17:47:03 raspberrypi kernel: [151341.819246] LR is at 
__kmalloc+0x1d8/0x274
Jul 24 17:47:03 raspberrypi kernel: [151341.821823] pc : [<8025dcb4>]lr 
: [<8025ddf0>]psr: 2013
Jul 24 17:47:03 raspberrypi kernel: [151341.821823] sp : b8d65c20  ip : 
b8d65c20  fp : b8d65c64
Jul 24 17:47:03 raspberrypi kernel: [151341.827138] r10: b9801e40  r9 : 
805904f0  r8 : 024080c0
Jul 24 17:47:03 raspberrypi kernel: [151341.829808] r7 : 0038  r6 : 
  r5 : b9801e40  r4 : 071128d5
Jul 24 17:47:03 raspberrypi kernel: [151341.832439] r3 :   r2 : 
80b81420  r1 : 39407000  r0 : b8d65c20
Jul 24 17:47:03 raspberrypi kernel: [151341.834988] Flags: nzCv  IRQs on  
FIQs on  Mode SVC_32  ISA ARM  Segment user
Jul 24 17:47:03 raspberrypi kernel: [151341.837631] Control: 10c5383d  
Table: 3718006a  DAC: 0055
Jul 24 17:47:03 raspberrypi kernel: [151341.840317] Process python (pid: 
747, stack limit = 0xb8d64210)
Jul 24 17:47:03 raspberrypi kernel: