You could enter sudo journalctl -u weewx >weewxlog.txt
and post the resulting file weewxlog.txt here. What you posted is not complete. ANDREI ROZWADOWSKI schrieb am Montag, 30. September 2024 um 13:09:52 UTC+2: > I reinstalled RaspOS. Now it's Bookworm ( 32-bit ) . > After that I've installed Weewx. > I use Davis Vantage Pro2 with data-logger > This station is connected to RaspPi via usb cable (direct connection). > I checked folder /var/www/html/weewx/. It's empty. > There isn't the file "index.html". > And I didn't find folder "/dev/vantage" > I agree with vince and Warren Gill that Vantage drivers (/dev/ttyUSB0) is > not installed correctly. > > Also I printed logs: > > pi@raspberrypi:~ $ sudo systemctl status weewx > × weewx.service - WeeWX > Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: > enable> > Active: failed (Result: exit-code) since Sun 2024-09-29 16:06:19 MSK; > 1h 3> > Duration: 1.229s > Docs: https://weewx.com/docs > Process: 2788 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, > status=4) > Main PID: 2788 (code=exited, status=4) > CPU: 1.148s > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > seri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: Unable to > load dri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: **** > Exiting.> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Main process > exited, cod> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Failed with result > 'exit> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Consumed 1.148s CPU > time. > ...skipping... > × weewx.service - WeeWX > Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: > enable> > Active: failed (Result: exit-code) since Sun 2024-09-29 16:06:19 MSK; > 1h 3> > Duration: 1.229s > Docs: https://weewx.com/docs > Process: 2788 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, > status=4) > Main PID: 2788 (code=exited, status=4) > CPU: 1.148s > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > seri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: Unable to > load dri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: **** > Exiting.> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Main process > exited, cod> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Failed with result > 'exit> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Consumed 1.148s CPU > time. > ~ > ~ > ~ > ~ > > > pi@raspberrypi:~ $ sudo journalctl -u weewx > Sep 29 16:06:18 raspberrypi systemd[1]: Started weewx.service - WeeWX. > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Initializing > weewxd ve> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Command line: > /usr/sha> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Using Python: > 3.11.2 (> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Located at: > /usr/bin> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Platform: > Linux-6.> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Locale: > 'en_US.U> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Entry path: > /usr/sha> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: WEEWX_ROOT: > /etc/wee> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Config file: > /etc/wee> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: User module: > /etc/wee> > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Debug: 0 > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: User: > weewx > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Group: > weewx > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO __main__: Groups: > weewx > Sep 29 16:06:19 raspberrypi weewxd[2788]: INFO weewx.engine: Loading > station ty> > Sep 29 16:06:19 raspberrypi weewxd[2788]: ERROR weewx.engine: Import of > driver > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Trac> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Perm> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Duri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Trac> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > Fi> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > > > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL weewx.engine: **** > seri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: Unable to > load dri> > Sep 29 16:06:19 raspberrypi weewxd[2788]: CRITICAL __main__: **** > Exiting.> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Main process > exited, cod> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Failed with result > 'exit> > Sep 29 16:06:19 raspberrypi systemd[1]: weewx.service: Consumed 1.148s CPU > time. > lines 27-49/49 (END) > > What do you recommend to me? > Do I reinstall weewx? > > суббота, 28 сентября 2024 г. в 22:07:20 UTC+3, Warren Gill: > >> Try setting port to /dev/vantage >> The proper way to configure this up is to map the weewx.conf port setting >> to what's setup in udev. That way if the serial device gets >> unplugged/plugged and the usb mapper sends it to a different port, udev >> will always symlink it to /dev/vantage >> >> If the install worked correctly you should see UDEV rules in >> /usr/lib/udev/rules.d/60-weewx.rules >> In there you can find this: >> # davis vantage via usb-serial >> >> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage" >> >> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage" >> >> Which should match up to what you see in lsusb: >> Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge >> >> On Sat, Sep 28, 2024 at 1:02 AM ANDREI ROZWADOWSKI < >> [email protected]> wrote: >> >>> I checked RaspPi USB ports: >>> >>> pi@raspberrypi:~ $ sudo lsusb >>> Bus 001 Device 007: ID 10c4:ea61 Silicon Labs CP210x UART Bridge >>> Bus 001 Device 006: ID 03f0:304a HP, Inc Slim Keyboard >>> Bus 001 Device 005: ID 03f0:134a HP, Inc Optical Mouse >>> Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS >>> 802.11n WLAN Adapter >>> Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly >>> SMSC) SMSC9512/9514 Fast Ethernet Adapter >>> Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly >>> SMSC) SMC9514 Hub >>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> >>> After I opened weewx.conf: >>> [Vantage] >>> # This section is for the Davis Vantage series of weather stations. >>> >>> # Connection type: serial or ethernet >>> # serial (the classic VantagePro) >>> # ethernet (the WeatherLinkIP or Serial-Ethernet bridge) >>> type = serial >>> >>> # If the connection type is serial, a port must be specified: >>> # Debian, Ubuntu, Redhat, Fedora, and SuSE: >>> # /dev/ttyUSB0 is a common USB port name >>> # /dev/ttyS0 is a common serial port name >>> # BSD: >>> # /dev/cuaU0 is a common serial port name >>> port = /dev/ttyUSB0 >>> >>> # If the connection type is ethernet, an IP Address/hostname is >>> required: >>> host = 1.2.3.4 >>> >>> I don't use any USB-RS232 connector. So it seems to me that "ttyUSB0" is >>> correctly. >>> >>> Also I've got log: >>> pi@raspberrypi:~ $ journalctl -n 100 >>> Sep 28 08:40:54 raspberrypi systemd[892]: Starting >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect... >>> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Control process exited, code=exited, status=1/FAILURE >>> Sep 28 08:40:54 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Failed with result 'exit-code'. >>> Sep 28 08:40:54 raspberrypi systemd[892]: Failed to start >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co> >>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Scheduled restart job, restart counter is at 24483. >>> Sep 28 08:40:59 raspberrypi systemd[892]: Stopped >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect. >>> Sep 28 08:40:59 raspberrypi systemd[892]: Starting >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect... >>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Control process exited, code=exited, status=1/FAILURE >>> Sep 28 08:40:59 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Failed with result 'exit-code'. >>> Sep 28 08:40:59 raspberrypi systemd[892]: Failed to start >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co> >>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Scheduled restart job, restart counter is at 24484. >>> Sep 28 08:41:04 raspberrypi systemd[892]: Stopped >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect. >>> Sep 28 08:41:04 raspberrypi systemd[892]: Starting >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect... >>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Control process exited, code=exited, status=1/FAILURE >>> Sep 28 08:41:04 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Failed with result 'exit-code'. >>> Sep 28 08:41:04 raspberrypi systemd[892]: Failed to start >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co> >>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Scheduled restart job, restart counter is at 24485. >>> Sep 28 08:41:09 raspberrypi systemd[892]: Stopped >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect. >>> Sep 28 08:41:09 raspberrypi systemd[892]: Starting >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect... >>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Control process exited, code=exited, status=1/FAILURE >>> Sep 28 08:41:09 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Failed with result 'exit-code'. >>> Sep 28 08:41:09 raspberrypi systemd[892]: Failed to start >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co> >>> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Scheduled restart job, restart counter is at 24486. >>> Sep 28 08:41:15 raspberrypi systemd[892]: Stopped >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect. >>> Sep 28 08:41:15 raspberrypi systemd[892]: Starting >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect... >>> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Control process exited, code=exited, status=1/FAILURE >>> Sep 28 08:41:15 raspberrypi systemd[892]: rpi-connect-wayvnc.service: >>> Failed with result 'exit-code'. >>> Sep 28 08:41:15 raspberrypi systemd[892]: Failed to start >>> rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Co> >>> >>> Unfortunately I don't receive data from Vantage Pro2 >>> пятница, 27 сентября 2024 г. в 13:30:54 UTC+3, Ho Lee Fooks: >>> >>>> Currently using Pi OS lite 64-bit Debian Bookworm port with a pip >>>> install after a SD card failure. >>>> >>>> On Fri, Sep 27, 2024, 02:27 vince <[email protected]> wrote: >>>> >>>>> Again - we need to see your logfile please. Also need to see your >>>>> [Vantage] section from weewx.conf. As Tom said, your logfile seems to >>>>> indicate that you are trying to connect to a port that does not exist on >>>>> your system. >>>>> >>>>> Mine on a raspberry pi looks like this for a VP2 connected to the pi4. >>>>> >>>>> [Vantage] >>>>> # This section is for the Davis Vantage series of weather stations. >>>>> >>>>> # Connection type: serial or ethernet >>>>> # serial (the classic VantagePro) >>>>> # ethernet (the WeatherLinkIP or Serial-Ethernet bridge) >>>>> type = serial >>>>> port = */dev/ttyUSB0* >>>>> >>>>> You might want to run the "lsusb" and "dmesg" command to see what >>>>> devices are on your USB bus. >>>>> >>>>> pi@pi4:~$ lsusb >>>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>>>> *Bus 001 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 >>>>> Serial Port / Mobile Action MA-8910P* >>>>> Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub >>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>>> >>>>> pi@pi4:~$ dmesg|grep USB >>>>> [ 1.494727] xhci_hcd 0000:01:00.0: new USB bus registered, assigned >>>>> bus number 1 >>>>> [ 1.496256] xhci_hcd 0000:01:00.0: new USB bus registered, assigned >>>>> bus number 2 >>>>> [ 1.496291] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed >>>>> [ 1.496652] usb usb1: New USB device found, idVendor=1d6b, >>>>> idProduct=0002, bcdDevice= 6.01 >>>>> [ 1.496688] usb usb1: New USB device strings: Mfr=3, Product=2, >>>>> SerialNumber=1 >>>>> [ 1.497522] hub 1-0:1.0: USB hub found >>>>> [ 1.498604] usb usb2: New USB device found, idVendor=1d6b, >>>>> idProduct=0003, bcdDevice= 6.01 >>>>> [ 1.498640] usb usb2: New USB device strings: Mfr=3, Product=2, >>>>> SerialNumber=1 >>>>> [ 1.499393] hub 2-0:1.0: USB hub found >>>>> [ 1.513632] usbhid: USB HID core driver >>>>> [ 1.751480] usb 1-1: new high-speed USB device number 2 using >>>>> xhci_hcd >>>>> [ 1.902082] usb 1-1: New USB device found, idVendor=2109, >>>>> idProduct=3431, bcdDevice= 4.21 >>>>> [ 1.902145] usb 1-1: New USB device strings: Mfr=0, Product=1, >>>>> SerialNumber=0 >>>>> [ 1.902172] usb 1-1: Product: USB2.0 Hub >>>>> [ 1.904186] hub 1-1:1.0: USB hub found >>>>> [ 2.199479] usb 1-1.2: new full-speed USB device number 3 using >>>>> xhci_hcd >>>>> [ 2.303884] usb 1-1.2: New USB device found, idVendor=067b, >>>>> idProduct=2303, bcdDevice= 3.00 >>>>> [ 2.303945] usb 1-1.2: New USB device strings: Mfr=1, Product=2, >>>>> SerialNumber=0 >>>>> [ 2.303973] usb 1-1.2: Product: USB-Serial Controller >>>>> [ 7.708729] usbserial: USB Serial support registered for generic >>>>> [ 7.735802] usbserial: USB Serial support registered for pl2303 >>>>> *[ 7.801504] usb 1-1.2: pl2303 converter now attached to ttyUSB0* >>>>> >>>>> My VP2 is connected by a serial2usb connector to the pi, so it shows >>>>> up as the only device attached to the pi as reported by lsusb, and the >>>>> dmesg command shows that it is allocated /dev/ttyUSB0, which is what >>>>> matches my setup. >>>>> >>>>> On Thursday, September 26, 2024 at 9:51:36 PM UTC-7 ANDREI ROZWADOWSKI >>>>> wrote: >>>>> >>>>>> Thanks for the tip. >>>>>> I will also try to reinstall the OS. >>>>>> Please tell me, >>>>>> Does Weewx support 64-bit OS? >>>>>> >>>>>> пятница, 27 сентября 2024 г. в 02:07:48 UTC+3, Ho Lee Fooks: >>>>>> >>>>>>> journalctl -n 100 >>>>>>> Shows the last 100 lines. >>>>>>> >>>>>>> On Thu, Sep 26, 2024, 18:31 Ho Lee Fooks <[email protected]> wrote: >>>>>>> >>>>>>>> Reinstalling weewx, I wondered where the log was as well. It may be >>>>>>>> replaced with a binary log named journal. I found a README that >>>>>>>> explains >>>>>>>> more. >>>>>>>> >>>>>>>> On Thu, Sep 26, 2024, 10:59 '[email protected]' via weewx-user < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Maybe your log is elsewhere: >>>>>>>>> https://weewx.com/docs/5.1/usersguide/where/ >>>>>>>>> >>>>>>>>> ANDREI ROZWADOWSKI schrieb am Donnerstag, 26. September 2024 um >>>>>>>>> 16:33:55 UTC+2: >>>>>>>>> >>>>>>>>>> As for link >>>>>>>>>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log >>>>>>>>>> I've got the following results: >>>>>>>>>> >>>>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog | tee >>>>>>>>>> /var/tmp/mylog >>>>>>>>>> tail: cannot open '/var/log/syslog' for reading: No such file or >>>>>>>>>> directory >>>>>>>>>> tail: no files remaining >>>>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>>>>>> tail: cannot open '/var/log/syslog' for reading: No such file or >>>>>>>>>> directory >>>>>>>>>> tail: no files remaining >>>>>>>>>> pi@raspberrypi:~ $ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> четверг, 26 сентября 2024 г. в 17:29:07 UTC+3, ANDREI >>>>>>>>>> ROZWADOWSKI: >>>>>>>>>> >>>>>>>>>>> Good evening! >>>>>>>>>>> Below is the log file for Raspberry Pi 3B (OS Bullseye) >>>>>>>>>>> The latest results on the charts (in the folder: /var/www/html/ >>>>>>>>>>> www ) which I received are dated 09/25/2024, 06:15:00 PM >>>>>>>>>>> >>>>>>>>>>> pi@raspberrypi:~ $ sudo journalctl -u weewx >>>>>>>>>>> Sep 24 11:52:40 raspberrypi systemd[1]: Started weewx.service - >>>>>>>>>>> WeeWX. >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: >>>>>>>>>>> Initializing weewxd version 5.1.0 >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Command >>>>>>>>>>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Using >>>>>>>>>>> Python: 3.11.2 (main, Aug 26 2024, 07:20:54) [GCC 12.2.0] >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Located >>>>>>>>>>> at: /usr/bin/python3 >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: >>>>>>>>>>> Platform: Linux-6.6.47+rpt-rpi-v7-armv7l-with-glibc2.36 >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Locale: >>>>>>>>>>> 'en_US.UTF-8' >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Entry >>>>>>>>>>> path: /usr/share/weewx/weewxd.py >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: >>>>>>>>>>> WEEWX_ROOT: /etc/weewx >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Config >>>>>>>>>>> file: /etc/weewx/weewx.conf >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: User >>>>>>>>>>> module: /etc/weewx/bin/user >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Debug: >>>>>>>>>>> 0 >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: User: >>>>>>>>>>> weewx >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Group: >>>>>>>>>>> weewx >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO __main__: Groups: >>>>>>>>>>> weewx >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: INFO weewx.engine: >>>>>>>>>>> Loading station type Vantage (weewx.drivers.vantage) >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: ERROR weewx.engine: >>>>>>>>>>> Import of driver failed: [Errno 2] could not open port /dev/tty> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** Traceback (most recent call last): >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** File "/usr/lib/python3/dist-packages/serial/seri> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** self.fd = os.open(self.portstr, os.O_RDWR | os> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** FileNotFoundError: [Errno 2] No such file or direc> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** During handling of the above exception, another ex> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** Traceback (most recent call last): >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** File "/usr/share/weewx/weewx/engine.py", line 11> >>>>>>>>>>> Sep 24 11:52:40 raspberrypi weewxd[3034]: CRITICAL weewx.engine: >>>>>>>>>>> **** self.console = loader_function(config_dict, se> >>>>>>>>>>> lines 1-28 >>>>>>>>>>> среда, 25 сентября 2024 г. в 23:24:13 UTC+3, Tom Keffer: >>>>>>>>>>> >>>>>>>>>>>> I don't know what you mean by "registration". Do you mean >>>>>>>>>>>> station registration so it shows on this map >>>>>>>>>>>> <https://www.weewx.com/stations.html>? Or, something else? >>>>>>>>>>>> >>>>>>>>>>>> In any case, it's almost impossible to diagnose what's >>>>>>>>>>>> happening without a log. See the section *How to get a good, >>>>>>>>>>>> useful log >>>>>>>>>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log>* >>>>>>>>>>>> . >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 25, 2024 at 11:12 AM ANDREY <[email protected]> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Good evening! >>>>>>>>>>>>> >>>>>>>>>>>>> I use meteostation Davis Vantage Pro2 with Raspberry Pi 2B >>>>>>>>>>>>> since 2022. >>>>>>>>>>>>> Its operation system is Raspbian Buster (because I use AnyDesk >>>>>>>>>>>>> for the remote access). >>>>>>>>>>>>> Since June 2024, data registration has interrupted. >>>>>>>>>>>>> It worked only some hours. >>>>>>>>>>>>> I was reinstalling the operating system (Raspbian Buster). >>>>>>>>>>>>> I replaced the board on a Raspberry Pi 3B with Raspbian >>>>>>>>>>>>> Bullseye. >>>>>>>>>>>>> But I see the graphics with results for some hours. >>>>>>>>>>>>> After that the registration is stopped. >>>>>>>>>>>>> Why? >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> 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 on the web visit >>>>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/77b03b34-495e-43aa-9f12-f9cfada246cdn%40googlegroups.com >>>>>>>>>>>>> >>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/77b03b34-495e-43aa-9f12-f9cfada246cdn%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 on the web visit >>>>>>>>> https://groups.google.com/d/msgid/weewx-user/dd7e77cf-2234-409d-92aa-53fae15de8a4n%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/dd7e77cf-2234-409d-92aa-53fae15de8a4n%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 on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/d90ffe5b-057e-4614-8687-ae199a9c7f17n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/d90ffe5b-057e-4614-8687-ae199a9c7f17n%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 on the web visit >>> https://groups.google.com/d/msgid/weewx-user/ac42315c-18a1-410c-9da2-64442d9031c0n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/ac42315c-18a1-410c-9da2-64442d9031c0n%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 on the web visit https://groups.google.com/d/msgid/weewx-user/691dd165-6e0c-4e87-8075-a268cfff0016n%40googlegroups.com.
