I'm running 2.3.1b1 on Solaris 8, so I guess I'll hold off upgrading.. Once you do get it going you'll discover that, in fact, no metrics are being reported because gmond isn't collecting any for Solaris yet. It turns out (see ./gmond/machines/solaris.c) that the metric-specific functions are just "stubs" returning zero, as the metric-specific code hasn't been written yet. It's structured pretty well so it wouldn't take too much to get it filled it.
I had started working on this, but as I'm under pressure to start collecting data quickly, I've opt'ed for a more familiar route. I run the 'orcallator' piece of Orca (www.orcaware.com/orca) on my Solaris boxes, which uses the SE Toolkit (www.setoolkit.com) to collect a nauseating list of metrics. In the middle, I run the orca/RRD piece of Orca and the ganglia RRD client (for my Linux farms) on a Linux box. My plan is to eventually write a gmetric wrapper for 'orcallator' and ditch the 'orca' piece, although there are some differences in Orca/ganglia RRD archive definitions that need to be worked out first. I don't think there are any very many Solaris folks on the ganglia list, if any, so feel free to shoot me a question anytime. On Tue, 28 May 2002, Steven Wagner wrote: > So after trawling the Sourceforge archives, I found that the monitoring > core breaks between version 2.3.1b1 and 2.3.1b3 - 2.3.1b1 compiled and > runs on my Netra t1 test box. > > I'd still like to know if anyone's using a later version than this with > Sun boxes running Solaris (preferably Solaris 8) ... but at least I've > got *something* working now ... > > >
