Illegal Instruction

Bug Report
22

Edward,

The error that you are seeing states Unable to read and parse agent config file at expected path... means that either the toml file does not exist in the expected directory, that it is not a toml file (it has a different extension), or formatting is not correct in the file. I have listed a couple suggestions below - please try them in the order listed and continue to move on to the next suggestion if the current one does not work:

  1. In your post from Aug 29, it looks like your toml file on your gateway is in this file location: C:\Users\v111405\Downloads. Is it still in this location? This file should be located in /home/losant-edge-agent/ based off your current Docker run command.

  2. Ensure that /home/losant-edge-agent/ is the absolute path to your config.toml file and that there aren’t other folders/directories before the home folder.

  3. Did you confirm that your toml file is definitely a toml file and not something like config.toml.iotgw?

  4. Can you create a new toml file within the /home/losant-edge-agent/ directory (you can delete the old one and create a new config.toml file OR create a new file with a new name like config_test.toml - if you create a new file with a new name, just a reminder to update your docker run file to look like below:

sudo docker run -d --restart always --name losant-agent -v /home/losant-edge-agent/data:/data -v /home/losant-edge-agent/config_test.toml:/etc/losant/losant-edge-agent-config.toml losant/edge-agent:1.11.0-alpine

Thank you Edward,
Kevin

23

Kevin,

Here are the answers below. Also I cut-n-pasted the content of the .toml file from your documentation page. This was the last issue you mentioned that the formatting was incorrect.

The error that you are seeing states Unable to read and parse agent config file at expected path... means that either the toml file does not exist in the expected directory, that it is not a toml file (it has a different extension), or formatting is not correct in the file. I have listed a couple suggestions below - please try them in the order listed and continue to move on to the next suggestion if the current one does not work:

  1. In your post from Aug 29, it looks like your toml file on your gateway is in this file location: C:\Users\v111405\Downloads . Is it still in this location? This file should be located in /home/losant-edge-agent/ based off your current Docker run command.
    [ECS] The path “C:\Users\v111405\Downloads” was just the path I copied the file to in order for me
    to attach it to this thread. I was on my home computer but the GW is on the other side of a
    VPN so I was not able to copy directly. Here is the actual location of the “config.toml” file

        admin@B7Z8N42:/home/losant-edge-agent$ pwd
        /home/losant-edge-agent

    admin@B7Z8N42:/home/losant-edge-agent$ ls
        config.toml  data

  2. Ensure that /home/losant-edge-agent/ is the absolute path to your config.toml file and that there aren’t other folders/directories before the home folder.
    [ECS] See “ls” and “pwd” command output above under #1. It show that the “config.toml” file is in
    the “/home/losant-edge-agent/”

  3. Did you confirm that your toml file is definitely a toml file and not something like config.toml.iotgw?
    [ECS] I believe the file is a .toml file and not another extension. I will delete it and recreate it. My
    experience with Linux that there are not hidden extensions display. What you see is what you
    get.

  4. Can you create a new toml file within the /home/losant-edge-agent/ directory (you can delete the old one and create a new config.toml file OR create a new file with a new name like config_test.toml - if you create a new file with a new name, just a reminder to update your docker run file to look like below:
    [ECS] I will delete and re-create the .toml file as “config.toml”. Again, I will cut-n-paste the contents
    from your documentation page

25

Kevin,

I deleted the config.toml file and re-created it from scratch and used the command that you provided in the previous post. It is now working as expected. Obviously there was something wrong with the previous version. My take is that the “content” was not correct. Thanks for the help. Please let us know when there is a “bug fix” for the “alpine” issue so we can upload and test the new image/container

ed

26

Edward,

Thank you for the follow up letting us know that you got it working, great work! I will be sure to update this post when we have fixed the issue that we are seeing in the non-alpine Losant Edge Agent v1.10.0 and v1.11.0 when running on an ATOM processor.

Thank you for initially reporting this bug!
Kevin

29

Kevin,

Do you have any status on when a new Losant Edge Agent might be available that addresses/resolves the issue of the agent crashing with the “Illegal Instruction” when running on the GW with the ATOM processor? Just curious as we want to upgrade our lab environment as soon as possible

thanks

ed

31

@Edward_Szajner,

You have awesome timing. We just released a new verion of the Edge Agent that addresses your issue:

https://docs.losant.com/edge-compute/edge-agent-changelog/

1 Like
33

FYI,

I just downloaded the Losant Edge 1.12.0 to my Dell 3002 GW with the ATOM processor that was experiencing the “Illegal Instruction” issue. I am happy to say that this image has appeared to resolve the issue. Thanks for the help on this one. Now running and successfully linked to my Losant Cloud application

ed

3 Likes