Uploaded image for project: ' AGL Development'
  1. AGL Development
  2. SPEC-2603

Multiple agl-services fail to start due to a 'Protocol Error'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • master
    • App Framework
    • None
    • "agl-demo agl-devel"
    • Renesas M3

      There is a sporadic issue on master.

      During system startup multiple agl-services fail to start.

       

        UNIT                                                              LOAD   ACTIVE SUB    DESCRIPTION                                                                                
      ● afm-service-agl-service-bluetooth-map--1.0-589ba36--main.service  loaded failed failed Binding for Bluetooth MAP profile                                                          
      ● afm-service-agl-service-bluetooth-pbap--1.0-f207663--main.service loaded failed failed Binding for Bluetooth Phonebook Access Profile                                             
      ● afm-service-agl-service-can-low-level--7.99--main.service         loaded failed failed Expose CAN Low Level APIs through AGL Framework                                            
      ● afm-service-agl-service-platform-info--6.90-099daf9--main.service loaded failed failed A binding meant to provide system, platform, build information for others bindings and apps
      ● afm-service-agl-service-unicens--0.1-b79d0ef--main.service        loaded failed failed UNICENS V2 - Infotainment network setup and access                                         
      ● rngd.service                                                      loaded failed failed Hardware RNG Entropy Gatherer Daemon                                                       
      ● sllin-demo.service                                                loaded failed failed LIN DEMO startup                                                                           
      ● ti-uim.service                                                    loaded failed failed User Mode Init Manager for TI shared transport  
      

       

      m3ulcb:~# journalctl -b | grep afm-service-agl
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-network--1.0-cc34edb--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-can-low-level--7.99--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-platform-info--6.90-099daf9--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-geoclue--1.0-f26b124--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-unicens--0.1-b79d0ef--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-bluetooth-map--1.0-589ba36--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-bluetooth-pbap--1.0-f207663--main.service: Failed with result 'protocol'.
      Jun 28 22:12:47 m3ulcb systemd[1]: afm-service-agl-service-bluetooth--2.0-28768d7--main.service: Failed with result 'protocol'.
      
      

      I attached a journal log.journal_startup_failed.log

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            jobol-iot jose bollo
            tjahnke Tobias Jahnke
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: