From: <Ral...@it...> - 2009-04-29 07:57:40
|
Hi Nicolai, thanks for your help! > Try running the node in debug/foreground mode? > ... I'm not sure what you'll find out though, > since I've not run the node in debug mode myself. these are this node's current settings: [root@nagsaz:~] # grep -e ^log_level -e ^background -e sets /etc/munin/munin-node.conf log_level 4 background 1 setseid 1 setsid yes According to the POD of Net::Server I think that I already have the munin-node running in highest verbosity. Should I change "background" and "setsid" to 0|no ? Btw, what's "sets*e*id" good for? (I think to remember that Gabriele already once asked this when she was doing research for her Munin Book) I haven't found any reference to it in Net::Server's POD. And it doesn't seem to appear anywhere in munin-node's source either. [root@nagsaz:~] # grep -c setseid /usr/sbin/munin-node 0 So was it just a typo by the provider of the sample munin-node.conf file in the tarball? quote from POD Net::Server: log_level Ranges from 0 to 4 in level. Specifies what level of error will be logged. "O" means logging is off. "4" means very verbose. ... background Specifies whether or not the server should fork after the bind method to release itself from the command line. Defaults to undef. Process will also background if "setsid" is set. setsid Specifies whether or not the server should fork after the bind method to release itself from the command line and then run the "POSIX::setsid()" command to truly daemonize. Defaults to undef. If a "log_file" is given or if "setsid" is set, STDIN and STDOUT will automatically be opened to /dev/null and STDERR will be opened to STDOUT. This will prevent any output from ending up at the ter- minal. > -----Original Message----- > From: Nicolai Langfeldt [mailto:ja...@re...] > Sent: Tuesday, April 28, 2009 3:07 PM > To: Grothe, Ralph > Cc: mun...@li... > Subject: Re: [munin-users] Why doesn't "list node" show my plug-in? > > > Ral...@it... wrote: > > I have written an snmp plug-in to glean temperature data > from our AKPC sensors. > > > > For now I manually set the symlink from it to /etc/munin/plugins > > (later if it works I will provide the snmpauto and snmpconf > magic headers) > > > # ls -l /etc/munin/plugins/snmp_sensor_r01_temp > > lrwxrwxrwx 1 root root 48 Apr 28 10:43 > /etc/munin/plugins/snmp_sensor_r01_temp -> > /usr/share/munin/plugins/snmp__sensors_akcp_temp > > > > Then I restarted my munin-node. > > Restarting munin-node is very important. > > > # echo nodes|nc localhost 4949 > > # munin node at nagsaz > > nagsaz > > sensor_r01 > > . > > Very good. > > > But the list command doesn't actually list this plug-in at > all why I suspect that the munin master > > (which happens to be this host) isn't creating a graph. > > > > [root@nagsaz:~] > > # echo list\ sensor_r01|nc localhost 4949 > > # munin node at nagsaz > > Very mysterious. > > > [munin@nagsaz:~] > > $ /usr/share/munin/munin-update --host sensor_r01 --debug > --stdout snmp_sensor_r01_temp|grep -v Skip|grep sensor > > Apr 28 14:10:47 - [5152] Processing node: sensor_r01 > > Apr 28 14:10:47 - [5152] Processed node: sensor_r01 (0.01 sec) > > Apr 28 14:10:47 - [5155] Configuring node: sensor_r01 > > Apr 28 14:10:47 - [5155] Configured node: sensor_r01 (0.00 sec) > > Consistent: no plugins seen I expect. Still very mysterious. > > > # grep -A3 sensor_r01 /etc/munin/munin.conf > > [DC;sensor_r01] > > address 127.0.0.1 > > use_node_name no > > As long as the "list sensor_r01" command does not list the plugin the > configuration you have in munin.conf is irelevant. Try > running the node > in debug/foreground mode? ... I'm not sure what you'll find > out though, > since I've not run the node in debug mode myself. > > What you should find is that when munin-node starts up it runs all > plugins with "config" argument to detect "host_name" fields > and make the > node list. The plugin name should then be resident in a node > name array > in munin-node. > > Nicolai > > -------------------------------------------------------------- > ---------------- > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use > code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > munin-users mailing list > mun...@li... > https://lists.sourceforge.net/lists/listinfo/munin-users > |