--> gemini has joined #net-snmp
--> gio-007 has joined #net-snmp
[2002/10/23 00:24:25] #net-snmp <gio-007> hiya
[2002/10/23 00:24:36] #net-snmp <gio-007> fgmaker --global 'WorkDir: /var/www/mrtg' --global 'Options[_]: bits,growright' --output /root/mrtg.cfg
[2002/10/23 00:24:36] #net-snmp <gio-007> --base: Get Device Info on :
[2002/10/23 00:24:36] #net-snmp <gio-007> --base: Vendor Id:
[2002/10/23 00:24:36] #net-snmp <gio-007> --base: Populating confcache
[2002/10/23 00:24:36] #net-snmp <gio-007> --snpo: Skipping ifName scanning because : does not seem to support it
[2002/10/23 00:24:47] #net-snmp <gio-007> why do i have this err?
[2002/10/23 02:06:21] #net-snmp <jbpn> You might do better to ask this question on an MRTG channel.
[2002/10/23 02:24:35] #net-snmp <gio-007> nah, it was snmp err
[2002/10/23 02:24:39] #net-snmp <gio-007> i did it :)
--> wes has joined #net-snmp
[2002/10/23 07:00:44] #net-snmp <rstory> jbpn and wes : no comments on my agent port hijacking message?
[2002/10/23 07:01:27] #net-snmp <wes> I haven'tread it yet.
[2002/10/23 07:08:16] #net-snmp <wes> I don't know, and i'd check the log to figure out why it was changed in the first place.
[2002/10/23 07:09:21] #net-snmp <rstory> * Allow the same port to be specified multiple times without failing.
[2002/10/23 07:09:21] #net-snmp <rstory> * (useful for a listener)
[2002/10/23 07:10:02] #net-snmp <rstory> it's supposed to be useful when restarting the agent...
[2002/10/23 07:10:33] #net-snmp <rstory> let's you re-open a socket before the os has released it from the last person who had it
[2002/10/23 07:11:02] #net-snmp <rstory> if we let it stand, we need something like a lock file
[2002/10/23 07:17:06] #net-snmp <wes> sigh.
[2002/10/23 07:17:32] #net-snmp <wes> I think this gets around the annoying bug in some OSes (true64) where it takes 60 seconds or so at least before the port is released after a crash.
[2002/10/23 07:17:49] #net-snmp <wes> who committed it?
[2002/10/23 07:17:56] #net-snmp <rstory> jbpn
[2002/10/23 07:18:09] #net-snmp <wes> ACTION pokes jbpn
[2002/10/23 07:19:44] #net-snmp <rstory> oops, actually it was dts
[2002/10/23 07:19:53] #net-snmp <wes> ACTION pokes dts
[2002/10/23 07:19:59] #net-snmp <wes> ACTION hits empty air
[2002/10/23 07:20:36] #net-snmp <rstory> log: set REUSEADDR so that specifying the same port twice doesn't kill the agent (Suggested by Robert Hastings)
[2002/10/23 07:20:50] #net-snmp <wes> Ohhh...
[2002/10/23 07:21:10] #net-snmp <wes> so thats don't do this by accident: "snmpd udp:161,tcp:161,udp:161"
[2002/10/23 07:21:19] #net-snmp <wes> sigh.
[2002/10/23 07:21:59] #net-snmp <wes> I'd: write a new note to -coders, CCing robert and dave and put "Robert Hastings/Dave" in the subject line.
[2002/10/23 07:22:01] #net-snmp <rstory> I think killing the agent is appropriate
[2002/10/23 07:22:13] #net-snmp <wes> I'd think so too.
[2002/10/23 07:52:13] #net-snmp <rstory> hmm... original message "RFH: Allow -p udp:161 -p udp:161@"
[2002/10/23 07:53:06] #net-snmp <rstory> wouldn't -p udp:161 pick up all addresses, making the second -p redundant?
[2002/10/23 07:55:06] #net-snmp <wes> I'd think so.
[2002/10/23 07:55:11] #net-snmp <wes> but what do I know?
[2002/10/23 08:34:37] #net-snmp <hampa> If I have this in my snmpd.conf: rwuser admin auth createUser admin SHA authpassphrase adminadmin
[2002/10/23 08:34:47] #net-snmp <hampa> how should I call it with snmpwalk to get a response?
[2002/10/23 08:35:44] #net-snmp <hampa> the wizard did not specify a community in my snmpd.conf.. maby I should add that
[2002/10/23 08:36:04] #net-snmp <wes> a community is not enough for v3
[2002/10/23 08:36:11] #net-snmp <wes> (in fact it won't be used)
[2002/10/23 08:36:25] #net-snmp <wes> Your createUser line looks a bit incorrect though.
[2002/10/23 08:36:32] #net-snmp <wes> I think you want: createUser admin SHA
[2002/10/23 08:36:32] #net-snmp <wes> authpassphrase adminadmin
[2002/10/23 08:36:35] #net-snmp <wes> opps
[2002/10/23 08:36:54] #net-snmp <wes> createUser admin SHA authpassphrase DES adminadmin
[2002/10/23 08:37:03] #net-snmp <hampa> k.. ill try that
[2002/10/23 08:37:09] #net-snmp <hampa> looked like DES was optional
[2002/10/23 08:37:19] #net-snmp <wes> Then, you should probably go read http://www.net-snmp.org/tutorial-5/commands/snmpv3.html
[2002/10/23 08:37:40] #net-snmp <wes> DES is optional if you want the same auth and priv password. You must put in the keyword to use different passwords.
[2002/10/23 08:38:21] #net-snmp <hampa> k
[2002/10/23 08:42:22] #net-snmp <rstory> wes: are you following the netsnmp_set_request_error thread on coders?
[2002/10/23 08:42:34] #net-snmp <wes> I should be, but no.
[2002/10/23 08:42:41] #net-snmp <wes> I hope to catch up on mail later this week
[2002/10/23 08:42:54] #net-snmp <wes> ok, that's a joke. I hope to catch up on "some" mail.
[2002/10/23 08:43:08] #net-snmp <rstory> LOL
[2002/10/23 08:47:39] #net-snmp <rstory> seems that we're not playing well with others.... (handlers below table.c/table_iterator.c)
[2002/10/23 08:48:04] #net-snmp <wes> ok, I'll read it soon.
--> benr has joined #net-snmp
--> shortbus has joined #net-snmp
[2002/10/23 11:10:33] #net-snmp <shortbus> i've got a problem w/ having net-snmp send traps for disk space use. its sending snmpd start and stop traps, so i know its sending some traps. any suggestions?
[2002/10/23 11:11:27] #net-snmp <wes> normally it doesn't.
[2002/10/23 11:11:34] #net-snmp <wes> Are you using net-snmp 5.0.6 or so?
[2002/10/23 11:11:49] #net-snmp <shortbus> yep
[2002/10/23 11:12:31] #net-snmp <wes> read the snmpd.conf manual page on the "DISMAN-EVENT-MIB"
[2002/10/23 11:12:41] #net-snmp <wes> (which you probably didn't compile in either)
[2002/10/23 11:14:06] #net-snmp <shortbus> so just having 'disk / 33%' in my snmpd.conf isn't enough then
[2002/10/23 11:15:53] #net-snmp <wes> right
[2002/10/23 11:19:01] #net-snmp <shortbus> really? even tho that the sample config has diskspace and load checks in it?
[2002/10/23 11:26:29] #net-snmp <wes> sorry for the delay.
[2002/10/23 11:26:35] #net-snmp <shortbus> np
[2002/10/23 11:26:35] #net-snmp <wes> deleting software
[2002/10/23 11:26:43] #net-snmp <wes> It has checks, but it doesn't actually activate traps.
[2002/10/23 11:27:15] #net-snmp <wes> the checks basically install data into certain mib tables. You're expected to either have a management engine that looks at that data, or have the disman event mib support turned on.
[2002/10/23 11:31:19] #net-snmp <shortbus> ah. that basicly makes sense.
[2002/10/23 11:37:11] #net-snmp <shortbus> would that be ./configure --with-DISMAN-EVENT-MIB right?
[2002/10/23 11:37:39] #net-snmp <wes> uh, not quite. --with-mib-modules="disman/event-mib"
[2002/10/23 11:37:54] #net-snmp <shortbus> ok. its one of those days for me
--> nostaw has joined #net-snmp
[2002/10/23 11:53:07] #net-snmp <shortbus> hmm. even with disman-event it still didn't work
[2002/10/23 11:53:24] #net-snmp <wes> did you read the snmpd.conf manual page?
[2002/10/23 11:53:27] #net-snmp <shortbus> yep
[2002/10/23 11:53:37] #net-snmp <wes> did you put "defaultMonitors yes" in your snmpd.conf file?
[2002/10/23 11:53:58] #net-snmp <wes> it only checks things every 5 minutes or so too, so you need to wait (or is it 10)
[2002/10/23 11:53:58] #net-snmp <shortbus> hmm...may have missed that. let me check
[2002/10/23 11:55:10] #net-snmp <shortbus> would the "defaultMonitors yes" just be in the top, or does it have to be anywhere special?
[2002/10/23 11:56:21] #net-snmp <wes> anywhere
[2002/10/23 11:56:49] #net-snmp <shortbus> ok. its there, i'll see what i get. either way tho, i've got to spilt and finish it tomorrow.
[2002/10/23 11:56:57] #net-snmp <shortbus> thx for the help tho
[2002/10/23 11:59:27] #net-snmp <wes> no prob
--> snmpbot has joined #net-snmp
--> wes has joined #net-snmp
--> rstory has joined #net-snmp
--> wes has joined #net-snmp

Powered by: