Sponsored Content
Operating Systems Solaris Timeout: No Response from localhost Post 302818267 by Neo on Friday 7th of June 2013 08:18:06 AM
Old 06-07-2013
Yes, you may have accidentally binded another process (the java process in your lsof output) to port 161. So, when you try to run snmpd, it will fail because it cannot bind to the port.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix, Netscape and Localhost

I have configured local host (127.0.0.1) in the hosts file, and the Apache conf file. Why does Netscape take me to a search page when I attempt to go to Http://localhost ?? (4 Replies)
Discussion started by: scruffeone
4 Replies

2. UNIX for Dummies Questions & Answers

Finding LocalHost IP Address

I am writing a program that need to be run on several machines. I am running UNIX and wanted to know if there is a command similar to ipconfig (in DOS) that would return the IP Address of the machine that I am working on. (Not just the loopback address of 127.0.0.1). (1 Reply)
Discussion started by: hazard0007
1 Replies

3. Linux

apache@localhost.localdomain

Hello, I am ltrying to find the config file to modify a parameter for apache (I guess). Here, when sending mail using php web form I get a copy of all mail sent from that form, but here is a sample of what I get : From : apache@localhost.localdomain To : myemail@host.com Subject : Mail ... (2 Replies)
Discussion started by: qfwfq
2 Replies

4. UNIX for Dummies Questions & Answers

AIX localhost error

I have a AIX box. When i ping localhost, it is pinging to some other IP address. When I remove resolv.conf it is working fine. ? What could be the reason ? I have netsvc.conf file with the below given entry hosts=local,bind Many Thanks !! (1 Reply)
Discussion started by: pramodvr
1 Replies

5. UNIX for Advanced & Expert Users

localhost problem!

hello guys, this morning when I start my pc (gentoo) I get some strange errors about localhost. "Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName" ... Apache the same for my aplications, I have to use the full address of my pc instead of... (1 Reply)
Discussion started by: georgeplus
1 Replies

6. Shell Programming and Scripting

SNMP Timeout: No Response from server

When I tried to connect snmp from one server to another server Timeout: No Response from server is comming Pls suggest (0 Replies)
Discussion started by: madhusmita
0 Replies

7. UNIX for Dummies Questions & Answers

How can I ftp to localhost from terminal ?

How can I ftp to localhost from terminal ? I want to test my localhost user and password.. > ftp localhost Trying ::1... ftp: connect to address ::1: Connection refused Trying fe80::1%lo0... ftp: connect to address fe80::1%lo0: Unknown error: 0 Trying 127.0.0.1... ftp: connect:... (2 Replies)
Discussion started by: aneuryzma
2 Replies

8. UNIX for Advanced & Expert Users

DIG uses localhost

Hi, I have these entries in the /etc/esolv.conf: ------------ domain xxxxxx search yyyyyy nameserver 127.0.0.1 nameserver aaaaaaaaaaaaaaaa nameserver bbbbbbbbbbbbbbbb ------------- When I use 'dig' or 'nslookup' command, like 'dig yahoo.com' it uses the localhost as the server. I... (2 Replies)
Discussion started by: chaandana
2 Replies

9. Debian

Waiting for localhost.

I am getting the message - waiting for localhost. Here are some diagnostic steps I have tried .... root@meow:/home/ethan# cat /var/www/cgi-bin/httpd.conf ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/jkj ServerName 127.0.0.1:80 Listen xx.xx.xx.xx:80 Listen 127.0.0.1:80 ... (1 Reply)
Discussion started by: Meow613
1 Replies

10. Shell Programming and Scripting

Cannot find localhost

I get a "not found" error from this localhost/choice.php ethan@meow:~$ ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.025 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.036 m and this ethan@meow:~$ mysql -u... (4 Replies)
Discussion started by: Meow613
4 Replies
snmpd(1M)						  System Administration Commands						 snmpd(1M)

NAME
snmpd - daemon to respond to SNMP request packets SYNOPSIS
/usr/sfw/sbin/snmpd [options] [listening addresses] DESCRIPTION
The snmpd daemon is an SNMP agent that binds to a port and awaits requests from SNMP management software. Upon receiving a request, it pro- cesses the request(s), collects the requested information, performs any requested operation(s), and, finally, returns information to the requester. OPTIONS
The following options are supported: -a Log the source addresses of incoming requests. -A Append to the log file rather than truncating it. -c file Read file as a configuration file. -C Do not read any configuration files except the one optionally specified by the -c option. Note that this behavior also covers the persistent configuration files. This can result in dynamically-assigned values being reset fol- lowing an agent restart, unless the relevant persistent configuration files are explicitly loaded using the -c option. -d Dump (in hexadecimal) the sent and received SNMP packets. -D[token[,...]] Turn on debugging output for the given token(s). Without any tokens specified, this option defaults to printing all of the tokens (which is equivalent to the keyword ALL). Use ALL for extremely verbose output. Note that you must not put a space between the -D flag and the listed tokens. -f Do not fork() from the calling shell. -g GID Change to the numerical group ID GID after opening listening sockets. -h, --help Display a brief usage message and then exit. -H Display a list of configuration file directives understood by the agent and then exit. -I -initlist This option specifies which modules you do (or do not) want to be initialized when the agent starts up. If the comma-separated initlist is preceded with an hyphen (-), it is the list of modules that you do not want to be started. Otherwise, initlist is the list of mod- ules to be started. To obtain a list of compiled modules, run the agent with the arguments -Dmib_init -H This command assumes you have debugging support compiled in. -l [file] Log all output from the agent (including stdout and stderr) to file. If no filename is given, log to a default file set at compile time, normally /var/log/snmpd.log. -L Do not open a log file. Send all messages to stderr instead. -P file Save the process ID of the daemon in file. -q Print simpler output for easier automated parsing. -r Do not require root access to run the daemon. Specifically, do not exit if files accessible only to root (such as /dev/kmem) cannot be opened. -s Use syslog for logging. See syslogd(1M) -S d[0-7] Specifies the syslog facility to use when logging to syslog. d means LOG_DAEMON and the integers 0 through 7 refer to LOG_LOCAL0 through LOG_LOCAL7. LOG_DAEMON is the default. -u UID Change to the user ID UID (which can be given in numerical or text form) after opening listening sockets. -v --version Display version information for the agent and then exit. -V Symbolically dump SNMP transactions. -x address Listens for AgentX connections on address rather than on the default /var/agentx/master. The address can either be a Unix domain socket path or the address of a network interface. The format is the same as the format of listening addresses described below. Note that it is a possible security risk to expose the master agent listening address through TCP/UDP. See section 9 of RFC 2741 for more details. -X Run as an AgentX subagent rather than as an SNMP master agent. Listening Addresses By default, snmpd listens for incoming SNMP requests only on UDP port 161. However, it is possible to modify this behavior by specifying one or more listening addresses as arguments to the daemon. A listening address takes the form: [<transport-specifier>:]<transport-address> At its simplest, a listening address can consist of only a port number, in which case snmpd listens on that UDP port on all IPv4 inter- faces. Otherwise, the <transport-address> part of the specification is parsed according to the following table: <transport-specifier> <transport-address> format udp hostname[:port] or IPv4-address[:port] tcp hostname[:port] or IPv4-address[:port] unix pathname Currently transports TCP/UDP over IPv4/IPv6 and unix domain sockets. Note that <transport-specifier> strings are case-insensitive so that, for example, tcp and TCP are equivalent. Below are some examples, with accompanying explanations. 127.0.0.1:161 Listen on UDP port 161, but only on the loopback interface. This prevents snmpd from being queried remotely. The :161 is redundant because that is the default SNMP port. TCP:1161 Listen on TCP port 1161 on all IPv4 interfaces. unix:/tmp/local-agent Listen on the Unix domain socket /tmp/local-agent. /tmp/local-agent Identical to the previous specification, because the Unix domain is the default transport if and only if the first character of <trans- port-address> is a slash (/). udp6:10161 Listen on port 10161 on all IPv6 interfaces. Note that not all the transport domains listed above will always be available. For example, hosts with no IPv6 support will not be able to use udp6 transport addresses, and attempts to do so will result in the error "Error opening specified endpoint". FILES
snmpd checks for the existence of and parses the following files: snmp.conf Common configuration for the agent and applications. See snmp.conf(4) for details. snmpd.local.conf Agent-specific configuration. See snmp.conf(4) for details. These files are optional and can be used to configure access control, trap generation, subagent protocols, and other features. In addition to these two configuration files, the agent will read any files with the names snmpd.conf and snmpd.local.conf in a colon- separated path specified in the SNMPCONFPATH environment variable, the default location upon agent startup are /etc/sma/snmp and /usr/local/share/snmp. /etc/sma/snmp/mibs The agent loads all files in this directory as MIBs. It does not, however, load any file that begins with a dot (.) or descend into subdirectories. EXIT STATUS
0 Successful completion. 1 A usage syntax error. A usage message is displayed. Also used for timeout errors. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsmagt | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
snmp.conf(4), attributes(5) NOTES
In addition to basic privileges, to run successfully, the agent requires PRIV_NET_PRIVADDR. See privileges(5). SunOS 5.10 20 Jan 2004 snmpd(1M)
All times are GMT -4. The time now is 11:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy