• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Monitor your Internet service and provider

Information and Support

Automatically monitor your Internet service and provider with optional alerts to problems
Monitor your Internet services or devices to ensure they are always online. Tracks Internet connectivity and speeds with useful proof. For Windows, Linux, ARM (Raspberry, Tinker Board, etc).
Learn more by visiting www.outagesio.com

starter.sh not executing on PI 3B

Scheduled Pinned Locked Moved ARM
rpi-3bexec format erroragent wont start
3 Posts 2 Posters 77 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    bokusdeeddy
    wrote on last edited by
    #1

    My agent had been running in the past successfully (manually started). Recently I restarted my Pi 3B and tried to restart my agent and got the following error after successful download of OTM: "./starter.sh: line 60: /home/eddy/otm/otm_binary: cannot execute binary file: Exec format error". I had not changed anything, so why the error? I tried creating a new agent, and received the same error. I am executing starter.sh with root permissions (which as I said worked before). Any ideas?

    1 Reply Last reply
    1
  • OutagesIO_SupportO Offline
    OutagesIO_SupportO Offline
    OutagesIO_Support Moderator
    wrote on last edited by
    #2

    Hi,

    Let's start with some basic things.

    The first thing that comes to mind is, did you change the path to reflect where the agent is actually getting downloaded to;
    /home/edddy/otm

    I assume so because you said it was working before.

    Line 60 should be; $STARTING_FOLDER/$OTM_BINARY &

    Since you are using the script manually, then this line would not be commented but if the code cannot find that folder and the downloaded binary, that would be why it would not run.

    Make absolutely sure the path is correct to start with.

    Also, is your system up to date because there have been SSL changes with some packages. Just the other day, we found a Pi 4 that stopped working and after updating the packages, it worked again.

    Try doing a manual download of that agent to make sure it's not an ssl issue.
    curl -v https://downloads.outagesio.com/otm/arm64_otm_1_79_2302

    You don't have to create a new agent but if you do, remember to use the new credentials. Each agent you create generates its own credentials, you have to use the ones matching for that particular agent.

    Regards,
    OutagesIO Support

    Search engines favor deep pockets and popularity making it difficult to find services like OutagesIO.
    Would you please take a moment to leave a Google review, it could help improve our chances of being found.

    1 Reply Last reply
    0
  • OutagesIO_SupportO Offline
    OutagesIO_SupportO Offline
    OutagesIO_Support Moderator
    wrote last edited by
    #3

    Hi,

    Did you resolve this?

    Regards,
    OutagesIO Support

    Search engines favor deep pockets and popularity making it difficult to find services like OutagesIO.
    Would you please take a moment to leave a Google review, it could help improve our chances of being found.

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups