{"action":"created","issue":{"url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/40","repository_url":"https://api.github.com/repos/ipbus/ipbus-firmware","labels_url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/40/labels{/name}","comments_url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/40/comments","events_url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/40/events","html_url":"https://github.com/ipbus/ipbus-firmware/issues/40","id":315514542,"number":40,"title":"Request for hints on Debugging Control hub","user":{"login":"DavidCussans","id":5689642,"avatar_url":"https://avatars1.githubusercontent.com/u/5689642?v=4","gravatar_id":"","url":"https://api.github.com/users/DavidCussans","html_url":"https://github.com/DavidCussans","followers_url":"https://api.github.com/users/DavidCussans/followers","following_url":"https://api.github.com/users/DavidCussans/following{/other_user}","gists_url":"https://api.github.com/users/DavidCussans/gists{/gist_id}","starred_url":"https://api.github.com/users/DavidCussans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DavidCussans/subscriptions","organizations_url":"https://api.github.com/users/DavidCussans/orgs","repos_url":"https://api.github.com/users/DavidCussans/repos","events_url":"https://api.github.com/users/DavidCussans/events{/privacy}","received_events_url":"https://api.github.com/users/DavidCussans/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-04-18T14:51:08Z","updated_at":"2018-04-18T16:04:45Z","closed_at":"2018-04-18T15:04:10Z","author_association":"NONE","body":"\r\nWe are having troubles connecting via the control hub.\r\n\r\nWe have compiled IPBus  and the control_hub on Ubuntu 14.04\r\n\r\nIPBus communication direct to the hardware ( uri=\"ipbusudp-2.0://192.168.200.30:50001\" ) works but is * very* slow.\r\n\r\nThe control hub seems to start up OK:\r\n\r\nteleuser@azalea-runcontrol:~/software/eudaq-master$ /opt/cactus/bin/controlhub_info \r\nThe ControlHub is running. General info ...\r\n    started at 2018-04-18 14:19:27 UTC\r\n    uptime:    0 days, 0 hours, 24 minutes, 19 seconds\r\n    version:   2.6.0\r\n    config file: /etc/controlhub/default/sys.config\r\n\r\nDevice client parameters ...\r\n    max packets in flight to each board = 16\r\n    timeout for replies from board = 20ms\r\n    device client lifetime when inactive = 15000ms\r\n\r\nTCP parameters ...\r\n    Listening on port 10203\r\n\r\n\r\n----------------------------------------------------------\r\nteleuser@azalea-runcontrol:~/software/eudaq-master$ /opt/cactus/bin/controlhub_status\r\nThe ControlHub is up (version 2.6.0, pid=23498)\r\n\r\n-----------------------------------------------------------\r\n\r\n\r\nteleuser@azalea-runcontrol:~/software/eudaq-master$ /opt/cactus/bin/controlhub_stats\r\nControl Hub Stats Report\r\n------------------------\r\n\r\nCLIENT  All-time connections: 32\r\n          Active connections: 1 (peak: 1)\r\n  @ 127.0.0.1:48440\r\n           Requests received: 1 (of which 0 were malformed)\r\n              Responses sent: 1\r\n  Old clients\r\n           Requests received: 31 (of which 0 were malformed)\r\n              Responses sent: 31\r\n\r\nOld UDP\r\n              Packets Out: 32\r\n               Packets In: 0\r\n                 Timeouts: 0 in normal operation (of which 0 were recovered)\r\n                             (0 request packets got lost, 0 reply packet)\r\n           Other timeouts: 160 (status), 0 (in resends)\r\n\r\n-----------------------------------\r\n\r\n... however, when we try to connect via the control hub we see errors. Extract from the log:\r\n\r\n18-04-18 16:21:14.006563 [7f231a191700] INFO - URI \"chtcp-1.3://localhost:10203?target=192.168.200.30:50001\" parsed as:\r\n > protocol : chtcp-1.3\r\n > hostname : localhost\r\n > port : 10203\r\n > path : \r\n > extension : \r\n > arguments :\r\n   > target = 192.168.200.30:50001\r\n\r\n18-04-18 16:21:14.006763 [7f231a191700] INFO - Converted IP address string \"192.168.200.30:50001\" to 192.168.200.30:50001 and converted this to IP 0xC0A8C81E, port 0xC351\r\n18-04-18 16:21:14.007685 [7f231a191700] INFO - Attempting to create TCP connection to 'localhost' port 10203.\r\n18-04-18 16:21:14.007847 [7f231a191700] INFO - TCP connection succeeded\r\n18-04-18 16:21:14.113072 [7f231977e700] ERROR - The ControlHub did not receive any response from the target with URI \"chtcp-1.3://localhost:10203?target=192.168.200.30:50001\"\r\n18-04-18 16:21:14.113114 [7f231977e700] ERROR - ControlHub returned error code 3 = 'no reply to status packet'\r\n18-04-18 16:21:14.113311 [7f231a191700] WARNING - Closing TCP socket for device with URI \"chtcp-1.3://localhost:10203?target=192.168.200.30:50001\" since exception detected.\r\n18-04-18 16:21:14.113375 [7f231a191700] INFO - function \"void uhal::ControlHub<InnerProtocol>::dispatchExceptionHandler() [with InnerProtocol = uhal::IPbus<1u, 3u>]\" in /home/teleuser/software/ipbus-software/uhal/uhal/src/common/ProtocolControlHub.cpp, line 292.\r\n18-04-18 16:21:14.113395 [7f231a191700] INFO - function \"void uhal::IPbus<1u, IPbus_minor>::dispatchExceptionHandler() [with unsigned char IPbus_minor = 3u]\" in /home/teleuser/software/ipbus-software/uhal/uhal/src/common/ProtocolIPbus.cpp, line 218.\r\n18-04-18 16:21:14.113408 [7f231a191700] INFO - function \"virtual void uhal::IPbusCore::dispatchExceptionHandler()\" in /home/teleuser/software/ipbus-software/uhal/uhal/src/common/ProtocolIPbusCore.cpp, line 577.\r\n\r\nDoes anybody have any ideas about how to debug this issue?\r\n\r\nWe used almost identical firmware in the past with no problems, using a CentOS7 machine running the control hub and our IPBus application.\r\n\r\nMany Thanks!\r\n\r\nDavid\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/comments/382440203","html_url":"https://github.com/ipbus/ipbus-firmware/issues/40#issuecomment-382440203","issue_url":"https://api.github.com/repos/ipbus/ipbus-firmware/issues/40","id":382440203,"user":{"login":"DavidCussans","id":5689642,"avatar_url":"https://avatars1.githubusercontent.com/u/5689642?v=4","gravatar_id":"","url":"https://api.github.com/users/DavidCussans","html_url":"https://github.com/DavidCussans","followers_url":"https://api.github.com/users/DavidCussans/followers","following_url":"https://api.github.com/users/DavidCussans/following{/other_user}","gists_url":"https://api.github.com/users/DavidCussans/gists{/gist_id}","starred_url":"https://api.github.com/users/DavidCussans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DavidCussans/subscriptions","organizations_url":"https://api.github.com/users/DavidCussans/orgs","repos_url":"https://api.github.com/users/DavidCussans/repos","events_url":"https://api.github.com/users/DavidCussans/events{/privacy}","received_events_url":"https://api.github.com/users/DavidCussans/received_events","type":"User","site_admin":false},"created_at":"2018-04-18T16:04:45Z","updated_at":"2018-04-18T16:04:45Z","author_association":"NONE","body":"Dave, Thanks . Yes, indeed chtcp-2.0 works better\r\n\r\nThe online documentation confused me - I just cut and pasted from a line mentioning chtcp-1.3 in https://ipbus.web.cern.ch/ipbus/doc/user/html/software/uhalQuickTutorial.html#creating-a-connection-file , although it does mention chtcp-2.0 later on.\r\n"}}
{"actor":{"display_login":"DavidCussans"}}