Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
Install infinite loop
-
So to summarize...
You did the following:
- created the agent with the correct device type (lets stick to PI4 128755)
- went to the confirmation page to get the correct credentials and the script
- created the /etc/agentid with the mentioned credentials
- ran the script
And what you get is what you shared in the image you shared meaning the download is not happening which I can confirm since i can see that the agent is trying over and over to download the file...
Do you have any limitation imposed by your ISP or do have some firewall rules not allowing to download files from some sites?
Sorry for all these questions but the process is quite straightforward so I need to confirm the steps
-
@SBK I shouldn't have any limitations imposed by my isp.
As far as a firewall, I don't really have one active for this device. The router has a firewall but this device is exempt. This device is a raspberry pi 4 and is also used to run Pi-Hole. I disabled the filtering to download the script and it still won't work. I am wondering now if the Pi-Hole cannot provide DNS for itself. I will readjust the network settings so the device is not asking itself for DNS.
My other question is the script seems to be trying to download the otm from foxymon.com. In the post above it
@OutagesIO_Support said in Install infintie loop:I think it's supposed to be this.
ARM based agentthe website in his post is downloads.outagesio.com/otm/otm_1.62.206_arm which isn't the same. Unless the foxymon website is just forwarding a new file. But, when i navigate to the address in the script it loads an empty page when I inspect the page.
-
I try to explain but I really need to know if you can download that file from a normal browser .
In the script you will see the requests made to foxymon.com which is a factory of servers answering requests from all the agents.
The file I am sending you is the file that the your PI is trying to download so eventually you can try with a wget and see if the file is downloaded onto the pi4 device
-
-
"hold the phone!" :-)
If you can download the file from the PI4 using wget then the issue must be different.In the script you can see there is a variable at the very beginning called start which says where the script and all the rest will be placed
Is it where you put the script? or is it another folder?
Can you double check that?And one more thing can you run the otm file you just downloaded?
-
Ok, we found a lead by doing an install on a pi device. Give us a little time to debug this and we'll give you a solution.
Thanks.
-
@OutagesIO_Support Sounds like a plan. Even though its not great that it is broken right now, I'm glad I am not totally crazy
-
Here's how you should proceed at this point.
All of those agents that you have in Created status, just let them expire. The will expire from your dashboard after 24hrs.
The site automatically does this to prevent confusion by leaving a bunch of non fully installed in the dashboard.
Create a new one, go through the process and it should work now. It's too bad people don't report problems more often so we can fix them. They just tend to find a problem and leave so it can be a while before we are even aware of any issues otherwise, we jump on them pretty quickly.
Just keep one thing in mind. There is a note that will show up saying that you have to comment out a line IF you are going to use systemd to start/stop your agent. If you don't, you'll end up with multiple instances running for no good reason.
You should be good to go now. let us know how things go.
-
@OutagesIO_Support I finally got it to work. Now I just have to troubleshoot getting the systemctl service up and going.
-
Nice to hear you got it. The problem was a simple case sensitivity in the script.
Remember, if you go with the systemd control, be sure to comment out the line mentioned in the script.
Thanks for bringing this to our attention glad it's working now.
-
Now while trying to start the service I get the following output in the terminal after following the instructions and commenting out the line in the script:
ā otm.service - Startup of the OutagesIO monitoring agent
Loaded: loaded (/etc/systemd/system/otm.service; enabled; vendor preset: enab
Active: activating (auto-restart) (Result: exit-code) since Thu 2022-02-17 23
Process: 9592 ExecStartPre=/agent/starter_aarch64_ocp.sh (code=exited, status=
lines 1-4/4 (END)...skipping...
ā otm.service - Startup of the OutagesIO monitoring agent
Loaded: loaded (/etc/systemd/system/otm.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2022-02-17 23:14:25 GMT; 2s ago
Process: 9592 ExecStartPre=/agent/starter_aarch64_ocp.sh (code=exited, status=203/EXEC)any ideas?
-
I'm sorry you're still experiencing problems.
We provide some scripts and tips that we use in-house but when it comes to operating systems, you would have to post this in some Linux or pi forums.
We were just working with that a while ago and didn't have any problems so not really sure where to start. I'll try to look at this tomorrow.
Can you tell me what post/article you are following and I can review that tomorrow.
-
@OutagesIO_Support don't worry about it. I have gotten way better customer support for this "free" product than i get for most paid products. I will be promoting your services to my data center pals that manage the centers.
-
Thanks for your nice comment.
We work very hard on this service in the hopes that it can help people since there is not a lot out there that isn't overly technical for the average consumer. With input and feedback, we keep trying to make it as easy as possible to use.
Unfortunately, we don't have the resources to support every operating system out there but hoping that in time, as enough people start using these forums, members can also help each other where we might not have the knowledge.
We installed the agent and service on a pi device earlier so we could go through all of the steps and didn't have any problem but maybe we're so used to setting things up that we didn't notice something.
I'll give it another try tomorrow while reading the blog post which I assume you were looking at too.
Monitor Your Internet With Raspberry Pi 3A, 3B+, 4, NanoPi, And Other ARM Devices
-
I'm sorry I've not gotten back to you on this. It is still in my list of things to do. The days are just too short to get everything done and we're also in the middle of a hardware upgrade.
I hope I can get to this next week perhaps.
-
Hi, it took a while but the article was updated with a fix.
Another member decided to look deeper into this and found there was one small error in the script which prevented the systemd service from starting the agent.
The script is now updated and available for all Pi devices. The blog article was also updated a little bit.
See if that helps now.
