Problem with XDS Server Connection when changing Port (student project)

Duplicate

Description

Hi,

I'm a student trying to build the "Hello World" application (https://docs.automotivelinux.org/docs/en/master/devguides/reference/xds/part-1/create-app-get-source-files.html) for the Renesas H3 Starter Kit (h3ulcb) using AGL XDS.

 

Therefore, I try to follow the steps on https://docs.automotivelinux.org/docs/en/master/getting_started/#developing-an-application but I am stuck on the step where the SDK is installed which is step 3 of "Get Ready to Create Your Application" (https://docs.automotivelinux.org/docs/en/master/getting_started/reference/getting-started/app-workflow-prep-app.html#using-xds).

 

Following the instructions at https://docs.automotivelinux.org/docs/en/master/devguides/reference/xds/part-1/install-sdk.html,  I put my self-built SDK installer into the $HOME/xds-workspace/sdks directory. But using the XDS to install the SDKs does not work.

 

XDS Dashboard:

When I start the XDS Dashboard and go to "SDKs" > "SDKS MANAGEMENT" it says "No data found" and I cannot choose any SDK for installation.

 

Command Line:

The command: 'xds-cli sdks ls -a -l' returns "No XDS Server connected"

The command: 'xds-cli sdks install --file $HOME/xds-workspace/agl/sdks/poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-aarch64-toolchain-6.0.4.sh -l' returns "No XDS Server Connected" as well.

 

For the XDS Server I used the Docker container solution (https://docs.automotivelinux.org/docs/en/master/devguides/reference/xds/part-1/server-part.html#docker-container ). I had to change the port to 8001 because 8000 did not work:

bash ./xds-docker-create-container.sh -id 1

I also changed "8000" to "8001" in the config files: /etc/xds/agent/agent-config.json and /etc/xds/server/server-config.json.

 

Is there anything wrong with the XDS Server or Client maybe?

Environment

Ubuntu 16.04

Attachments

5

Activity

Show:

Sebastien Douheret 
January 31, 2020 at 4:45 PM

Duplicate of 

Jan-Simon Moeller 
November 6, 2019 at 1:11 PM

Sebastien Douheret 
September 26, 2019 at 11:56 AM

Sorry for the delay in reply.
I just fixed some bugs and update SDKs list (see https://gerrit.automotivelinux.org/gerrit/c/src/xds/xds-server/+/22504)
So your can stop and start xds-server container in order to get the latest SDK DB file but I'm not sure that changes will resolved your problem.

I would think that your problem is more about host name resolution. Would you please tell me what is the result of following command :
 docker exec -t 01234  bash -x  host www.iot.bzh

Are you available tomorrow (Friday 27th) for a debug session using www.whereby.com/iotbzh ? 

Jonas Leopold 
September 10, 2019 at 7:14 AM

Yes, it is a self-built SDK, but I tried it with a pre-built SDK and had exactly the same problem.

I attached the output of both commands: debug_log.txt

Sebastien Douheret 
September 9, 2019 at 9:15 PM

Is it an SDK that you built by your own or did you download this SDK ?

Would you please try this command and tell me if you get an error ?

 

Note that you must replace 980f492bd498  by the ID of your docker container where xds-server is running

If you get an error, please send me output of this command (same as previous but with bash in debug mode) :

 

Depending from what I can analyse with this new log you will send, maybe a more efficient way to understand what is going wrong would be to have a video-call.
I propose to use http://whereby.com/iotbzh in order to share your screen.
But please let's first provide me new log and then we will see if video-call is needed or not.

 

 

Details

Assignee

Reporter

Labels

Contract ID

Components

Affects versions

Priority

Created September 5, 2019 at 9:01 AM
Updated February 14, 2020 at 7:02 PM
Resolved January 31, 2020 at 4:45 PM