Tuesday, September 05, 2006

Solview Updated

I've updated my solview utility to version 0.3.

What is solview, I hear you ask? It's a little java gui to show useful information about a Solaris system. It shows installed software packages (and installation software clusters); services and their status; and the output from various informational commands.

This new version enhances the package and cluster information. It's split up into several tabbed panels, and now shows cluster membership, the installed status of clusters, and can calculate full dependencies.

What happened to version 0.2? Well, that version included a rather spectacular failure to enhance the software display by parsing the contents file. I expect it is possible to get java to extract useful information from this file without running out of memory, but I didn't succeed in doing so. So that attempt got scrapped and I moved on to version 0.3.

Sunday, August 20, 2006

How hard can it be?

Yesterday I tried to write a CD on the family PC. I've been taking digital photos almost exclusively for the past couple of years, and we went through the accumulation and decided to get a few printed off properly. Simple - just burn them to a CD and take it to the nearest supermarket.

So the family PC has a writable CD drive, and a popular user-friendly operating system that's supposed to make this a breeze. So it should be a doddle, right? Wrong! I go to my photos and click where it says "Copy all items to CD", and failed completely to produce a CD with any pictures on. Several coasters, for sure, but no viable CDs. (My understanding of the way this is supposed to work is that it just copies the files to a holding cell, and when you open a writable CD it's supposed to ask you if you want to burn the CD. Nope, just trashed the CD every time.)

The PC has a number of utilities, that either came preinstalled, or as part of some other package, that allow you to write to a CD. None of those did the job either (I know the thing works, because I've written backups or VideoCDs, but I wanted something terribly simple. No dice.)

Unwilling to waste any more time, I simply copied the files to a real computer running Solaris. A couple of simple commands later and I had burnt a CD, first time, no problem.

Oh, and the pictures came out great.

Friday, August 18, 2006

Back in Circulation

I haven't disappeared. I haven't given up. I'm still alive.

The last month has been pretty hectic for me. It being summer and the kids having time off school, we took some holiday.

Also, as I mentioned earlier, I've changed jobs. I'm now working for Proquest Information and Learning, looking after their Sun Solaris servers. Half the first month was spent on holiday (arranged long before, and Proquest were happy with that - they were keen for me to make a start as soon as possible rather than wait until after my vacation). So far, I've been enjoying myself enormously. It's a big challenge and an environment rather different to what I've been used to, but I'm starting to get my teeth into it. The lifestyle is much better, and I've been cycling to work quite a lot (although, if you read the holiday story, it's not as if I have much choice at the moment).

Sunday, July 30, 2006

Self Preservation

It's been unpleasantly warm here in the UK over the last month. I'm sure other places have it hotter, but we're not used to it and not geared up for it.

I have some old work colleagues who I set up some systems for, and I got an urgent phone call just before going on holiday: "the air conditioning failed yesterday and the power in the data centre was unceremoniously yanked - could you check the systems out?".

It turns out the servers - Sun machines - were fine. With a fine sense of self preservation they had shut themselves down gracefully due to the heat:

Jul 19 18:00:14 foobar rmclomv: [ID 690426 kern.crit]
SC initiating soft host system shutdown due to fault at MB.T_ENC.
Jul 19 18:00:15 foobar rmclomv: [ID 222544 kern.error]
SC Request to Power Off Host.
Jul 19 18:00:16 foobar rmclomv: [ID 428258 kern.crit]
TEMP_SENSOR @ MB.T_ENC has exceeded high soft shutdown threshold.

So far, all appears to be well, and I haven't seen any further errors.

Thursday, July 13, 2006

Enhancing the JDS desktop look

While the JDS desktop that currently comes with Solaris is essentially functional, I've always found it rather bland. In one sense it's a good thing - it has no major irritations (most window managers or desktop environments have something that drives me up the wall).

Still, I would like to get a bit more character out of the desktop. Unfortunately, the available themes are pretty thin on the ground. Unlike the huge array of themes that you can get for Window Maker, you're really very restricted.

I actually quite liked the new theme that the latest JDS builds come with, but it doesn't seem to be separately available.

I've found a couple of themes that I like. I've used eXPerience for most of the last year. I've got my Windows XP box set to the olive green theme, and find that color combination works quite well for me. And I've just been playing with Clear Blue, which works pretty well. It's a bit pale on my current monitor, and I might have to tone down some of the other applications I use to blend in a little better, but it's looking good.

There's still a lot of room for more gorgeous looking desktop themes, though.

Wednesday, July 05, 2006

S10U2 companion problems

Recently, the update 2 of Solaris 10 was released.

Along with this comes the companion CD - a collection of unsupported freeware.

However, the S10U2 companion DVD has a number of problems. Apart from the old one of being distributed as a single ISO image with both sparc and x86 binaries, so that you have to download both architectures even if you only wanta one, some new problems have appeared.
  • There isn't an installer. THere are over a hundred packages here and installing them individually by hand can get a bit tedious.
  • Worse, some packages depend on packages that are no longer shipped. I had to install SFWgcc2l, SFWgcc34l, SFWgfile, SFWgtext, SFWshutl, and probably SFWgm4 off the S10U1 companion to get the dependencies and missing components back.
  • Some useful utilities (some of them listed above, but also things like bluefish) have just disappeared.
  • Coreutils has been added, without the g prefixes.

For all that pain, is there any gain? I can't see any. I can't see any new packages that add any value, we've lost functionality, the installed packages don't work, and it's not even as if we have anything useful like a more up to date version of KDE.

I recommend going back to the S10U1 companion.

Thursday, June 22, 2006

#opensolaris

One part of the OpenSolaris first anniversary (or birthday) last week was an IRC chat party.

I'm not entirely sure I'm fluent with IRC yet. I used to chat interactively 15-20 years ago, but haven't done much since. One problem is that I get interrupted or distracted quite a lot. This isn't much of a problem for email discussions, but it's rather easy to lose the thread of a chat conversation.

First couple of times I used the builtin mozilla client. Just tried the ChatZilla extension for Firefox, which is basically the mozilla client, and it works fine.

Wednesday, June 21, 2006

Solaris Install

Mark Mayo lists his top 10 Solaris Installation Annoyances.

I'm not going to try and pretend that the Solaris installer isn't anything other than bad, but consider the following:

I've done thousands of Solaris installs over the last decade or so. I can probably count the number of times I've used the interactive installer on the fingers of one hand. No, I didn't like it much either.

The fact that most admins with a clue use jumpstart means that the interactive installer has received precious little attention. Even if the interactive installer was the best thing since sliced bread, I would never use it at work. That's not to say that the interactive installer can't be improved - it can, and must be.

I've not used a modern Linux installer (say, Ubuntu) but have used RedHat, Mandrake, Suse, Fedora. And I wouldn't necessarily say they're actually much better. Sure, they might look prettier, and feel slicker, but were often fragile (installer just bombs out) and unreliable (system all messed up afterwards). The Solaris installer might be butt-ugly and dog-slow, but produced working systems if you were prepared to suffer to the end. And if people are using interactive installers professionally, they need to get with the program and adopt some automatic provisioning scheme.

1. As for why it's slow, some work has been done on this. The biggest problem is that the distribution is compressed with bzip2. It goes way quicker if you swap out bzip2 for gzip.

2,3,4. Never happen if you use jumpstart.

5. I would argue against any attempt to change the default shell to bash. (Now, if they suggested tcsh, that might be received more favourably.)

6. Err, who on earth logs in as root?

7,8. We ought to chuck vi and vim and replace 'em with emacs...

9. Urrgh. Sendmail.....

10. Secure by default has finally made it into Nevada. But automation under jumpstart would normally knock out services you don't need.

Opera 9, Solaris x86

Not only is there a new version of Opera, but it's available for Solaris x86 as well!

Hooray!

An unfair comparison:

PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
107 ptribble 4 49 0 1024M 971M sleep 219:15 1.75% firefox-bin
25551 ptribble 1 49 0 64M 52M sleep 0:07 0.02% opera

I still prefer firefox, but that might change. Don't know why, it just seems to work for me better than other browsers. One thing that opera does have that's useful is the ability to duplicate a tab. And I am getting rather fed up of having to restart firefox every day or two to keep memory utilization within bounds on my workstation (or cpu utilization down on the XP box at home).

Thursday, June 15, 2006

Moving On

Not as newsworthy as Scoble, but I'm changing jobs soon.

I've been in my current job for about 9 months, and it's been tough. I've never really settled properly into the organization, and there have been a lot of frustrations that I haven't been able to identify properly or address. Combine that with spending between 2 and 3 hours a day commuting, and it wasn't really a situation I wanted to continue in.

Last week got fairly frantic. I saw an advert for an attractive position with a company only a few minutes from home at the beginning of the week. Sent off my CV, got called by the agency, went for interview, went back for a second interview the next day. I liked what I saw, and they obviously liked me enough to offer me the post, so I start there in about a month's time.

I'm looking forward to it. And not just the job - 2 hours of my life back every weekday is going to make a huge difference.

Wednesday, June 14, 2006

Striding Out

A year ago today, OpenSolaris was launched and started taking its first baby steps.

Over the last year, a lot has happened. More code has been released. We've had lots of lively discussions. Many projects have started. OpenSolaris distributions have been created. There's been serious progress on building a Source Code Management system that fits the needs of Sun and the community. Members of the outside community have been filing bugs and contributing fixes.

Progress in some areas has been slow, but that's fine. We've been learning how to walk before we can run, and we love Solaris too much to risk running too fast and falling over and breaking anything. But the project is gaining strength and starting to stride out more confidently.

For my own part, I've been involved in the community since the early days of the pilot. Job issues meant I had to back off on the code contribution front for a while, but I've recently managed to get some fixes put back, with more on the way. This work seems to have been picked up by ZDnet Australia and even a Sun feature.

So we've had a good year, and I feel privileged to have been allowed to be a part of it.

, here's to many more successful years!

How fast is my SCSI?

Discovered a quick way of working out at what speed SCSI devices are connected to a Sun server at.

This only works for some SCSI cards - it seems to be a bit hit and miss. I've generally had some success on my SPARC workgroup servers, but other machines give zilch.

And the actual data transfer rate is something else again. But at least you can check that things are being set up at the rated speeds.

The command is:

prtpicl -v | grep sync-speed

and you then have to work out what the devices are.

Some examples. Here's a V240 with an attached 3310 array:

:target0-sync-speed 160000
:target1-sync-speed 160000
:target2-sync-speed 160000
:target3-sync-speed 160000
:target0-sync-speed 320000
which shows the intrenal drives at Ultra160, and the external array at Ultra320.

Here's a V440 with a pair of 3120 arrays:

:target5-sync-speed 5000
:target8-sync-speed 320000
:target9-sync-speed 320000
:targeta-sync-speed 320000
:targetb-sync-speed 320000
:target5-sync-speed 5000
:target8-sync-speed 320000
:target9-sync-speed 320000
:targeta-sync-speed 320000
:targetb-sync-speed 320000
:target0-sync-speed 320000
:target1-sync-speed 320000
:target2-sync-speed 320000
:target3-sync-speed 320000
all the disks are at Ultra320, and you see an SES target on each array that's come in at 5M.

Here's an old E450:

:target0-sync-speed 40000
:target1-sync-speed 40000
:target2-sync-speed 40000
:target3-sync-speed 40000
:target6-sync-speed 20000
:target1-sync-speed 10000
which has the disks at 40M, the DVD at 20M, and the tape at 10M.

Friday, June 09, 2006

Ultra 25

So where did the Ultra 25 come from? I don't recall any product announcement or big splash.

Still, that's not much of a surprise really, as the machine doesn't look too impressive. Only a 1.34GHz chip, which is slower than the SunBlade 1500 it presumably replaces.

I also note that the operating systems it supports include

Solaris 9 (Available September 2006)

Does this mean that there's going to be a new hardware release of Solaris 9 in September?

Wednesday, June 07, 2006

That's Reliable?

I was just looking at a Yankee Group report on server reliability, as reported by Yahoo!.

Now it's nice to hear that they think Solaris is winning on reliability. I knew that :-)

However, going beyond the headline they find:
  • 3-5 failures per server per year
  • 10-19.5 hours of downtime per server per year
Ouch!

Of course, that's server uptime, not service uptime. With a decent architecture you would have some backup so that the service would be available even if a server failed. And servers do fail, no matter how good they are, or need maintenance work.

But whatever, I don't regard 99.8% availabilty as anything like good. In fact, it's terrible.

My own experience is that Solaris is pretty damn reliable. Much better than the figures quoted, at any rate. And Windows servers themselves don't seem to be too bad (although they do seem vulnerable to major corruption events which, while rare, involve significant outage), although PC networks overall seem very fragile. Linux I've found to be less robust, with older versions simply wedging and hanging regularly (something that I believe has been dramatically improved), but I suspect a lot of Linux problems are due to people believing the myth that it's free and will run on any old piece of junk hardware, and so they use junk hadware and don't manage it properly - with predictable consequences.

The other aspect of system reliability is applications and, quite frankly, application reliability is often simply not up to scratch.

Friday, May 26, 2006

Lapping it up

My intention to learn some new tricks has been going quite well.

I've been working with PHP on a little project of mine. It's a system monitoring application - data about the health of systems is inserted into a database and reports displayed on a web page.

It was written using JSP, and that works extremely well up to a point. But it doesn't really need any specific technology - there's nothing in JSP that is especially suited to the task, which is fairly simple. Rewriting it in PHP therefore looked fairly easy, and having a real project is a good way to learn something new.

And it worked very well. PHP is very easy to develop in, and I was able to implement some new features as well.

So how would I compare PHP and JSP? Each has advantages and disadvantages:

PHP is quicker to get going in, so putting together simple prototypes and building on them is slightly easier.

I found it easier to make silly mistakes in PHP - the language is a bit more forgiving, so that some typos that would have generated a failure in JSP get through and you end up with something that doesn't quite work right. You need to impose a bit more discipline with PHP.

PHP doesn't need a huge java process to run a servlet engine. This has always bothered me - the overhead of a servlet container, just to dynamically create a few web pages, is considerable.

The really big advantage of PHP, though, is that it's very easy to create images on the fly. The GD extension is pretty well standard, and works (although not capable of horizontal dashed line - doh!). I've tried various ways of creating graphs using JSP and, while it's possible, it's neither easy nor pleasant. There's clearly for an opening here for a dead-easy JSP image generator to be created (or, if it exists, to come out from wherever it's been hiding).

The downside to PHP was the length of time it took to put the stack together. Tomcat is a zip file you unzip, and you're basically done. PHP makes the common mistake of using autotools and is a right pain in the neck to configure and build correctly as a result. (Note that its not PHP's fault; it's autoconf.)

So that project is almost done, and while I wouldn't claim to be fluent in PHP, at least I'm capable of asking directions in the language. Now on to ruby on rails when I get some more free time...

OpenSolaris contributions

As Jim has just noted, some of my contributions to OpenSolaris recently got putback.

This is great. It's great that Sun - as an organization - gives external contributors like myself the opportunity to put changes into Solaris. It's great that individuals within Sun (thanks Dave!) take on the time and effort required to integrate the changes into the codebase.

It's taken a while to get going. I was starting to work on fixes during the pilot stage of the OpenSolaris project, over a year ago. The fixes just putback aren't those (although I am looking at getting that work integrated too). This set of fixes to the install consolidation was actually due to something I was trying to do at work, and pkgchk wasn't cooperating. In the old days, I could have spent days fighting with support trying to persuade them that (a) it was a problem, and (b) that it might be worth fixing. Instead of which I can now get in there and fix the thing properly.

I have some other fixes planned for the Solaris package tools as well, with several possible performance improvements having been identified.

Actually getting the fixes into OpenSolaris isn't hard (the Sun sponsor does most of the legwork). It would do no harm to start off simple, just to run through the process (I didn't, of course, and it was the first external contribution to the install consolidation as well, so it was a learning experience for us).

Monday, May 15, 2006

Old dog, new tricks

I've decided it's time to learn a few new tricks.

The first trick I'm trying to learn is PHP. I'm used to java and JSP pages (although these modern new-fangled frameworks do nothing for me), but there seem to lots of web-based applications out there using PHP, and if I'm going to install and maintain some of them, I ought to understand how the language works.

The second trick is Ruby on Rails. The promise of simplicity is very appealing to me. That agrees with my systems philosophy - KISS.

(More generally, the more completely you can understand a system, the better the chance you have of making it work properly.)

After a few trails and tribulations, I've now got both software stacks up and running. Off to try a few examples...

Flimsy fans?

Anyone having trouble with the main fans ("rear fan 1") in a W2100z?

We've got 3 W2100z boxes at work, from two different batches. Even the oldest one is only a year old.

Now all 3 have had the main fan die, needing hardware replacement. The system is dead while waiting for a new fan to show up, which is somewhat annoying.

(No, it's not the old BIOS problem.)

Still, my old SunBlade 2000 had its disk die today, so sparc boxes aren't immune. This means I'm temporarily without a system running a nevada build - I shall have to go root around in the dumpster tomorrow to see if there are any spare FCAL drives left.

dumb

Every so often I have it reinforced just how stupid using autoconf can be.

I maintain my own software stack in /usr/local - applications that don't come with the operating system, or different version of ones that do.

I was just updating gzip. So the ./configure script, when invoked with --help, says:

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.


OK, so I do ./configure, make, make install.

What the heck?!?!?!

It's installed it in /usr, overwriting the system copies!

Looking at the configure output in more detail, it did say:

checking for prefix by checking for gzip... /usr/bin/gzip


I know I can't blame autoconf itself for this one, because the tool has been misused, but using a tool and then violating both its common conventions (default prefix of /usr/local) and its own self-documenting behaviour, is really bad.

And one last thing. It installs itself as zcat, not gzcat. On Solaris, zcat isn't even the same beast.