Welcome to the Cumulus Support forum.

Latest Cumulus MX release v3.0.0 build 3050 - 1 May 2019.
Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014

See the Wiki for downloading either version.

_wapi_connect: error looking up socket handle 0x11

Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.

Moderator: mcrossley

Post Reply
Chapel
Posts: 79
Joined: Mon 30 Jul 2018 10:23 am
Weather Station: Instromet
Operating System: Raspbian
Location: Binbrook UK
Contact:

_wapi_connect: error looking up socket handle 0x11

Post by Chapel » Wed 03 Jul 2019 7:21 am

I noticed the following error on the MX console this morning. Despite this everything was running as expected and I have now restarted CuMX as a precaution. The box is a Raspberry Pi3B+

Reading archive data from 17/06/2019 09:10:31 - please wait
Normal running
_wapi_connect: error looking up socket handle 0x11

Has anyone else experienced this?

User avatar
mcrossley
Posts: 5581
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2
Operating System: Stretch Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: _wapi_connect: error looking up socket handle 0x11

Post by mcrossley » Mon 08 Jul 2019 4:06 pm

Not seen it before, but it looks like a transitory error doing a HTTP call, was there anything in the diags log at that time?

Chapel
Posts: 79
Joined: Mon 30 Jul 2018 10:23 am
Weather Station: Instromet
Operating System: Raspbian
Location: Binbrook UK
Contact:

Re: _wapi_connect: error looking up socket handle 0x11

Post by Chapel » Mon 08 Jul 2019 6:53 pm

Nothing in the logs related to this event, in fact all I do see is the usual "WU update: Error getting response stream (ReadDone2): ReceiveFailure"

User avatar
mcrossley
Posts: 5581
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2
Operating System: Stretch Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: _wapi_connect: error looking up socket handle 0x11

Post by mcrossley » Tue 09 Jul 2019 2:27 pm

From what I have read the error is coming direct from Mono, but it isn't severe enough to cause raise an exception back to the application.

Post Reply