« As Insty would say: "Unexpectedly!" | Main | Another bit of Awesome Tech doesn't do what I want »

Sunday, 06 January 2013

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83452f36169e2017d3f919653970c

Listed below are links to weblogs that reference When "UPS" doesn't stand for "Brown Truck of Happiness"...:

Comments

Have you tried running APC UPS? It's linux software for managing these things, whether serial or usb connected. I've had great success with it, if nothing else it gives you insight into the status of the UPS. I run it at home and at work.

Sooooo, did the change to the Apache init.d script do what you wanted - once the BIOS fun and games were resolved?

With switching gear, if it's Cisco it might be the knock-off Chinese stuff. One of the ways people discover is when the switches start having problems as the traffic load rises, but is still well shy of the capacity of the switch. Then you start experiencing intermittent network problems. There are web pages that tell how to crack the case and see if it's real or faux.

In other news, we had some problems with a ProCurve Gigaswitch delaying packets. The delay was just enough for our clustered services to have a server fail when it didn't respond quickly enough. I reviewed the logs then hit the ProCurve boards looking for answers. Upgrading the firmware was the answer and the solution. That resolved the issue and the clustered services were back to their normal selves.

fwiw, when I'm having issues with machines booting wrong, I'll unplug the machine. Not just turn it off, but unplug it then take a bio pause, fire up the espresso machine and have a cup. Then come back, plug it in and try again. Frequently it works. Sometimes it doesn't. I just remember the old OS2 installation instructions from IBM where they recommended unplugging a computer for 10 minutes before installing the new OS.

Another enjoyable read.

marcus

The Apache init script change didn't do what I expected, but that's because I'd forgotten the magic command to process the dependencies: insserv. That having been run, I think it'll work, but I don't plan on another boot until I've gotten the UPS fixed and some weekend time is available, which may not be the coming weekend....

I haven't been actively communicating with the UPS - had been running, I think, NUT, back when I had a BSD server, but haven't gotten around to configuring any such software on the Linux box. I should probably do that.

The new Ethernet switch is Linksys, i.e., downmarket Cisco. The old one is Netgear. I don't recall the identities of the bargain-basement Gig-E cards in the connected machines. (Actually, I think the workstation is using its onboard Ethernet, while the server is using an aftermarket card for LAN, onboard for DSL, and another card for a secondary network, currently not connected.)

Remaining likely suspects for the performance problem are the controllers in the machines, my NFS configuration, and the fact that I'm using NFS at all. It may be time to give one of the newer network filesystems a try.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

My Photo

Disclaimers

  • The Secretary disavows any knowledge of my actions.
  • The Gnomes of Zurich are not responsible for any content on this site.

Infobits

Blog powered by Typepad