And Its back to erroring....

I don't know what to do here guys...it seems totally sporadic.  back to 
original driver issues it appear(I realize the snip of th log isnt ful, but 
it gets the idea across)  I think I'[ll reach out ot those who have had 
this working with a PI b+ and the WMII and see what specific version of 
each they were using... Any other ideas?

Thanks!

Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: enable
   Active: failed (Result: exit-code) since Wed 2025-02-26 09:02:20 EST; 
3min 29s ago
     Docs: https://weewx.com/docs
  Process: 370 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf 
(code=exited, status=4)
 Main PID: 370 (code=exited, status=4)

Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     ****   
   self.open(
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     ****   
 File "/usr/l
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     ****   
   self._upda
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     ****   
 File "/usr/l
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     ****   
   fcntl.ioct
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL weewx.engine:     **** 
 OSError: [Errn
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL __main__: Unable to load 
driver: [Errn
Feb 26 09:02:20 raspberrypi weewxd[370]: CRITICAL __main__:     **** 
 Exiting...
Feb 26 09:02:20 raspberrypi systemd[1]: weewx.service: Main process exited, 
code=exited,
Feb 26 09:02:20 raspberrypi systemd[1]: weewx.service: Failed with result 
'exit-code'.
 

On Thursday, February 20, 2025 at 1:40:51 PM UTC-5 Brian LeDuc wrote:

> After a full reset here is where I'm at.  Still doesn't seem to be 
> recording any files in the db or generating anything in the expected folder:
> weewx.service - WeeWX
>    Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>    Active: active (running) since Thu 2025-02-20 11:59:35 EST; 21s ago
>      Docs: https://weewx.com/docs
>  Main PID: 4340 (python3)
>    Memory: 7.8M
>    CGroup: /system.slice/weewx.service
>            └─4340 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO __main__: Group:       
>  weewx
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO __main__: Groups:       
> weewx
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO weewx.engine: Loading 
> station type wmII (user.wmII)
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO user.wmII: Weather Monitor 
> II: driver version is 1.0
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO user.wmII: Weather Monitor 
> II: using serial port /dev/ttyUSB0
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO weewx.engine: StdConvert 
> target unit is 0x1
> Feb 20 11:59:41 raspberrypi weewxd[4340]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Feb 20 11:59:47 raspberrypi weewxd[4340]: INFO weewx.engine: Archive will 
> use data binding wx_binding
> Feb 20 11:59:47 raspberrypi weewxd[4340]: INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> Feb 20 11:59:47 raspberrypi weewxd[4340]: INFO weewx.engine: Using archive 
> interval of 300 seconds (specified in weewx configuration)
> root@raspberrypi:~# 
> root@raspberrypi:~# sudo systemctl status weewx
> ● weewx.service - WeeWX
>    Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>    Active: active (running) since Thu 2025-02-20 11:59:35 EST; 21min ago
>      Docs: https://weewx.com/docs
>  Main PID: 4340 (python3)
>    Memory: 8.8M
>    CGroup: /system.slice/weewx.service
>            └─4340 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>
> Feb 20 12:20:10 raspberrypi weewxd[4340]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> Feb 20 12:20:10 raspberrypi weewxd[4340]: INFO __main__: Starting up weewx 
> version 5.1.0
> Feb 20 12:20:12 raspberrypi weewxd[4340]: INFO weewx.engine: Error reading 
> time: Acknowledge returned empty: b''
> Feb 20 12:20:13 raspberrypi weewxd[4340]: INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Feb 20 12:20:13 raspberrypi weewxd[4340]: INFO weewx.manager: Starting 
> backfill of daily summaries
> Feb 20 12:20:13 raspberrypi weewxd[4340]: INFO weewx.manager: Daily 
> summaries up to date
> Feb 20 12:20:13 raspberrypi weewxd[4340]: INFO weewx.engine: Starting main 
> packet loop.
> Feb 20 12:20:15 raspberrypi weewxd[4340]: INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
> Feb 20 12:20:15 raspberrypi weewxd[4340]: CRITICAL __main__: Caught 
> WeeWxIOError: Acknowledge returned empty: b''
> Feb 20 12:20:15 raspberrypi weewxd[4340]: CRITICAL __main__:     **** 
>  Waiting 60.0 seconds then retrying...
> root@raspberrypi:~# sudo systemctl status weewx
>
> On Thursday, February 20, 2025 at 11:21:38 AM UTC-5 Brian LeDuc wrote:
>
>> Tom-
>>
>> Thanks.  Something is definitely off.  I switched the BR on the logger to 
>> give that a go and no dice.  Reset everything and put bacak to the way it 
>> was and now Weewx wont even start up....
>>
>> root@raspberrypi:~# sudo systemctl status weewx
>> ● weewx.service - WeeWX
>>
>>    Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
>> preset: enabled)
>>    Active: failed (Result: exit-code) since Thu 2025-02-20 11:13:42 EST; 
>> 1min 49s ago
>>      Docs: https://weewx.com/docs
>>   Process: 24689 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf 
>> (code=exited, status=4)
>>  Main PID: 24689 (code=exited, status=4)
>>
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****      self.open()
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****    File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
>> 286, in open
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****      self._update_dtr_state()
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****    File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
>> 634, in _update_dtr_state
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****      fcntl.ioctl(self.fd, TIOCMBIS, TIOCM_DTR_str)
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL weewx.engine:     
>> ****  OSError: [Errno 5] Input/output error
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL __main__: Unable to 
>> load driver: [Errno 5] Input/output error
>> Feb 20 11:13:42 raspberrypi weewxd[24689]: CRITICAL __main__:     **** 
>>  Exiting...
>> Feb 20 11:13:42 raspberrypi systemd[1]: weewx.service: Main process 
>> exited, code=exited, status=4/NOPERMISSION
>> Feb 20 11:13:42 raspberrypi systemd[1]: weewx.service: Failed with result 
>> 'exit-code'.
>> root@raspberrypi:~# 
>>
>> On Thu, Feb 20, 2025 at 10:39 AM Tom Keffer <[email protected]> wrote:
>>
>>> Brian,
>>>
>>> You will have to take this up with the driver's author. It appears that 
>>> the hardware is sending an acknowledgement number that the driver is not 
>>> expecting.
>>>
>>> -tk
>>>
>>> On Thu, Feb 20, 2025 at 7:29 AM Brian LeDuc <[email protected]> wrote:
>>>
>>>> Vince-
>>>>
>>>> Below is what I'm getting now.  It doesn't seem to be writing any 
>>>> data.  The folders are empty at /var/www/html/weewx
>>>>
>>>> Am I totally missing something?
>>>>
>>>> Thanks,
>>>>
>>>> -Brian
>>>>  
>>>> weewx.service - WeeWX
>>>>    Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
>>>> vendor preset: enabled)
>>>>    Active: active (running) since Thu 2025-02-20 09:53:13 EST; 17s ago
>>>>      Docs: https://weewx.com/docs
>>>>  Main PID: 2965 (python3)
>>>>    Memory: 11.3M
>>>>    CGroup: /system.slice/weewx.service
>>>>            └─2965 python3 /usr/share/weewx/weewxd.py 
>>>> /etc/weewx/weewx.conf
>>>>
>>>> Feb 20 09:53:22 raspberrypi weewxd[2965]: INFO weewx.engine: 'pyephem' 
>>>> detected, extended almanac data is available
>>>> Feb 20 09:53:22 raspberrypi weewxd[2965]: INFO __main__: Starting up 
>>>> weewx version 5.1.0
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.engine: Error 
>>>> reading time: Acknowledge not equal 6: b'\x00'
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.engine: Using 
>>>> binding 'wx_binding' to database 'weewx.sdb'
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.manager: Starting 
>>>> backfill of daily summaries
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.manager: Daily 
>>>> summaries up to date
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.engine: Starting 
>>>> main packet loop.
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: INFO weewx.engine: Main loop 
>>>> exiting. Shutting engine down.
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: CRITICAL __main__: Caught 
>>>> WeeWxIOError: Acknowledge not equal 6: b'\x00'
>>>> Feb 20 09:53:25 raspberrypi weewxd[2965]: CRITICAL __main__:     **** 
>>>>  Waiting 60.0 seconds then retrying...
>>>>
>>>> root@raspberrypi:~# sudo journalctl -u weew --lines 100
>>>> -- Logs begin at Fri 2025-02-14 15:03:55 EST, end at Thu 2025-02-20 
>>>> 10:09:06 EST. --
>>>> -- No entries --
>>>>
>>>> On Thursday, February 13, 2025 at 7:30:45 PM UTC-5 Brian LeDuc wrote:
>>>>
>>>>> Vince-
>>>>>
>>>>> Roger that, no SS.  Does that appear of have been successful though?
>>>>>
>>>>> Thanks for the addtional info.  I used the debian apt install for 
>>>>> weewx and the latest offical rasb pi installer for the pi image.  I'll 
>>>>> give 
>>>>> nginx a try.  The weewx simulator was working fine, so I guess I thought 
>>>>> the numbers should push as well once live.  I did fumble through the 
>>>>> folders after manually running the StandardReport and there is no data at 
>>>>> what I believe the correct locati should be based on documentation: 
>>>>> /var/www/html/weewx/
>>>>>
>>>>> Yes, Irix was fun...it was probably 25 years ago.  Did a bunch of work 
>>>>> on the old SGI Indy(pizza box) and O2.  Played on a couple Indigos as 
>>>>> well, 
>>>>> but really like the 02....It was back when Scuzzy was all the rage so it 
>>>>> almost felt like you were workign with a rack machine.  
>>>>>
>>>>> Thanks again,
>>>>>
>>>>> -Brian
>>>>>
>>>>>
>>>>> On Thursday, February 13, 2025 at 6:48:21 PM UTC-5 vince wrote:
>>>>>
>>>>>> IRIX ?  It has to have been decades.  They were pretty cool when they 
>>>>>> were cutting edge back then.
>>>>>>
>>>>>> Please don't post screen shots.  Attach log excerpts please.   Try "sudo 
>>>>>> journalctl -u weewx" for viewing weewx related entries.  You might 
>>>>>> optionally add a "--lines 100" switch too if you want to limit it to 
>>>>>> the last 100 lines.   We basically need to see the log entries from 
>>>>>> weewx 
>>>>>> startup through the first or second archive period, meaning 5 minutes or 
>>>>>> more.
>>>>>>
>>>>>> Weewx does not install a webserver and depending on how you installed 
>>>>>> the pi, raspi os might not do so either.  FWIW, I use nginx here as it's 
>>>>>> light and reliable, but any webserver you want to install would work 
>>>>>> fine 
>>>>>> if properly configured.
>>>>>>
>>>>>> On Thursday, February 13, 2025 at 3:04:38 PM UTC-8 Brian LeDuc wrote:
>>>>>>
>>>>>>> Vince-- thank you for the quick response.  I'm rusty on my 
>>>>>>> linux...most of my past experience is actually with Irix/Unix and its 
>>>>>>> been 
>>>>>>> years...
>>>>>>>
>>>>>>> Oh, I hope it was that simple....I got lazy with the SS, and this is 
>>>>>>> a lot easier when running two monitors and 3 systems.....
>>>>>>>
>>>>>>> still not showing up on /var/www/html/weewx/index.html though.
>>>>>>>
>>>>>>> [image: KIMG3644.JPG]
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, February 13, 2025 at 5:31:34 PM UTC-5 vince wrote:
>>>>>>>
>>>>>>>> Sounds like all the other usb related problems, but before we try 
>>>>>>>> going deeper please try /dev/ttyUSB0 in mixed case in your weewx.conf 
>>>>>>>> file. 
>>>>>>>> Linux is case-specific.
>>>>>>>>
>>>>>>>> On Thursday, February 13, 2025 at 2:26:46 PM UTC-8 Brian LeDuc 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi-
>>>>>>>>>
>>>>>>>>> I"m new to all this but have been working for a few days trying to 
>>>>>>>>> get weewx working iwth a WMII on a pi b+.  I have done the intall 
>>>>>>>>> from the 
>>>>>>>>> root cmd prompt following the debian directions and installed the 
>>>>>>>>> wmII 
>>>>>>>>> driver in the user folder.  I continue to have connectivity issues 
>>>>>>>>> and 
>>>>>>>>> errors- looking mostly like driver issues maybe?  any help from 
>>>>>>>>> anyone who 
>>>>>>>>> has done this setup with a WMII would be greatly appreciated, thanks!
>>>>>>>>>
>>>>>>>>> Error from the log:
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: 
>>>>>>>>> Initializing weewxd version 5.1.0
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Command 
>>>>>>>>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Using 
>>>>>>>>> Python: 3.7.3 (default, Dec 20 2019, 18:57:59) 
>>>>>>>>>                                          [GCC 8.3.0]
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Located 
>>>>>>>>> at:   /usr/bin/python3
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Platform: 
>>>>>>>>>     Linux-4.19.97+-armv6l-with-debian-10.3
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Locale:   
>>>>>>>>>     'en_US.UTF-8'
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Entry 
>>>>>>>>> path:   /usr/share/weewx/weewxd.py
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: 
>>>>>>>>> WEEWX_ROOT:   /etc/weewx
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Config 
>>>>>>>>> file:  /etc/weewx/weewx.conf
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: User 
>>>>>>>>> module:  /etc/weewx/bin/user
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Debug:     
>>>>>>>>>    0
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: User:     
>>>>>>>>>     weewx
>>>>>>>>> Feb 12 16:00:40 raspberrypi weewxd[341]: INFO __main__: Group:     
>>>>>>>>>    weewx
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: INFO __main__: Groups:   
>>>>>>>>>     weewx
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: INFO weewx.engine: 
>>>>>>>>> Loading station type wmII (user.wmII)
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: INFO user.wmII: Weather 
>>>>>>>>> Monitor II: driver version is 1.0
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: INFO user.wmII: Weather 
>>>>>>>>> Monitor II: using serial port /dev/ttyusb0
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: ERROR weewx.engine: 
>>>>>>>>> Import of driver failed: [Errno 2] could not open port /dev/ttyusb0: 
>>>>>>>>> [Errno 
>>>>>>>>> 2] No such file or directory: '/dev/ttyusb0' (<class 'serial.serial
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****  Traceback (most recent call last):
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****    File 
>>>>>>>>> "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
>>>>>>>>> 265, in open
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****      self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
>>>>>>>>> os.O_NONBLOCK)
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****  FileNotFoundError: [Errno 2] No such file or directory: 
>>>>>>>>> '/dev/ttyusb0'
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****  During handling of the above exception, another exception 
>>>>>>>>> occurred:
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****  Traceback (most recent call last):
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****    File "/usr/share/weewx/weewx/engine.py", line 115, in 
>>>>>>>>> setupStation
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****      self.console = loader_function(config_dict, self)
>>>>>>>>> Feb 12 16:00:41 raspberrypi weewxd[341]: CRITICAL weewx.engine:   
>>>>>>>>>   ****    File "/etc/weewx/bin/user/wmII.py", line 45, in loader
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Brian
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -- 
>>>> 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].
>>>> To view this discussion visit 
>>>> https://groups.google.com/d/msgid/weewx-user/5894ea85-618d-45c1-94a0-2e0acafe7767n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/5894ea85-618d-45c1-94a0-2e0acafe7767n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>>> 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].
>>>
>> To view this discussion visit 
>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEDtR0WRHo6viBe8KV5YU392q4nJ-uVuE7tWeze-3LXxqA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDtR0WRHo6viBe8KV5YU392q4nJ-uVuE7tWeze-3LXxqA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/517cf692-0edd-48f9-9643-497b4bfb49efn%40googlegroups.com.

Reply via email to