signal-composer connect to low-can error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, AGL

 

I am new member in AGL. Recently 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.

 

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'.

 

Best regards,

Ouyang

 

 

--------------------------------------------------

Ouyang Jun

Development Dept.III

Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)

No.6 Wenzhu Road, Software Avenue, Nanjing, 210012, China

TEL: +86+25-86630566-9453

Mail: ouyangj.fnst@xxxxxxxxxxxxxx

--------------------------------------------------

 

_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux