From: Dave S. <D.T...@cs...> - 2002-12-16 09:57:43
|
> I decided to try starting > up this snmpd daemon as the second one running on the system and tried by > adding the agentaddress 1161 line to the snmpd.conf...[but] > I still got the following as the last lines of the log file: > > init_master_agent: Invalid local port (Address already in use) > Server Exiting with code 1 What happens if you try specifying the port on the command line? Either snmpd -f -L -p 1161 (v4 agent) or snmpd -f -L 1161 (v5 agent) Dave |
From: Dave S. <D.T...@cs...> - 2002-12-17 10:01:21
|
> I tried starting the v4 agent version with the following command > but with the same results. > snmpd -f -L -D -p 1161 -c /usr/local/ucd-snmp-4.2.6/share/snmp/snmpd.conf > > In reviewing the logs it appears that when it is near the end of the > snmpd.conf file and parsing the various info that it gets to agentaddress > 1161 and it responds with snmp_ports: port spec: 1161,1161 and also > ds_set_string: Setting 1:2 = 1161,1161 Sorry - I'd actually meant for you to try '-p 1161' *instead* of the config entry, rather than in addition to it. I should have been clearer. > Is this because I used the -p 1161 to start and also had that entry > in the snmpd.conf ?? Probably. But it does seem to show that it's at least picking up that setting OK. (albeit twice). So try switching back to how you'd prefer to run things - i.e. drop the command-line option, and just run with 'agentaddress'. Does the debug output list simply "snmp_ports: port spec: 1161", or do you still get a doubled value? And does the 'installing_master_agent' message get displayed twice or not? > It then parses the last line but then goes looking for more to do in > files that don't exist like snmpd.local.conf and ../lib/snmp/snmpd.conf > and ../share/snmp/snmp.conf etc. That's fine - no problem at all. The agent has a list of "likely locations", where it will look for variously named config files. Many (if not most) won't exist, and the agent will skip these quite happily. The main thing to check here, is whether the agent is actually loading a config file twice. Or else whether the 'agentaddress' token appears in two separate config files. That would also be a possible explanation of why you might get "Invalid local port". Dave |
From: Dave S. <D.T...@cs...> - 2002-12-18 09:22:08
|
> After some effort it appears that I finally am able to start the > ucd-snmp snmpd as the second one on the system and have it continue > to run..... [but] most of the core mib tables are missing.... > .... Specifically, I am > looking for prTable, memory, diskTable, systemStats. How have you configured the agent? The process table, and the disk table only monitor the processes/disks that you explicitly tell them to - see the FAQ entry: Why can't I see values in the UCDavis 'extensible' or 'disk' trees? The memory group probably isn't implemented under AIX. This is one of the more architecture-specific things being monitored, and we're reliant on those with access to various systems providing the support for the appropriate architectures. (I don't believe any of the core developers have AIX kit). See the FAQ entry: Why can't I see values in the UCDavis 'memory' or 'vmstat' trees? I'm not sure about the systemStats, but that may well be similar. Did you compile this from source? If so, have a look at the directory 'agent/mibgroup/ucd-snmp'. The presence (or absence) of .o files should tell you which groups have been compiled into the agent. Note that this is nothing to do with finding the MIB files. The agent doesn't really use these definitions - the information it returns is essentially hardcoded. Dave |