Volcane recently asked in ##infra-talk on Freenode if anyone knew of "some little tool that can be used in a cronjob for example to noop the the real task if say load avg is high or similar?"
I came up with the idea to use nagios plugins. So, for example, to check load average before running a task:
/usr/lib64/nagios/plugins/check_load -w 0.7,0.6,0.5 -c 0.9,0.8,0.7 >/dev/null && echo "Run the task here"
Substitute the values used for the -w and -c args as appropriate, or use a different plugin for different conditions.
I recently had need to install uwsgi on EL7 (CentOS 7, actually, but RHEL 7 will be the same).
I ended up rebuilding the uwsgi SRPM from Fedora 21 which was relatively straight-forward but it required a few tweaks to the .spec file. I also had to build a chain of dependencies: mongodb, perl-Cora, libecb, perl-EV, libev, zeromq, perl-BDB, perl-AnyEvent-BDB, perl-AnyEvent-AIO.
All packages (including SRPMs) are in my repo: http://repo.yo61.net/el/7/
For some undetermined reason, NFS fails when my SmartOS NAS is rebooted. statd fails to start and nlockmgr also fails.
These commands seem to fix it:
svcadm restart svc:/network/rpc/bind:default
svcadm clear svc:/network/nfs/status:default
sharectl set -p lockd_servers=80 nfs
svcadm clear svc:/network/nfs/nlockmgr:default
In his talk at Puppetconf 2013, James Fryman mentioned a blog post by James White which contains a list of guidelines for management which has come to be known as the jameswhite manifesto.
Here’s the same list but unconstrained by a fixed-width text box so you can actually read it. 🙂
- There is one system, not a collection of systems.
- The desired state of the system should be a known quantity.
- The “known quantity” must be machine parseable.
- The actual state of the system must self-correct to the desired state.
- The only authoritative source for the actual state of the system is the system.
- The entire system must be deployable using source media and text files.
On Buying Software
- Keep the components in the infrastructure simple so it will be better understood.
- All products must authenticate and authorize from external, configurable sources.
- Use small tools that interoperate well, not one “do everything poorly” product.
- Do not implement any product that no one in your organization has administered.
- “Administered” does not mean saw it in a rigged demo, online or otherwise.
- If you must deploy the product, hire someone who has implemented it before to do so.
- Do not author any code you would not buy.
- Do not implement any product that does not provide an API.
- The provided API must have all functionality that the application provides.
- The provided API must be tailored to more than one language and platform.
- Source code counts as an API, and may be restricted to one language or platform.
- The API must include functional examples and not requre someone to be an expert on the product to use.
- Do not use any product with configurations that are not machine parseable and machine writeable.
- All data stored in the product must be machine readable and writeable by applications other than the product itself.
- Writing hacks around the deficiencies in a product should be less work than writing the product’s functionality.
- Keep the disparity in your architecture to an absolute minimum.
- Use Set Theory to accomplish this.
- Do not improve manual processes if you can automate them instead.
- Do not buy software that requires bare-metal.
- Manual data transfers and datastores maintained manually are to be avoided.
I recently offered to help out with the hosting of a WordPress site. It’s currently hosted somewhere with no shell access – just ftp – and there are a lot of images to transfer.
I quickly figured out I could use wget to mirror the site, using something like:
wget -m ftp://username:email@example.com
However, this broke in this case because the username for the site contained an @ character (the username was
Turns out the solution was to encode the special chars using HTML notation. This is the command that did the trick:
wget -m ftp://user%40example.com:firstname.lastname@example.org
This is one of those “dead easy so why so hard” issues.
I use chrome on Fedora 18 on my home desktop. I have put up with a non-working java plugin for some time (to be honest, I’ve not been to bothered given java’s history of security issues).
Here’s how to enable the java plugin under chrome on Fedora 18 using icedtea (openjdk).
sudo yum install icedtea-web
sudo mkdir -p /usr/lib64/firefox/plugins
sudo ln -s /usr/lib64/IcedTeaPlugin.so /usr/lib64/firefox/plugins/libjavaplugin.so
Now restart chrome and go here to test the java plugin now works.
I wanted to create a full-disk partition, with optimal alignment, on a 4TB disk under CentOS 6.4 and use it as an LVM PV.
fdisk doesn’t work on disks larger than 2TB so I used parted:
parted -a optimal /dev/sda
Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to continue?
(parted) mkpart primary ext2 0% 100%
(parted) set 1 lvm on
Some time ago, I wrote up how I created RPMs for ruby gems to simplify installation on EL-flavoured distributions. In the comments for that article, Jordan Sissel pointed me at his fpm tool which I said I’d check out if I ever needed to build any more rubygem RPMs.
Well, that time has come. I wanted to deploy a later version of capistrano across a client’s infrastructure and my previous approach didn’t work so I grabbed fpm and did this:
gem install --no-ri --no-rdoc --install-dir . capistrano
find ./cache -name '*.gem' | xargs -rn1 fpm -s gem -t rpm
rubygem-capistrano-2.15.4-1.noarch.rpm rubygem-net-scp-1.1.0-1.noarch.rpm rubygem-net-ssh-2.6.7-1.noarch.rpm
rubygem-highline-1.6.19-1.noarch.rpm rubygem-net-sftp-2.1.2-1.noarch.rpm rubygem-net-ssh-gateway-1.2.0-1.noarch.rpm
Nice and easy. Kudos whack!
My Note 2 recently started apparently locking up/freezing and apparently required powering off to fix it.
Thanks to this post, I discovered that this seems to be a "known" problem with the eMMC chip which is susceptible to "Sudden Death Syndrome"
There is an app to determine if your phone has the chip that is affected, and another app to write data to every area of the chip to "fix" the issue.
My phone now appears to be back to normal.
We have app servers with smallish local file systems and application data mounted over NFS.
Sometimes I want to find all files matching a particular set of criteria but don't want to traverse the NFS mounts.
Here's how to do it:
find / -group sophosav -print -o -fstype nfs -prune
Ordering is important, as is the explict inclusion of -print. If you omit this, it will print the name(s) of the NFS mounts as well.
Change start location (/) and criteria (-group sophosav) to suit your own purposes.