Unix and music cross overs always tickle my funny bone, probably because I’ve spent a good part of my professional career as a unix sysadmin or programmer for companies in the music and entertainment industry. Today, while looking for some info on UWin, I came across this on David Korn of Korn Shell fame’s web page – Korn meets KoRN . David, if you read this, will you please leave me your KoRn signed copy of your book?!
Archive for March, 2008
every time someone mentions running windows at home, they always follow up by mentioning what piece of software they need that doesn’t have a *nix version and doesn’t run acceptably in WINE or another emulator.
Ironically, in my new job I work on the only Windows servers (actually running Windows XP Home but running part of a Ruby On Rails app that needs to run windows only software) at a *nix shop. I get to do lots of *nix work too, but given how much I like *nix, it’s ironic. It is SO nice working in a *nix shop again!
Interesting problem today, had a Linux box that was providing slow NFS, intermittent SAMBA failures (of said NFS mounts), and the following KEY error messages:
Mar 12 10:59:05 somehost kernel: [X] portmap: server localhost not responding, timed out
Mar 12 10:59:05 somehost kernel: [X] lockd: cannot monitor XXX.XXX.XXX.XXX
Mar 12 10:59:05 somehost kernel: [X] lockd: failed to monitor XXX.XXX.XXX.XXX
This kind of looked like portmap or one of it’s RPC services weren’t running. On inspection, rpc.statd had failed and when restarting, it would time out because it couldn’t contact the portmapper. I decided to restart the system, because that is usually quicker than restarting portmapper and all RPC services (as required with a portmap restart) by hand and in this case the system users would be equally out of service from either one. After restarting, the NFS mounts didn’t mount and when we mounted them by hand we got the following KEY error messages.
Mar 12 14:46:42 somehost kernel: [X] portmap: server localhost not responding, timed out
Mar 12 14:46:42 somehost kernel: [X] RPC: failed to contact portmap (errno -5).
Mar 12 14:46:42 somehost kernel: [X] lockd_up: makesock failed, error=-5
Turns out that there was no route to localhost because ifconfig thought the loopback device was up, but route didn’t. Taking down the loopback device, bringing it back up and then adding the route to localhost manually (it’s
route add localhost dev lo, BTW) got us back to fully functional. I’m still investigating the root cause.