| Re: [leda-dev] SeatAdjusterApp launch in Leda |
|
Hello, I updated the Dockerfile maintaining only Kanto container manifest and added the
extra_hosts tag, yet I still see no change. Attached the file for your reference. On comparing the logs between Velocitas and Leda, I see that the log of “Topic registered” for the MQTT in Velocitas is logged only by DAPR runtime. The application proceeds to display log for subscription of data broker.
PFA for reference. For better understanding, I also tried to compare seat-service logs of Leda and run-seatservice in Velocitas. Isn’t it expected to log in a similar fashion? Regards, Antara From: leda-dev <leda-dev-bounces@xxxxxxxxxxx>
On Behalf Of Haller Mike (ETAS-E2E/XPC-Fe1) Hi, the attached container manifest looks like a merged Velocitas application manifest (Port, DAPR_GRPC_PORT, VehicleModel, dependencies) and a Kanto Container Manifest
(container_id, container_name, image, host_config etc.) You cannot just “merge” two different types of JSON configurations into a single file. Kanto may be ignoring the Velocitas keys, but it’s not the right way to copy everything into a single file and hope for the best. Coming to the problem that the application is not connecting to databroker, and I actually assume that it also does not connect to the MQTT broker. It says “Registering
topic”, which is an indication that the code WANTS to register, but there is no further log, so it may as well not be able to connect. Otherwise it should log something like “Topic registered” Since there is no “extra_hosts” defined, the application container may not resolve the IP addresses of the services correctly. I guess you’re missing this part in the container deployment manifest: "host_config":
{ … "extra_hosts": [ "databroker:container_databroker-host", "mosquitto:host_ip" ], … } Regards Mike Von: leda-dev <leda-dev-bounces@xxxxxxxxxxx>
Im Auftrag von Antara Dey Hello Leda Community, I am a student currently working at ITK. I, and my team have been exploring Eclipse Leda, to understand its underlying functionality and how it interacts with the contributor pieces of SDV.
I am currently facing a challenge with debugging the application container in Leda and seek some support on it. First, I used to Velocitas examples tutorial to launch the services in VS Code and traced the logs.
Then, I followed the Leda documentation and launched the Seat Adjuster Vehicle App as a Kanto-CM container in Leda. I used the Dockerfile from Velocitas repository to create a docker image – which includes the necessary
modifications for it to work. All other containers are also successfully up and running. Issue: The
SeatAdjusterApp does not work as expected in Leda. It does not launch completely. It subscribes to MQTT topic /seatadjuster/setPosition/request. But, as seen from the Kantui logs, it fails to further subscribe to the VehicleDataBroker. Due to this, the
MQTT publish message command (move seat position) does not render any output from the app. The functionality of the application works as expected in Velocitas. I have attached the Container Manifest, Dockerfile and Kantui logs for your reference.
Kindly provide support and/or information on this issue to proceed further.
Best regards, Antara Dey Work Student ITK Engineering GmbH, Stuttgart-Vaihingen |
== APP == /home/antara/Projects/vehicle-app-python-sdk-0.8.2/./examples/seat-adjuster/src/main.py:116: DeprecationWarning: There is no current event loop
== APP == LOOP = asyncio.get_event_loop()
== APP == 2023-06-05 07:13:12,285 INFO [__main__] [main.py:111] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - Starting seat adjuster app...
== APP == 2023-06-05 07:13:12,285 DEBUG [sdv.vehicle_app] [vehicle_app.py:72] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - VehicleApp instantiation successfully done
== APP == 2023-06-05 07:13:12,286 DEBUG [sdv.dapr._servicier] [_servicier.py:66] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - Registering topic 'seatadjuster/setPosition/request'
INFO[0000] application discovered on port 50008 app_id=seatadjuster instance=osboxes scope=dapr.runtime type=log ver=1.10.2
INFO[0000] actors: state store is not configured - this is okay for clients but services with hosted actors will fail to initialize! app_id=seatadjuster instance=osboxes scope=dapr.runtime type=log ver=1.10.2
INFO[0000] actor runtime started. actor idle timeout: 1h0m0s. actor scan interval: 30s app_id=seatadjuster instance=osboxes scope=dapr.runtime.actor type=log ver=1.10.2
INFO[0000] configuring workflow engine with actors backend app_id=seatadjuster instance=osboxes scope=dapr.runtime.wfengine type=log ver=1.10.2
INFO[0000] Registering component for dapr workflow engine... app_id=seatadjuster instance=osboxes scope=dapr.runtime type=log ver=1.10.2
INFO[0000] initializing Dapr workflow component app_id=seatadjuster component="dapr (workflow.dapr/v1)" instance=osboxes scope=dapr.contrib type=log ver=1.10.2
== APP == 2023-06-05 07:13:12,317 INFO [sdv.dapr.client] [client.py:70] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - Waiting for dapr sidecar...
INFO[0000] app is subscribed to the following topics: [seatadjuster/setPosition/request] through pubsub=mqtt-pubsub app_id=seatadjuster instance=osboxes scope=dapr.runtime type=log ver=1.10.2
INFO[0000] MQTT is subscribed to topic seatadjuster/setPosition/request (qos: 1) app_id=seatadjuster component="mqtt-pubsub (pubsub.mqtt/v1)" instance=osboxes scope=dapr.contrib type=log ver=1.10.2
INFO[0000] dapr initialized. Status: Running. Init Elapsed 275ms app_id=seatadjuster instance=osboxes scope=dapr.runtime type=log ver=1.10.2
INFO[0000] placement tables updated, version: 0 app_id=seatadjuster instance=osboxes scope=dapr.runtime.actor.internal.placement type=log ver=1.10.2
== APP == 2023-06-05 07:13:12,419 DEBUG [sdv.dapr.client] [client.py:65] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - dapr: Health endpoint returned status code: 204
== APP == 2023-06-05 07:13:12,419 INFO [sdv.vdb.subscriptions] [subscriptions.py:72] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - Subscribing to SELECT Vehicle.Cabin.Seat.Row1.Pos1.Position
== APP == 2023-06-05 07:13:12,420 DEBUG [sdv.dapr.client] [client.py:65] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - dapr: Health endpoint returned status code: 204
== APP == 2023-06-05 07:13:12,509 DEBUG [sdv.dapr.client] [client.py:45] [trace_id=39219f58f0340a2c4697b97077a57a2f span_id=e7f9314a48c85e30 resource.service.name=./examples/seat-adjuster/src/main.py] - Published an event data :{"position": 420} to the specified MQTT topic: seatadjuster/currentPosition
â¹ï¸ Updating metadata for appPID: 110438
â¹ï¸ Updating metadata for app command: python3 ./examples/seat-adjuster/src/main.py
â
You're up and running! Both Dapr and your app logs will appear here.
Attachment:
seatadjuster-app.json
Description: seatadjuster-app.json