helge- there is a simple answer to your problem. you need to compile the monitor core with the (--enable-gexec) option so that gmond announces the host is available for gexec to run on.
%./configure --enable-gexec if you have a host that you DON'T to announce as a gexec host .. add the option no_gexec on to /etc/gmond.conf btw, i know that "no_gexec" on is awkward syntax... if should be "gexec on" but it comes from when gmond had every option on the commandline. one of the options was "--no_gexec". we're going to go through and make things more sane soon. hope this helps. -- matt Today, Helge Hansemann wrote forth saying... > Hello, > > guess I've got a beginners, basical problem, but I don' have a clue what > it is. > > Following process are running on my system, just one in the moment: > > 19082 ? S 0:00 authd -d > 19086 ? S 0:00 gmond > 19087 ? S 0:00 gmond > 19088 ? S 0:00 gmond > 19089 ? S 0:00 gmond > 19090 ? S 0:00 gmond > 19091 ? S 0:00 gmond > 19092 ? S 0:00 gmond > 19093 ? S 0:00 gmond > 19099 pts/7 S 0:00 gexecd > > gexecd is started not via (x)inetd, but from the command line, but I get > the same output if I try it via inetd. > > Here's the problem: > > bash-2.05# gexec -n 0 uptime > > All GEXEC_GMOND_SVRS servers are down > > bash-2.05# gstat -a > CLUSTER INFORMATION > Name: unspecified > Hosts: 1 > Gexec Hosts: 0 > Dead Hosts: 0 > Localtime: Wed Apr 2 14:17:09 2003 > > CLUSTER HOSTS > Hostname LOAD CPU > Gexec > CPUs (Procs/Total) [ 1, 5, 15min] [ User, Nice, System, Idle] > > hostname.domain > 1 ( 1/ 97) [ 0.03, 0.01, 0.00] [ 0.7, 0.0, 0.7, 98.6] > OFF > > Does "servers are down" have something to do with "Gexec OFF" and does > someone have an idea what to do ? > > Thanks for your help, > > Greetings, Helge > >
