| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: Asyn not automatically reconnecting |
| From: | "Daykin, Evan" <[email protected]> |
| To: | Mark Rivers <[email protected]>, "[email protected]" <[email protected]> |
| Date: | Fri, 23 Feb 2018 14:55:04 +0000 |
|
Here is the output from the moment I killed the connection: 2018/02/23 09:51:47.086 TEST-RF-DCU-N0001 read VALUE AMP_WATER_FLOW AMP 2 7.0049e-168\n 2018/02/23 09:51:47.087 TEST-RF-DCU-N0001 set Eos 0 2018/02/23 09:51:47.087 asynManager::portThread port=TEST-RF-DCU-N0001 callback 2018/02/23 09:51:47.087 TEST-RF-DCU-N0001 addr -1 queueRequest priority 0 not lockHolder 2018/02/23 09:51:47.088 TEST-RF-DCU-N0001 schedule queueRequest timeout 2018/02/23 09:51:47.088 asynManager::portThread port=TEST-RF-DCU-N0001 callback 2018/02/23 09:51:47.088 test-rf-dcu-n0001.cts:5001 read. 2018/02/23 09:51:47.088 test-rf-dcu-n0001.cts:5001 read 0 2018/02/23 09:51:47.088 Close test-rf-dcu-n0001.cts:5001 connection (fd 18): Read from broken connection 2018/02/23 09:51:47.088 _TEST-RF-DCU-N0001:asyn: exception 0, asynExceptionConnect 2018/02/23 09:51:47.088 TEST-RF-DCU-N0001 read 2018/02/23 09:51:47.089 test-rf-dcu-n0001.cts:5001 read. 2018/02/23 09:51:47.089 test-rf-dcu-n0001.cts:5001 read. The last line then repeats rapidly forever. From: Mark Rivers [mailto:[email protected]] Can you set the asynTraceIOMask to 2 and the asynTraceMask to 0xff on that port just before you shut down the client? From: Daykin, Evan [mailto:[email protected]]
Hi Mark, Thanks for the reply. We are using asyn 4.33-2 and Stream 2.6-3. The protocol file has a ReplyTimeout of 2000ms. From: Mark Rivers [mailto:[email protected]]
Hi Evan, Ø
We have client devices that, when remotely updated and rebooted, the IOC does not attempt to reconnect automatically Ø
TEST-RF-DCU-N0001 multiDevice:No canBlock:Yes autoConnect:Yes Ø
enabled:Yes connected:No numberConnects 1 Ø
nDevices 0 nQueued 114 blocked:No The above information says that indeed autoConnect is set to Yes, and it is currently not connected. The 114 entries in the queue seems strange. What version of asyn and what version of StreamDevice are you using? What you are observing does not seem correct. What timeouts if any have you specified in your protocol file? Mark From:
[email protected] [mailto:[email protected]]
On Behalf Of Daykin, Evan Hello, Apologies if this has already been asked and answered. We have client devices that, when remotely updated and rebooted, the IOC does not attempt to reconnect automatically. Any records tied to it simply enter a TIMEOUT_ALARM state, and
no asyn or StreamDevice error messages are printed. autoConnect is not specified in drvAsynIPPortconfigure, which, according to the documentation, implicitly enables autoConnect/attempting to reconnect every 20 seconds. Does anything else need to be done? The devices are configured to communicate using Stream Device. Relevant asyn configuration in the startup script: -drvAsynIPPortConfigure("TEST-RF-DCU-N0001", "test-rf-dcu-n0001.cts:5001”) asynReport after client is disconnected and brought back up: TEST-RF-DCU-N0001 multiDevice:No canBlock:Yes autoConnect:Yes enabled:Yes connected:No numberConnects 1 nDevices 0 nQueued 114 blocked:No asynManagerLock:No synchronousLock:Yes exceptionActive:No exceptionUsers 2 exceptionNotifys 0 traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1 interposeInterfaceList asynOctet pinterface 0x7f0a07506900 drvPvt 0x6c3720 interfaceList asynCommon pinterface 0x7f0a07502650 drvPvt 0x6bfe30 asynOption pinterface 0x7f0a07502670 drvPvt 0x6bfe30 asynOctet pinterface 0x6bff50 drvPvt 0x6bfe30 Port test-rf-dcu-n0001.cts:5001: Disconnected fd: -1 Characters written: 127036 Characters read: 138000 -Evan |