AJTCL sample code execution on RaspberryPI

asked 2015-04-15 05:01:13 -0800

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

Hi, I am trying to execute sample "signal_service" and "signal_client" code using AJTCL on RaspberryPI on command line, with alljoyn-daemon router. Signal_service app execution is failing with errno="Address family not supported by protocol" status=AJ_ERR_READ. I have successfully built AJTCL on raspberryPI as stated in this link https://wiki.allseenalliance.org/develop/building_and_running#raspberry_pi_-_alljoyn-js . Looking for help on how to proceed further. Kindly share your comments.

edit retag flag offensive close merge delete

Comments

Im trying to narrow down where this error was printed. Can you please provide the full line that was printed not just the errno. Something like "000.123 aj_net.c:345 someFunction() errno=...". I have seen something similar on the Yun but this error had no effect, everything connected and continued as normal. It was because the Yun doesn't support IPv6.

jprestwo ( 2015-04-15 09:05:05 -0800 )edit

000.000 aj_net.c:736 MCastup6(): socket() fails. errno="Address family not supported by protocol" status=AJ_ERR_READ.. I have gone through the aj_net.c where MCastup6() is for IPV6 where as Im working on IPV4. Need help on how to configure it to MCastup4().

kamble4u ( 2015-04-15 23:43:20 -0800 )edit

What exactly is happening after that error is printe?. It should continue execution as normal as that error doesn't return a fatal error up the call stack. Not having IPv6 functionality is fine, just as long as you can open an IPv4 socket.

jprestwo ( 2015-04-16 09:12:24 -0800 )edit

On basic_service terminal AJ_StartService() connect failed. on basic_client terminal I am getting "Client timed-out trying to connect to bus" and exiting with status 7. On Router terminal simply it shows the router is running.

kamble4u ( 2015-04-17 05:06:50 -0800 )edit

So both basic_client and basic_service cannot connect to the routing node. Are you sure they are on the same WiFi/Ethernet network (with the same subnet) and that the access point has multicast turned on?

jprestwo ( 2015-04-17 08:51:36 -0800 )edit