WP7607-1 - Legato doesn't start after reboot


#1

Hi,

This issue happens very rarely, but if I reboot several times (using “reboot” cmd), I noticed that sometimes the legato framework won’t be running.

I’m running legato 18.06.3_dc55d84226223a3798b01c1a272e9603.

legato status:

root@swi-mdm9x28-wp:~/logread# legato status
Systems installed:
  4 [good] <-- current
Legato framework is NOT running.

logread | grep legato:

root@swi-mdm9x28-wp:~/logread# logread | grep legato
Jan  1 00:05:49 swi-mdm9x28-wp user.info kernel: [    6.703953] block ubiblock2_0: created from ubi2:0(legato)
Jan  6 00:05:49 swi-mdm9x28-wp user.notice root: update-ld-cache: Updating ld.so.cache using [/legato/systems/current/lib]...
Jan  6 00:05:52 swi-mdm9x28-wp user.warn Legato: -WRN- | _UNKNOWN_[785]/framework T=main | LE_FILENAME BindMount() 1450 | '/legato' is already mounted.

df -h:

root@swi-mdm9x28-wp:~/logread# df -h
Filesystem                Size      Used Available Use% Mounted on
devtmpfs                256.0K      4.0K    252.0K   2% /dev
/dev/mapper/rt           16.3M     16.3M         0 100% /
mdev                    256.0K      4.0K    252.0K   2% /dev
tmpfs                    76.3M         0     76.3M   0% /dev/shm
tmpfs                    76.3M         0     76.3M   0% /run
tmpfs                    76.3M     40.0K     76.2M   0% /var
tmpfs                    76.3M     24.0K     76.2M   0% /tmp
mdev                    256.0K      4.0K    252.0K   2% /dev
tmpfs                    76.3M         0     76.3M   0% /dev/shm
tmpfs                    76.3M         0     76.3M   0% /run
tmpfs                    76.3M     40.0K     76.2M   0% /var
tmpfs                    76.3M     24.0K     76.2M   0% /tmp
/dev/ubi3_0             104.5M      1.7M     98.1M   2% /mnt/flash
/dev/ubiblock2_0          3.8M      3.8M         0 100% /mnt/legato
/dev/ubi4_0               8.7M     68.0K      8.1M   1% /mnt/userrw
overlay                 104.5M      1.7M     98.1M   2% /etc
overlay                 104.5M      1.7M     98.1M   2% /data
overlay                 104.5M      1.7M     98.1M   2% /lib/firmware
/dev/ubi3_0             104.5M      1.7M     98.1M   2% /home
/dev/ubiblock1_0         24.8M     24.8M         0 100% /firmware
/dev/ubi3_0             104.5M      1.7M     98.1M   2% /legato
tmpfs                    76.3M     24.0K     76.2M   0% /etc/ld.so.conf
tmpfs                    76.3M     24.0K     76.2M   0% /etc/ld.so.cache
tmpfs                    76.3M     24.0K     76.2M   0% /etc/hosts
tmpfs                    76.3M     24.0K     76.2M   0% /etc/resolv.conf

I see here that two entries are missing compared to when the legato framework starts properly. The following two entries are at the end of the previous list when legato starts successfully:

cgroupsRoot              77.6M         0     77.6M   0% /sys/fs/cgroup
/dev/ubi3_0             104.5M      2.0M     97.8M   2% /legato/systems/current

Note that none of my apps are installed as I tried to reproduce with the base system.

If I do legato start, the framework will be launched and everything will work properly, so I’m considering having a script running outside of legato to make sure it’s always launched:

root@swi-mdm9x28-wp:~/logread# legato start
Starting Legato...
update-ld-cache: Updating ld.so.cache using [/legato/systems/current/lib]...
update-ld-cache: Updating /etc/ld.so.cache ...
update-ld-cache: Removing stale mount [/etc/ld.so.cache]...

Thanks for your help,
Best regards,
Ben


#2

Hello,

Any news on this issue?

Thanks for your help,
Best regards