Issues and Observations about xig and Connect Port X2D unresponsive

[Kingsley Hill]

As noted in earlier posts I can force xig on ConnectPort X2D with the latest version (as of today) of everything to go into an unresponsive state.  Sending a string over the air that xig doesn't understand (e.g. abcdefg) or sending xig://help will initiate the state.  At that point any more data from that device will be ignored (or at least get no response) and the CPU utilization on the CP X2D will rise to 100%.  xig://abort or xig://quit sent from that radio will be ignored too. 

BUT:

Another radio will still get a response.  AND that other radio can send the xig:quit which reboots the CP X2.  Is that what xig:quit is supposed to do???  xig:abort does not do anything useful.  With xig:abort you get a "No Session to abort." message which makes sense since that station's session (the session of the station that is still working) is still in a functioning state and the session has terminated normally.

I take this to be two bugs in Xig:

1)  sending gobbledygook should not send the CP X2D session to go into the unresponsive state.

2)  xig:abort should work when the sent from the station with the session that has gone haywire.

Possible bug:

1)  Is xig:quit supposed to cause the CP X2 to reboot?

I hope this helps someone.  

[Rob Faludi]

This isn't a general problem with XIG, but it could be something specific to the X2D, or even to your firmware version on the X2D, we shouldn't rule that out either.

I just added a Wiki help item about launching XIG from the command line interface. You might want to try that and see if there's more info from the dynamic log:

https://code.google.com/p/xig/wiki/Command_Line_on_Gateways

--
You received this message because you are subscribed to the Google Groups "xbee-internet-gateway" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xbee-internet-ga...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kingsley Hill]

This is what the ConnectPort X2D does when you load it manually, send a couple of proper commands, and then send something it doesn't understand:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.03.06 20:43:08 =~=~=~=~=~=~=~=~=~=~=~=

#> python xig.py

xig - XBee Internet Gateway (XIG) v1.5.1 starting.
xig.io_kernel - XBee Version = 8067, Series = 8
xig.io_kernel - XBee reliable transmit enabled
xig.io_kernel - Enabling UDP listener on port 5649...
xig.io_kernel - XBee MTU = 256 bytes
xig - Loading and initializing configured session types...
xig - Loading ['HTTPSession'] from http...
xig - Loading ['iDigiDataAutostartSession', 'iDigiDataSession'] from idigi_data...
xig - Loading ['iDigiRCIAutostartSession', 'iDigiRCISession'] from idigi_rci...
xig - Formatting help text...
xig - Starting scheduler...
xig - XIG startup complete, all ready to serve requests.
xig.io_kernel - RECV: 11 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://time\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 1)
xig.xmit - X-API ZigBee TX Status (id = 1)
xig.xmit - GOOD: tx_status (id = 1)
xig.io_kernel - RECV: 39 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('http://www.flingbear.com/amIHere.html\r')
xig.http - successful GET of http://www.flingbear.com/amIHere.html
xig.http - connection closed by remote server
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 2)
xig.xmit - X-API ZigBee TX Status (id = 2)
xig.xmit - GOOD: tx_status (id = 2)
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('u')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('k')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('o')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('w')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('j')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('u')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('n')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('k')
xig.io_kernel - RECV: 1 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d2c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1c4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)

...thousands of these lines...  Then I sent ABORT

xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dec>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1b2c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1e8c>)
xig.io_kernel - RECV: 12 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://abort\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1e8c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)

...thousands more ...  Then I sent QUIT

xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dac>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1bec>)
xig.io_kernel - RECV: 11 bytes from ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17, 0, 0) ('xig://quit\r')
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1bec>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dec>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1c4c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1d0c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1e8c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1dcc>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c192c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1a8c>)
xig.xmit - SEND: to ('[00:13:A2:00:40:BF:22:05]!', 232, 49413, 17) (id = 3)
xig.io_kernel - IO: exception on XBee xmit (<socket.error instance at 0x8c1f4c>)

ad infinitum...

The only way out is to reboot the ConnectPort X2D

https://code.google.com/p/xig/wiki/Command_Line_on_Gateways

To unsubscribe from this group and stop receiving emails from it, send an email to xbee-internet-gateway+unsub...@googlegroups.com.