Re: [weewx-user] Resource busy - raspbian buster, weewx 4 and WMR200

[Chris Manton]

It looks like the initial error was a read failure from the device.

The second error is despite retries the resource is not reset to re-open and 
re-claim.


Since the system worked for a long time without this failure, I would think 
something about the new installation.


If the initial error 'froze' the usb bus, no amount of software tries will  
jiggle it lose.


mai 08 13:08:10 domo python3[322]: weewx[322] ERROR weewx.drivers.wmr200: USB 
read_device overflow error
mai 08 13:08:10 domo python3[322]: weewx[322] ERROR weewx.drivers.wmr200: USB 
device read error
mai 08 13:08:11 domo python3[322]: weewx[322] ERROR weewx.drivers.wmr200: USB 
polling thread unexpectedly 


I think we'd need to know the state of the wmr200 and/or usb bus at the time of 
failure, or understand exactly what kind of read_device overflow error occurred.


On Friday, May 8, 2020 at 7:28:21 AM UTC-7, Tom Keffer wrote:
>
> I've asked the author of the driver for help.
>
> On Fri, May 8, 2020 at 6:49 AM CloDi > 
> wrote:
>
>> Hi.
>>
>> Same error. I have activated the debug and joined the log.
>>
>> I don't know python to help to debug. But I can test any script...
>>
>> Thanks!
>>
>>
>> Le 07/05/2020 à 16:29, Tom Keffer a écrit :
>>
>> I am guessing the problem is that the WMR200 driver is not always 
>> releasing the USB interface, despite saying it has.
>>
>> One thing you can try is run weewxd with the loop_on_init flag. This 
>> will cause it to keep trying. See the section *General 
>> * in the User's Guide.
>>
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c1e74582-84d6-8108-1f38-629238f1f67e%40gmail.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/004c441a-22d9-47b4-804f-efda94a83866%40googlegroups.com.

Re: [weewx-user] Resource busy - raspbian buster, weewx 4 and WMR200

[Tom Keffer]

I've asked the author of the driver for help.

On Fri, May 8, 2020 at 6:49 AM CloDi  wrote:

> Hi.
>
> Same error. I have activated the debug and joined the log.
>
> I don't know python to help to debug. But I can test any script...
>
> Thanks!
>
>
> Le 07/05/2020 à 16:29, Tom Keffer a écrit :
>
> I am guessing the problem is that the WMR200 driver is not always
> releasing the USB interface, despite saying it has.
>
> One thing you can try is run weewxd with the loop_on_init flag. This will
> cause it to keep trying. See the section *General
> * in the User's Guide.
>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c1e74582-84d6-8108-1f38-629238f1f67e%40gmail.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDdKZ6Wcf75AnrJ%3D19AXYmpAXOHhd6m8bcLNHyk2NgP9A%40mail.gmail.com.

Re: [weewx-user] Resource busy - raspbian buster, weewx 4 and WMR200

[CloDi]

Hi.

Same error. I have activated the debug and joined the log.

I don't know python to help to debug. But I can test any script...

Thanks!


Le 07/05/2020 à 16:29, Tom Keffer a écrit :
I am guessing the problem is that the WMR200 driver is not always 
releasing the USB interface, despite saying it has.


One thing you can try is run weewxd with the loop_on_initflag. This 
will cause it to keep trying. See the section /General 
/ in the User's Guide.





--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c1e74582-84d6-8108-1f38-629238f1f67e%40gmail.com.
-- Logs begin at Fri 2020-05-08 12:17:01 CEST, end at Fri 2020-05-08 15:38:27 CEST. --
mai 08 13:07:03 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:12 live_queue_len:1
mai 08 13:07:04 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:12
mai 08 13:07:04 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:13 live_queue_len:1
mai 08 13:07:05 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:13
mai 08 13:07:13 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:14 live_queue_len:1
mai 08 13:07:14 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:14
mai 08 13:07:18 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:15 live_queue_len:1
mai 08 13:07:19 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:15
mai 08 13:07:20 domo python3[322]: weewx[322] INFO weewx.manager: Added record 2020-05-08 13:07:00 CEST (1588936020) to database 'weewx.sdb'
mai 08 13:07:20 domo python3[322]: weewx[322] INFO weewx.manager: Added record 2020-05-08 13:07:00 CEST (1588936020) to daily summary in 'weewx.sdb'
mai 08 13:07:22 domo python3[322]: weewx[322] DEBUG weewx.reportengine: Running reports for latest time in the database.
mai 08 13:07:22 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() phase getting live packets
mai 08 13:07:22 domo python3[322]: weewx[322] DEBUG weewx.reportengine: Running report 'neoground'
mai 08 13:07:22 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Acknowledged control packet rx:1
mai 08 13:07:22 domo python3[322]: weewx[322] DEBUG weewx.reportengine: Found configuration file /etc/weewx/skins/neowx/skin.conf for report 'neoground'
mai 08 13:07:23 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:1 archive_queue_len:1
mai 08 13:07:24 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:2 archive_queue_len:2
mai 08 13:07:24 domo python3[322]: weewx[322] DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
mai 08 13:07:24 domo python3[322]: weewx[322] DEBUG weewx.manager: Daily summary version is 2.0
mai 08 13:07:25 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:3 archive_queue_len:3
mai 08 13:07:26 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:4 archive_queue_len:4
mai 08 13:07:27 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:5 archive_queue_len:5
mai 08 13:07:28 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:6 archive_queue_len:6
mai 08 13:07:30 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:7 archive_queue_len:7
mai 08 13:07:30 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Acknowledged control packet rx:2
mai 08 13:07:31 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing archive packet rx:8 archive_queue_len:8
mai 08 13:07:31 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:16 live_queue_len:1
mai 08 13:07:32 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:26
mai 08 13:07:33 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:17 live_queue_len:1
mai 08 13:07:34 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:27
mai 08 13:07:44 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200:   Queuing live packet rx:18 live_queue_len:1
mai 08 13:07:44 domo python3[322]: weewx[322] DEBUG weewx.drivers.wmr200: genLoop() Yielding live queued packet id:28
mai 

Re: [weewx-user] Resource busy - raspbian buster, weewx 4 and WMR200

[Tom Keffer]

I am guessing the problem is that the WMR200 driver is not always releasing
the USB interface, despite saying it has.

One thing you can try is run weewxd with the loop_on_init flag. This will
cause it to keep trying. See the section *General
* in the User's Guide.

On Thu, May 7, 2020 at 4:30 AM Clo Di  wrote:

> Hello! I have been using Weewx for many years with raspbian on a
> raspberry with a WMR200 station.
> This week, I installed the new system (buster - 10.3) and the new version
> of weewx.
> I also used a new base SQLite.
> Weewx launch correctly for a  few hours. But there "regurlarly" an error.
> The unique solution is to stop and start weewx.
>
> Someone have an idea what is the source of the problem?
>
> $ sudo systemctl status weewx
> weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: active (running) since Tue 2020-05-05 23:10:17 CEST; 1 day 13h
> ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 5624 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>Memory: 29.5M
>CGroup: /system.slice/weewx.service
>└─5640 python3 /usr/share/weewx/weewxd --daemon
> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
>   self.console = loader_function(config_dict, self)
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/wmr200.py", line 58, in loader
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
>   return WMR200(**config_dict[DRIVER_NAME])
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/wmr200.py", line 1466, in
> __init__
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
>   self.usb_device.open_device()
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/wmr200.py", line 196, in
> open_device
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
>   raise weewx.WakeupError(exception)
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL weewx.engine:
>   weewx.WakeupError: [Errno 16] Resource busy
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL __main__: Unable
> to load driver: [Errno 16] Resource busy
> mai 07 06:41:05 domo python3[5640]: weewx[5640] CRITICAL __main__:
>   Exiting...
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b6aa4404-a1ef-476f-bbb0-e2a87fbfaff4%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEB2UbyXt62K7adZQDbErbK2uEMRvSv2%2BQjYqLZ1kWu_pA%40mail.gmail.com.