Information and Support

sure let's do that :+1:

i think if it got into the Unraid app store you'd probably get a lot of installs, but I think you'd at least need the heartbeat status included in the free version otherwise it would be unsupportable.

Free includes everything in the light view right?

@outagesio_support I guess I'd look at it the other way and think of who would pay for the paid version then try to increase userbase on the free. Users like myself would never pay the fee for premium not because I think the service isn't worth it (i'm here discussing with you after all) but because for $70 a year i could get a small vm for the same sort of money I could also do other stuff with.

The data produced has value too because if it gained enough support it could hold ISPs to account, which is what attracted me to what you guys were doing in the first place.

Where are the costs? My guess

• Development which you have to do anyway
• Hosting the service (graphs, analytics)
• Hosting the endpoint
• Building support for the agents on different platforms.

The last two you could get community support with, the first two if you wanted community support you'd have to open source your software which you likely don't want to do or you would have done it already. Maybe if the agent wrote metrics locally in a logfile or something that could be included in free?

I haven't fixed it, the Debian based container works now so I guess you updated the agent in the last few weeks. The issue you refer to occurs in the alpine Linux container, I could take a look at that later.

So I think the docker image I provided works so you can probably run that at your end and test it. I also provided a template to run this in unraid which should work on unraid too.

I do think that the data provided without subscription isn't enough for people to feel it worth to run the container I created, personally if I couldn't verify it was running I'd just delete it. Happy to discuss this further of you want to.

@outagesio_support sure, 128433

@outagesio_support said in outages.io in a docker container:

linux-vdso.so.1

I didn't change anything my end, reinstalled my container (which pulls down the latest agent) and I think it's connected now. I'm not able to see any stats though because seems you charge for this now. How do I verify it's connected?

Hi,
I want to run outages.io in a container and then add it to the Unraid appstore.

I have done this using Debian but it's quite large, also the agent isn't connecting. I'll post about that after I've done some more troubleshooting. Links below for reference.
https://github.com/peachy-ch/docker-templates
https://hub.docker.com/r/peachych/outagesio

Ultimately I'd like to run this on Alpine Linux so it ends up small, but I get the following issue that prevents me from running the binary, any idea what this issue is?

/otm # ldd otm_linux
/lib64/ld-linux-x86-64.so.2 (0x7f360a322000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f360a322000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f360a181000)
libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f360a322000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f360a167000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f360a322000)
Error relocating otm_linux: __res_init: symbol not found

Quick update:

• My kitchen lights work again therefore my missus hasn't kicked me out on the street

• I haven't electrocuted myself again

• I found and ordered a $3 device with the same chipset as the Shelly to try to run outagesio on. Don't think it's arm so we might need to jointly geek out to get this working

I had issues getting it running at boot too, i actually just hacked it in the end and ran a Cron job to check if it's running and start if not.

I've concluded I'm fine with this since I want it running all the time.

If we get loads more people with the same issue I'll take a proper look at it

It seems reliable. Probably a bunch of them were me testing stuff :D

I have a Shelly wired up, I'll take a look at that soon. In installing the Shelly's I electrocuted myself and have taken out half the electrics in my kitchen, so unless you are more scary than my missus you'll need to wait whilst I sort that first 😂

let's see how it runs for a week.

I'd say the cheaper device with 256mb memory would also run fine if you only want to run outagesio on it, the os and outages is currently using less than 90mb.

One limitation on this device is the 100mb network card, the agent is consistently hitting this limit in it's speed tests. Personally I don't think this matters, I'm more interested in degradation in general or at specific points of the day, but it may be important to others.

I would strongly recommend that anybody that buys one of these gets it from the same store i bought from, Aliexpress can be a minefield of copies of copies.

The Shelly is going to be a bit more work, because i don't have experience with Mongoose OS or Tasmota, i will get round to it soon.

[attachment]Photo_-_Google_Photos.jpg[/attachment]" />

So it arrived, it's tiny, put here next to a mouse for perspective.

I did the following
* Downloaded armbian from here [](https://www.armbian.com/orange-pi-zero/)[https://www.armbian.com/orange-pi-zero/](https://www.armbian.com/orange-pi-zero/)
* Flashed armbian to the sd card using etcher [](https://www.balena.io/etcher/)[https://www.balena.io/etcher/](https://www.balena.io/etcher/) and put card in Orange Pi
* Plugged network cable into switch and Orange pi
* Plugged usb cable into micro usb port, this device is quite low power so no special usb power block needed
* Went to my router to see what IP address the Pi had been assigned
* sshed to root@ using password 1234
* Went through the password change you are prompted to do first time
* apt update to update repos then apt upgrade to update all software
* mkdir /opt
* created new outages agent in the control panel type Raspberry Pi 3B+ and downloaded the agent
* copied agent to Orange Pi scp otm_1.58.2002_arm root@<ip address="">:/otm</ip>
* created /etc/agentid per instructions on agent page
* made agent executable chmod 755 /opt/otm_1.58.2002_arm
* ran agent with /otm/otm_1.58.2002_arm &

So it's now running a treat via the wired interface. I also have it connected to wireless so could monitor as a wireless client if i wanted to.

How to connect to wireless?

BSD version I'm able to test if you have something

Not yet Alex, I bought 10 of them on a "deal of the day" offer when my missus explicitly told m not to buy them. I now have to wait for an opportunity to covertly install them when she is not around :lol:

I just read the note in the "Informational" about this and was also chatting to Mike over email but I still don't really understand your speed tests.

> However, after we stopped testing but continued transferring the file, the 50Mbps connection was very slow, very sluggish, trying to pull up a web site on a very fast remote site that we often use was not fast, it was very slow to load the page, taking nearly 30 seconds.
I don't understand the point here, a web site is much more complicated to measure that a file transfer. Where was the time taken? Initial connection (slow webserver), pulling down the elements of the page (webserver or connection), rendering the page?

I'm getting about 2-300Mbps on my wired speedtest, it's still useful in that i will spot a relative degradation but i'm pretty sure if we used iperf or qperf to test between our connections we'd almost always get 1000Mbps.

I'm assuming (and reading between the lines in your article) that you are concerned ISPs might have traffic shaping in place that would e.g. throttle a connection. So if we want to test a 1000Mbps line we'd ideally xfer a 1TB file or something, but then of course I'd see a degradation in performance over the duration of this test, so you have to xfer a smaller file and calculate up?

My guess is the speedtest uses a very small file and so on my big connection it's measuring the time taken to establish the connection too which is why it nets out at about a quarter actually bandwidth?

It's ok now Mike, thanks.

Could the latest version and binary per release be made available somewhere so that we could access it programatically?

Think there is a problem with the download link, the CP told me to update, i click to download and get

The webpage at https://app.outagesio.com/agent/downloadSoftware/id/36 ERR_INVALID_RESPONSE

Coin sized linux device: https://shelly.cloud/shelly1-open-source/

I actually have a bunch of these I haven't installed yet, I'll have a poke around in the OS at some point and see if outages could run on it.

You could monitor your internet connection from every lightswitch :)

I'm thinking the device I linked above could serve as a pi hole too, just want to nerd out to be honest 8-)

I want to get to a sub $20 embedded PC to run as an outages-io monitor, I'm not quite there yet. I've ordered the following which is coming in at $21.49, the SD card might end up being junk, I'll have to find a power supply, but I have loads lying around.

Here is exactly what I've ordered

Embedded PC

Sd Card

I'll let you know when it arrives (probably a few months), I plan to install debian on it.

Very interested to hear about anybody elses experience with low cost hardware devices.