v3.2.1 "Unable to load driver: write failed"

[Phil]

I just upgraded from 1.14.1 and can't get weewx to start.  After failing, I removed all the old files and started with a "fresh" install, still no dice.  I can use minicom to issue a "TEST" to the serial port and it echoes back "TEST", so I know comms are good (and it worked in 1.14.1)

Here's what I'm getting:

Oct  2 16:47:44 Server weewx[8767]: engine: Initializing weewx version 3.2.1
Oct  2 16:47:44 Server weewx[8767]: engine: Using Python 2.7.6 (default, Jun 22 2015, 17:58:13) #012[GCC 4.8.2]
Oct  2 16:47:44 Server weewx[8767]: engine: Platform Linux-3.13.0-65-generic-x86_64-with-Ubuntu-14.04-trusty
Oct  2 16:47:44 Server weewx[8767]: engine: Using configuration file /etc/weewx/weewx.conf
Oct  2 16:47:44 Server weewx[8767]: engine: Initializing engine
Oct  2 16:47:44 Server weewx[8767]: engine: Loading station type Vantage (weewx.drivers.vantage)
Oct  2 16:47:44 Server weewx[8767]: vantage: Opened up serial port /dev/rfcomm0; baud 19200; timeout 5.00
Oct  2 16:47:44 Server weewx[8767]: engine: Unable to load driver: write failed: [Errno 107] Transport endpoint is not connected
Oct  2 16:47:44 Server weewx[8767]:     ****  Exiting...

Anyone have any ideas?

[Thomas Keffer]

​Hello, Phil

First time I've seen this error. ​A Google search reveals that it usually has something to do with sockets. 

The port you are using, /dev/rfcomm0, is non-standard. Are you using an unusual way to connect to the logger, say through a TCP/IP connection? I know that you got connectivity through minicom, but these are important clues.

-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.
For more options, visit https://groups.google.com/d/optout.

[Phil]

I'm using a bluetooth serial connection to connect to the console, and have been since 2012 using version 1.14.1.  Here's how I did it: http://www.wxforum.net/index.php?topic=16937.0 

It's not TCP/IP or sockets-based, and like I said I can connect with minicom and talk to the console just fine.  Is it possible that the code in 3.2.1 tries to use a socket somehow if it doesn't see a tty serial port?

[Thomas Keffer]

​Despite your version being over 3 years old, the Vantage driver has actually changed very little. Most of the changes have been around how the databases and extensions are handled.

Could you please swap out your version of weewx/engine.py with the attached?

It will give a little more information about exactly where the error is happening.

-tk

​

[Phil]

I just found out what's going on, and this will probably happen to anyone who reboots their Ubuntu 14.04 box after the most recent update.

The current Kernel version (3.13.0-65) breaks Python serial comms as well as TX on most USB serial adapters somehow.  I rebooted with 3.13.0-63 and have no problems.

Here's the information: https://www.mail-archive.com/kernel-...@lists.launchpad.net/msg137077.html

What a nightmare!  I've been screwing with this all day and just finally found that bug!

[Thomas Keffer]

I just tried this and am having the same problem. Ubuntu 14.04, which I "upgraded" to kernel 3.13.0-65. Got the error

Oct  3 07:05:16 nuc weewx[4236]: engine: Using configuration file /home/weewx/weewx.conf

Oct  3 07:05:16 nuc weewx[4236]: engine: Initializing engine

Oct  3 07:05:16 nuc weewx[4236]: engine: Loading station type Vantage (weewx.drivers.vantage)

Oct  3 07:05:16 nuc weewx[4236]: vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 5.00

Oct  3 07:05:17 nuc weewx[4236]: vantage: SerialException.

I'm amazed this one shipped, particularly seeing as how it is an "LTS" release.

-tk

[Mike DW5071]

Thanks for figuring this out for us all.

[Thomas Keffer]

+1 on that. Thanks, Phil.

-tk

On Sat, Oct 10, 2015 at 1:36 PM, Mike DW5071 <mi...@dw5071.com> wrote:

Thanks for figuring this out for us all.

--

[Jason Rennie]

I saw that folks were reporting success with 3.13.0-66, so I updated and rebooted. I'm happy to report that weewx seems to be working normally :)

Thanks Phil!

Jason

[(-pEEf-)]

Yeah, I was damn near pulling my hair out for a few hours over this.  I didn't want anyone else to suffer.

--
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/FdapyM5Ku0U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.