Sponsored Content
Full Discussion: portmapper service
Operating Systems Linux SuSE portmapper service Post 302597261 by bitlord on Thursday 9th of February 2012 08:07:06 PM
Old 02-09-2012
I had to include shutting off nfs, because when I just tried to turn off rpcbind without turning nfs 1st, it would give me a warring.
When I then checked to see if rpcbind was still running after turning it off i would see it still running. So I turn off nfs 1st then turned off rpcbind and it stuck.

Thanks for your imput.
 

4 More Discussions You Might Find Interesting

1. 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

2. Linux

problem with pmap_set (portmapper)

Hi guys, i am putting this problem again please help me out.. The RPC problem is appearing on the screen while starting the portmap service,take a look of the real.. #/etc/init.d/portmap restart Stopping portmap: Starting portmap: Cannot register service: RPC: Timed out not registered:... (15 Replies)
Discussion started by: daya.pandit
15 Replies

3. 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

4. UNIX for Beginners Questions & Answers

Run one service after another service has finished - systemd

Hi all I would like to know how to run task2.service after task1.service has finished. task1.service has a timer (task1.timer), that makes it run every 5 minutes OnCalendar=*:0/5task2.service is basically a script, that has to work on the files created after task1 has finished. This is what I... (2 Replies)
Discussion started by: guilliber
2 Replies
RPCBIND(8)						    BSD System Manager's Manual 						RPCBIND(8)

NAME
rpcbind -- universal addresses to RPC program number mapper SYNOPSIS
rpcbind [-6adiLls] [-h bindip] DESCRIPTION
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve. When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the address where RPC requests should be sent. The rpcbind utility should be started before any other RPC service. Normally, standard RPC servers are started by port monitors, so rpcbind must be started before port monitors are invoked. When rpcbind is started, it checks that certain name-to-address translation-calls function correctly. If they fail, the network configura- tion databases may be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates. The rpcbind utility can only be started by the super-user. OPTIONS
-6 Bind to AF_INET6 (IPv6) addresses only. -a When debugging (-d), do an abort on errors. -d Run in debug mode. In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will abort on certain errors if -a is also specified. With this option, the name-to-address translation consistency checks are shown in detail. -h bindip Specify specific IP addresses to bind to for TCP and UDP requests. This option may be specified multiple times and is typically nec- essary when running on a multi-homed host. If no -h option is specified, rpcbind will bind to INADDR_ANY, which could lead to prob- lems on a multi-homed host due to rpcbind returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP addresses with -h, rpcbind will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list. -i ``Insecure'' mode. Allow calls to SET and UNSET from any host. Normally rpcbind accepts these requests only from the loopback interface for security reasons. This change is necessary for programs that were compiled with earlier versions of the rpc library and do not make those requests using the loopback interface. -L Allow old-style local connections over the loopback interface. Without this flag, local connections are only allowed over a local socket, /var/run/rpcbind.sock. -l Turn on libwrap connection logging. -s Cause rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing connec- tions, preventing non-privileged clients from using rpcbind to connect to services from a privileged port. -W Enable libwrap (TCP wrappers) support. NOTES
All RPC servers must be restarted if rpcbind is restarted. FILES
/var/run/rpcbind.sock SEE ALSO
rpcbind(3), netconfig(5), rpcinfo(8) BSD
March 6, 2014 BSD
All times are GMT -4. The time now is 03:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy