cli.py crashes everytime...
tsarangi opened this issue · 1 comments
tsarangi commented
(env)[tapas@ayinger ctp6commander]$ python cli.py --connection ctp6_connections.xml --verbose --nwords 4 status
INFO:__main__:Setting up connection: file://ctp6_connections.xml
ctp6.frontend
Namespace(capture_char='0xbc', command='status', connection='ctp6_connections.xml', expected=None, links=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47], ncapture=4, power_down=False, verbose=True)
16-10-13 17:17:08.826981 [0x4c2bbb0] WARNING - Closing socket since deadline has passed
16-10-13 17:17:08.827262 [0x4c0c970] WARNING - Closing Socket since exception detected.
Traceback (most recent call last):
File "cli.py", line 167, in <module>
commands[args.command](hw, args)
File "cli.py", line 48, in do_status
status_flags = api.status(hw, args.links)
File "/scratch/tapas/ctp6commander/api.py", line 156, in status
hw.dispatch()
uhal._core.TcpTimeout:
I'm terribly sorry to have to tell you this, but it appears that there was an exception:
* Exception type: uhal::exception::TcpTimeout
* Description: Exception class to handle the case where the TCP connection timed out.
* Additional Information:
> ASIO reported a timeout in TCP read callback. Error code message is: "Operation canceled"
* Exception occured in thread with ID: 0x4c2bbb0
* Current thread has ID: 0x4c0c970
* Exception constructed at time: 2013-10-16 17:17:08.827123
* Exception's what() function called at time: 2013-10-16 17:17:08.827471
ekfriis commented
This is due to the fact that the CTP gets hung up and never returns the expected response. Once we fix uwcms/cms-calo-layer1#26 this should go away.