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

sure let's do that

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

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