signal-composer start failed
Description
Environment
Attachments
- 30 May 2019, 06:43 AM
- 30 May 2019, 06:43 AM
- 30 May 2019, 06:43 AM
- 24 Apr 2019, 09:29 AM
- 12 Apr 2019, 08:56 AM
- 12 Apr 2019, 08:56 AM
- 12 Apr 2019, 08:56 AM
- 12 Apr 2019, 08:56 AM
- 10 Apr 2019, 08:53 AM
is blocked by
Activity
Walt Miner July 9, 2019 at 3:27 PM
Close for HH RC3
Jun Ouyang May 30, 2019 at 6:44 AM
@jose bollo @Romain Forlot
Thank you for your reply.
I try to use signal-composer connect to low-can, then I use the etc/control-basic-conf.json, copy control-basic-conf.json to control-signal-composer.json, then do command
“systemctl start afm-service-signal-composer--7.0--main@0.service”, but failed, there have some error that I don’t know how to fix it.
Used agl-service-signal-composer_git.bb
file , control-signal-composer.json file and details log log-7.0.2.txt in attachment.
ENV:
AGL : Guppy 7.0.2
Board : M3
agl-service-signal-composer_git.bb :
SRCREV = "cbfe3d859515a593fbad5edd82f5a9162749476b"
Error log:
m3ulcb:~# systemctl status afm-service-signal-composer--7.0--main@0.service
● afm-service-signal-composer--7.0--main@0.service - Signal composer API connected to low level AGL services
Loaded: loaded (/usr/local/lib/systemd/system/afm-service-signal-composer--7.0--main@.service; static; vendor preset: enabled)
Active: failed (Result: protocol) since Tue 2019-05-14 10:21:05 UTC; 12s ago
Process: 12331 ExecStart=/usr/bin/afb-daemon --name afbd-signal-composer@7.0 --rootdir=/var/local/lib/afm/applications/signal-composer/7.0 --workdir=/home/0/app-data/signal-composer --verbose --verbose --monitoring --port=31021 --token=HELLO --roothttp=. --ws-client=unix:/run/user/0/apis/ws/low-can --ws-client=unix:/run/user/0/apis/ws/gps --binding=/var/local/lib/afm/applications/signal-composer/7.0/lib/afb-signal-composer.so --ws-server=sd:signal-composer (code=exited, status=1/FAILURE)
Process: 12325 ExecStartPre=/bin/mkdir -p /home/0/app-data/signal-composer (code=exited, status=0/SUCCESS)
Main PID: 12331 (code=exited, status=1/FAILURE)
CPU: 30ms
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: ERROR: ALERT! signal 11 received: Segmentation fault [/usr/src/debug/af-binder/guppy+gitAUTOINC+f878e8026a-r0/git/src/sig-monitor.c:226,on_signal_error]
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: ERROR: BACKTRACE due to signal Segmentation fault/11:
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: [1/1] afbd-signal-composer@7.0(+0x372e4) [0xaaaaad2ca2e4]
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: [/usr/src/debug/af-binder/guppy+gitAUTOINC+f878e8026a-r0/git/src/sig-monitor.c:78,dumpstack]
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: ERROR: binding [/var/local/lib/afm/applications/signal-composer/7.0/lib/afb-signal-composer.so] initialisation failed [/usr/src/debug/af-binder/guppy+gitAUTOINC+f878e8026a-r0/git/src/afb-api-so-v3.c:132,afb_api_so_v3_add]
May 14 10:21:05 m3ulcb afbd-signal-composer@7.0[12331]: ERROR: can't start the binding /var/local/lib/afm/applications/signal-composer/7.0/lib/afb-signal-composer.so [/usr/src/debug/af-binder/guppy+gitAUTOINC+f878e8026a-r0/git/src/main-afb-daemon.c:175,apiset_start_list]
May 14 10:21:05 m3ulcb systemd[1]: afm-service-signal-composer--7.0--main@0.service: Main process exited, code=exited, status=1/FAILURE
May 14 10:21:05 m3ulcb systemd[1]: Failed to start Signal composer API connected to low level AGL services.
May 14 10:21:05 m3ulcb systemd[1]: afm-service-signal-composer--7.0--main@0.service: Unit entered failed state.
May 14 10:21:05 m3ulcb systemd[1]: afm-service-signal-composer--7.0--main@0.service: Failed with result 'protocol'.control-signal-composer.json
zhiqiang wang April 24, 2019 at 9:29 AM(edited)
Today I tried as below:
I saw the issue SPEC2292 was fixed in guppy7.0.1, so I begun to use agl-service-signal-composer in guppy7.0.1.
At same time, I found that the version of signal-composer was not lastest, so in guppy7.0.1 I changed the recipe of signal-composer to point to the lastest version of master branch, then made a test enviroment.
Changed json files which in signal-composer-7.0.1.zip, and I did as description once more, the result was signal-compooser got " ERROR: Terminating signal 6 received:", please look log.txt in signal-composer-7.0.1.zip.
Romain Forlot April 19, 2019 at 3:47 PM
@zhiqiang wang:
The txc-binding is integrated as a virtual binding using the af Test framework feature and is under the test/afb-test/fixture directory from the signal-composer. However there is a binding that is come from that can be found in our GitHub here: https://github.com/iotbzh/txc-demo/tree/master/binding but it isn't packaged through Yocto. You could use it if you want to reproduce the demo using the txc json files.
You did not have any issue with your Json but the two GPS signals you define aren't valid because at subscription step it try to make an api call to the verb "subscribe" of the "gps" api and this return an error, so the signals are removed. This because GPS api require an argument that you did not provide, if I remember well about the GPS api. Indeed, as you did not indicate a "getSignals" key for your signal then the signal composer use the default action which is calling subscribe verb without argument. You can reuse the init section of the source if you want to fix that.
I'm not sure about your segfault. It is weird and I need to retry. I'll try to bring you an answer next week, if all is going well.
Walt Miner April 18, 2019 at 1:08 PM
Should be backported to Guppy as well.
Details
Details
Assignee
Reporter
Fix versions
Labels
Contract ID
Priority
Major
I was trying to use signal-composer to get data from low-can and gps, so I tried as below:
modify an application's config.xml file to require signal-composer.
<feature name="urn:AGL:widget:required-api"> <param name="signal-composer" value="ws"/> </feature>start the application and look at journalctl log.
With upper operation, I got the error log in log.txt.
Please help checking whether there are any errors existing.