Sponsored Content
Operating Systems Linux problem with pmap_set (portmapper) Post 302251947 by otheus on Tuesday 28th of October 2008 12:00:11 PM
Old 10-28-2008
portmap is not working properly. Make sure /etc/rpc is there and has a valid portmapper line. Also check if you have any firewall rules preventing localhost from connecting. All the errors are resulting from this.

The /etc/init.d/portmap script tries to run portmap and then load portmap with its last-known-state. If portmap isn't running, you'll get the RPC/timeout errors.

You don't really need portmap unless you intend to run NFS or NIS on a LAN.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SSH Problem auth problem

Hi, Just recently we seem to be getting the following error message relating to SSH when we run the UNIX script in background mode: warning: You have no controlling tty. Cannot read confirmation.^M warning: Authentication failed.^M Disconnected; key exchange or algorithm negotiation... (1 Reply)
Discussion started by: budrito
1 Replies

2. UNIX for Dummies Questions & Answers

Portmapper not responding

Kindly When I start the server i have this error "portmapper on server 185.125.241.321 is not responding" let me also clarify that this is the old IP of the server and the new one 192.168.0.2 regards (1 Reply)
Discussion started by: sak900354
1 Replies

3. Shell Programming and Scripting

problem with dd command or maybe AFS problem

Hi, folks. Sorry for bothering, but maybe someone could help me please. The problem is the following: there is some script that copies files from local file system to AFS. The copying is performed with dd command. The script copies data into some AFS volumes. The problem appeared with one... (0 Replies)
Discussion started by: Anta
0 Replies

4. Shell Programming and Scripting

ssh script problem problem

Hi Please help me with the following problem with my script. The following block of code is not repeating in the while loop and exiting after searching for first message. input_file ========== host001-01 host001-02 2008-07-23 13:02:04,651 ConnectionFactory - Setting session state... (2 Replies)
Discussion started by: pcjandyala
2 Replies

5. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

6. Red Hat

Mail Problem. Maybe, it is a DNS Problem!

Hi, i've a redhat linux 9 upadated by redhat from 7 version to 9 version. A couple of days ago i was a problem with my mail, in other words i'm not able to get any email nor to send any email. I've a proxy configuration and i tried to set iptables in order to verify the port. The 110,255 and 995... (1 Reply)
Discussion started by: pintalgi
1 Replies

7. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

8. SuSE

portmapper service

Hello, I've been asked to look this up and I'm having issue finding it. We are currently harding our servers and I'm new to SUSE 11. The security people at work want me to disable the portmapper service. How do you disable the portmapper service? Thanks ... (3 Replies)
Discussion started by: bitlord
3 Replies

9. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

10. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME
rpc.statd - NSM status monitor SYNOPSIS
rpc.statd [-FNL] [-d] [-?] [-n name ] [-o port ] [-p port ] [-H prog ] [-V] DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnamed, since it doesn't actu- ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots. Operation For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/sm. When starting, it normally runs sm- notify to iterate through these files and notify the peer rpc.statd on those machines. OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground. This option is mainly for debugging purposes. -d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter. -n, --name name specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname. Specifying a local hostname may be useful for machines with more than one interfaces. -o, --outgoing-port port specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -p, --port port specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ- ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -P, --state-directory-path directory specify a directory in which to place statd state information. If this option is not specified the default of /var/lib/nfs is used. -N Causes statd to run in the notify-only mode. When started in this mode, the statd program will check its state directory, send noti- fications to any monitored nodes, and exit once the notifications have been sent. This mode is used to enable Highly Available NFS implementations (i.e. HA-NFS). This mode is deprecated - sm-notify should be used directly instead. -L, --no-notify Inhibits the running of sm-notify. If sm-notify is run by some other script at boot time, there is no need for statd to start sm- notify itself. This can be appropriate if starting of statd needs to be delayed until it is actually need. In such cases sm-notify should still be run at boot time. -H, --ha-callout prog Specify a high availability callout program, which will receive callouts for all client monitor and unmonitor requests. This allows rpc.statd to be used in a High Availability NFS (HA-NFS) environment. The program will be run with 3 arguments: The first is either add-client or del-client depending on the reason for the callout. The second will be the name of the client. The third will be the name of the server as known to the client. -? Causes rpc.statd to print out command-line help and exit. -V Causes rpc.statd to print out version information and exit. TCP_WRAPPERS SUPPORT This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow: statd: .bar.com You have to use the daemon name statd for the daemon name (even if the binary has a different name). For further information please have a look at the tcpd(8) and hosts_access(5) manual pages. SIGNALS
SIGUSR1 causes rpc.statd to re-read the notify list from disk and send notifications to clients. This can be used in High Availability NFS (HA-NFS) environments to notify clients to reacquire file locks upon takeover of an NFS export from another server. FILES
/var/lib/nfs/state /var/lib/nfs/sm/* /var/lib/nfs/sm.bak/* SEE ALSO
rpc.nfsd(8), portmap(8) AUTHORS
Jeff Uphoff <juphoff@users.sourceforge.net> Olaf Kirch <okir@monad.swb.de> H.J. Lu <hjl@gnu.org> Lon Hohberger <hohberger@missioncriticallinux.com> Paul Clements <paul.clements@steeleye.com> 31 Aug 2004 rpc.statd(8)
All times are GMT -4. The time now is 12:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy