Skip to main content

Failed CoreOS Services

I'm not going to describe how fleetd and systemd work together. That's better researched on the CoreOS site. But I am going to describe a condition that I often find myself in.  My rig is like this.
  • I have a Chromebook running "terminal"
  • my remote CoreOS servers are typically at Google Compute Engine
  • and I use a blend of tools installed in a dedicated docker container
However, from time to time; when I log into my CoreOS instance I get this crazy error message about some "failed unit". After a quick investigation:
  • systemctl status
  • systemctl list-units
  • systemctl --failed
I determined that my ssh session had terminated and left some breadcrumbs behind. I'm exactly sure why the session died but it is common. There must be some idle timer on the chrome-terminal application that I have not configured properly because when I have a similar session open on my macbook it remains open longer.

On one occasion I noticed that I had multiple failed units and I was never able to determine what happened. After some additional systemd research I was able to find away to remove the symptoms.
  • systemctl stop sshd@60338-x.y.z.a:22-a.b.c.d:54566.service
  • systemctl unload sshd@60338-x.y.z.a:22-a.b.c.d:54566.service
  • systemctl reset-failed sshd@60338-x.y.z.a:22-a.b.c.d:54566.service
I'm fairly certain it was the last one that actually cleared the dead unit. The other two did not seem to do anything meaningful.  Also, I needed to prefix the commands with the 'sudo' command.

UPDATE:
systemctl --failed | grep "service loaded" | sed -e 's/^.*\(sshd.*service\).*$/\1/' | xargs -n 1 -I {} sudo systemctl stop {}

systemctl --failed | grep "service loaded" | sed -e 's/^.*\(sshd.*service\).*$/\1/' | xargs -n 1 -I {} sudo systemctl reset-failed {}


UPDATE:  In the previous UPDATE I wrote two one-liners.  They both work, and that's all you need. However, while testing the results I executed the two scripts from the clipboard; then I logged off and reconnected very quickly.  I noticed that that CoreOS' motd still displayed the 10 failed units I had previously cleaned. I tried the root command 'systemctl --failed' and it returned '0 failed'.  I then logged out and back in (second time) and the failed units were no longer displayed in the motd. I must have been too fast on the keyboard when I sent the initial cleanup one-liners.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…