RPi WeeWx Python 3.7 Issue

103 views
Skip to first unread message

Dave McCreath

unread,
Apr 21, 2021, 7:08:18 PM4/21/21
to weewx-user
Good Evening Venerable Experts

Earlier on today I updated my RPi (sudu apt-get update && sudo apt-get upgrade).  On rebooting WeeWx failed to start, this was post an upgrade from 4.2 to 4.5.1. (I have WeeWx added to the sources list)

So, being savvy, rebooted from a backup sd card to bring the system back to where it was prior to the update/upgrade and WeeWx version 4.2.

I then went about updating/upgrading WeeWx from 4.2 to 4.5 (sudo apt-get install weewx), that went fine, rebooted and WeeWx ran without any issues post the upgrade.

Next I then tried sudu apt-get update && sudo apt-get upgrade again.  Post a reboot, exactly the same issue as before, WeeWx would not start:

pi@raspberrypi:~ $ service weewx status

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx; generated)

   Active: active (exited) since Wed 2021-04-21 23:48:06 BST; 2min 28s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 338 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)

 

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****      self.port.openPort()

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 308, in openPort

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****      self.serial_port = serial.Serial(self.port, self.baudrate, timeout=self.timeout)

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****    File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****      self.open()

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****    File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****      raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL weewx.engine:     ****  serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL __main__: Unable to load driver: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'

Apr 21 23:48:06 raspberrypi python3[611]: weewx[611] CRITICAL __main__:     ****  Exiting...


Any ideas?

Dave McCreath

unread,
Apr 21, 2021, 7:34:34 PM4/21/21
to weewx-user
Forgot to add.

Now running 4.5.1 from a backup SD card and all is currently well but does not look like I'll be able to update/upgrade the RPi until I figure out what's wrong.

Regards

Dave

Tom Keffer

unread,
Apr 21, 2021, 8:07:33 PM4/21/21
to weewx-user
Do you have a device /dev/ttyUSB0? That's normally where a Vantage shows up in the device directory, but not always. 

The most reliable way to find out where the Vantage ended up is to unplug it, plug it in again, then type 'dmesg'. This will look something like:

dmesg
[14818.699217] usb 2-2.1: USB disconnect, device number 4
[14818.699660] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[14818.699710] pl2303 2-2.1:1.0: device disconnected
[14820.731608] usb 2-2.1: new full-speed USB device number 10 using xhci_hcd
[14820.844750] usb 2-2.1: New USB device found, idVendor=05ad, idProduct=0fba, bcdDevice= 3.00
[14820.844756] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[14820.844759] usb 2-2.1: Product: USB-Serial Controller
[14820.844761] usb 2-2.1: Manufacturer: Prolific Technology Inc.
[14820.852720] pl2303 2-2.1:1.0: pl2303 converter detected
[14820.856368] usb 2-2.1: pl2303 converter now attached to ttyUSB0

In my case, the serial-to-usb converter showed up at /dev/ttyUSB0, but your results may differ.

-tk

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/27e48fc1-8ea2-44c7-bdaa-73cfb1c15dcen%40googlegroups.com.

Dave McCreath

unread,
Apr 21, 2021, 8:14:53 PM4/21/21
to weewx...@googlegroups.com

Tom

 

Hi.

 

Yep, mine is the same as yours:

 

[ 4689.183852] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4689.183939] cp210x 1-1.4:1.0: device disconnected

[ 4689.633565] usb 1-1.4: new full-speed USB device number 5 using xhci_hcd

[ 4692.803586] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd

[ 4692.938998] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00

[ 4692.939011] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 4692.939021] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4692.939031] usb 1-1.4: Manufacturer: Silicon Labs

[ 4692.939040] usb 1-1.4: SerialNumber: 0001

[ 4692.946665] cp210x 1-1.4:1.0: cp210x converter detected

[ 4692.952907] usb 1-1.4: cp210x converter now attached to ttyUSB0

[ 4693.217302] usb 1-1.4: USB disconnect, device number 6

[ 4693.217689] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

[ 4693.217742] cp210x 1-1.4:1.0: device disconnected

[ 4693.513548] usb 1-1.4: new full-speed USB device number 7 using xhci_hcd

[ 4693.648964] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00

[ 4693.648972] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 4693.648979] usb 1-1.4: Product: CP2102 USB to UART Bridge Controller

[ 4693.648986] usb 1-1.4: Manufacturer: Silicon Labs

[ 4693.648992] usb 1-1.4: SerialNumber: 0001

[ 4693.652553] cp210x 1-1.4:1.0: cp210x converter detected

[ 4693.657075] usb 1-1.4: cp210x converter now attached to ttyUSB0

pi@raspberrypi:~ $

 

Regards

 

Dave

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/8CM2mGJ4eh8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECZ4Z%3DFCUUjoGFqJAgVkMg-WAiD6YpV2RXo69uMtAv7%2BA%40mail.gmail.com.

Tom Keffer

unread,
Apr 21, 2021, 8:19:22 PM4/21/21
to weewx-user
And it still doesn't work? Ok, you've got me stumped.

1. Show more of the log, not just what a service 'status' command shows. It may show clues farther upstream.

2. What happens if you try the Establishing connectivity test listed in the Wiki? Make sure you stop weewx first.

-tk

p q

unread,
Apr 21, 2021, 8:20:26 PM4/21/21
to weewx...@googlegroups.com
Unplug it and plug it back in :b



--
Peter Quinn
(415)794-2264

Dave McCreath

unread,
Apr 21, 2021, 8:21:28 PM4/21/21
to weewx-user
Tom

Please be aware that my answer is for the current working system, not the one that was broken.

I can try the RPi upgrade again and see if the file is located within the devices directory?

Dave

Dave McCreath

unread,
Apr 21, 2021, 8:23:25 PM4/21/21
to weewx...@googlegroups.com

Wait 15 minutes and I’ll do the upgrade again.

Tom Keffer

unread,
Apr 21, 2021, 8:28:21 PM4/21/21
to weewx-user
Well, geez, we're not trying to fix the working system. Try it on the broken system.

Dave McCreath

unread,
Apr 21, 2021, 8:43:37 PM4/21/21
to weewx-user
Tom

Apologies, it's 0140 in the morning here and it's been a long day!

Completed the upgrade but this time removed the plug and then re-inserted it post the reboot, all is now well.

pi@raspberrypi:~ $ service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Thu 2021-04-22 01:36:39 BST; 1min 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 437 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/weewx.service
           └─595 python3 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: CWOP: Posting not enabled.
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: WOW: Posting not enabled.
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.restx: AWEKAS: Data will be uploaded for user DMacWx
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO __main__: Starting up weewx version 4.5.1
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.engine: Clock error is 18.35 seconds (positive is fast)
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.drivers.vantage: Clock set to 2021-04-22 01:36:40 BST (1619051800)
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.manager: Starting backfill of daily summaries
Apr 22 01:36:39 raspberrypi python3[595]: weewx[595] INFO weewx.manager: Daily summaries up to date
Apr 22 01:36:40 raspberrypi python3[595]: weewx[595] INFO weewx.engine: Starting main packet loop.
pi@raspberrypi:~ $ 

Thanks for the suggestion Peter, appears to have fixed it.

Regards

Dave

Reply all
Reply to author
Forward
0 new messages