Tracking Server Uptimes
Unlike some other OS's, Linux almost never has to reboot… or so I was told when I first started learning about it. To illustrate the point, my mentor introduced me to an app that he ran on all of his servers called uptimed. It is similar to the utility that most of us have heard of, uptime, except that it runs as a daemon and logs the system's uptime instead of just reading info that is lost on a reboot. Uptimed provides a secondary command called uprecords that give statistics and makes it easy to see how long your server has been up, what the longest it has ever been up is, when it rebooted, and more.
Until recently, I just took for granted that this wonderful app was still being maintained since it has always been available to me… enter CentOS 6. Even with the usual suspects added to my list of available repositories it was nowhere to be found. My roots are in Gentoo so I decided to take a look at its ebuild (uptimed-0.3.16-r4.ebuild) and see where they pulled it from. Based on that I was able to find the source and, sadly, find that it is not being maintained anymore. The logical solution: grab the source and build my own RPM that could be distributed where I work… that too was a no-go due to dependency on an older version of automake.
The bottom line: if you run Gentoo or Ubuntu you can still grab uptimed via your package manager. As for the rest of us, hopefully someone will read this and either decide to pickup maintenance or be able to enlighten us to a good alternative.
- Thanks to help from a commenter below I have been able to build and install uptimed on 64-bit CentOS 6. I am working on setting things up so I can publish my changes.
- Source that is patched for CentOS 6 is now available on GitHub. Check out uptimed.technicalissues.us for more info.
Gene Liverman is a Systems Administrator of *nix and VMware at a university.
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Non-Linux FOSS: libnotify, OS X Style
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- RSS Feeds
- Reply to comment | Linux Journal
1 hour 50 min ago
- Yeah, user namespaces are
3 hours 6 min ago
- Cari Uang
6 hours 38 min ago
- user namespaces
9 hours 31 min ago
9 hours 57 min ago
- One advantage with VMs
12 hours 25 min ago
- about info
12 hours 59 min ago
13 hours 4 sec ago
13 hours 58 sec ago
13 hours 3 min ago