This is a pocket-size lead on How to ready “not starting portmapper is non running … (warning)” inwards Debian or Kali Linux.
Fixing “not starting portmapper is non running … (warning)”:
In most Kali or Debian installation users come across this alert spell booting their system. There’s 2 ways to ready this, it is upward to the readers which ane they choose.
Solution 1: Disable nfs-common service from startup using chkconfig
If you lot expect into rpcbind script, it says that it replaces portmapper service. In my mind, in that location must survive approximately dependencies somewhere that causes this alert message to appear.
The primary 2 services used past times rpcbind are every bit follows:
- NFS (Network File System or nfs-common)
- NIS (Network Information service)
### BEGIN INIT INFO
# Provides: rpcbind
# Required-Start: $network $local_fs
# Required-Stop: $network $local_fs
# Default-Start: southward 2 three four 5
# Default-Stop: 0 1 6
# Short-Description: RPC portmapper replacement
# Description: rpcbind is a server that converts RPC (Remote
# Procedure Call) plan numbers into DARPA
# protocol port numbers. It must survive running in
# lodge to brand RPC calls. Services that use
# RPC include NFS as well as NIS.
Of these 2 it seems nfs-common causes the most issues, thence nosotros are simply going to disable that.
If you lot don’t usage NFS functionality correct right away as well as thence you lot tin disable NFS at startup.
First of all install chkconfig application.
apt-get install chkconfig -y
Now usage the next ascendency to listing nfs-common service, it’s runlevel as well as dependencies.
chkconfig -l nfs-common --deps
As you lot tin come across from the screenshot below, it’s dependencies are $portmap as well as $time.
Note: Use chkconfig -l servicename –deps to honor out dependencies for whatsoever services. This is specially useful when you lot accept vague sentiment on what you’re after.
If you lot are happy alongside the findings as well as desire to take it from startup, lawsuit the next command
chkconfig --del nfs-common
From the output, your tin come across nfs-common is right away disabled from run-levels.
In instance you’ve constitute that this is causing to a greater extent than problem than genuinely fixing, (i.e. nfs-common beingness used past times approximately other service as well as right away you’re getting errors), you lot tin revert your alter dorsum easily. To revert your changes back, usage the next command:
chkconfig --add nfs-common
Again, from the screenshot below, you lot tin come across nfs-common is dorsum inwards startup alongside precisely the same run levels every bit before.
Then reboot. Next fourth dimension you lot shouldn’t come across that alert anymore.
A like work alongside Pulse Audio If you lot also accept pulseaudio alert during kick time, If you lot accept pulseaudio alert during Kali or Debian Linux during kick upward then follow this lead Fixing PulseAudio configured for per-user sessions … (warning) inwards Kali Linux as well as Debian.
Solution 2: Enabling rpcbind defaults
I was notified that this is non the best solution as well as it enables unnecessary services to charge at startup as well as makes your organisation vulnerable. However, if you’re non every bit good worried virtually that, as well as thence larn ahead … :) By loading rpcbind defaults as well as enabling them, you lot tin ready this easily. Open upward a final as well as type inwards the next 2 commands,
update-rc.d rpcbind defaults
update-rc.d rpcbind enable
That’s it, Next fourth dimension you lot shouldn’t come across that alert anymore.
If you lot also accept pulseaudio alert during kick time, Fixing PulseAudio configured for per-user sessions … (warning) inwards Kali Linux as well as Debian.
Portmap
The portmapper (rpc.portmap or simply portmap, or rpcbind) is an Open Network Computing Remote Procedure Call (ONC RPC) service that runs on network nodes that supply other ONC RPC services.
Version 2 of the port mapper protocol maps ONC RPC plan number/version number pairs to the network port number for that version of that program. When an ONC RPC server is started, it volition rank the port mapper, for each detail plan number/version number couple it supports for a detail carry protocol (TCP or UDP), what port number it is using for that detail plan number/version number couple on that carry protocol. Clients wishing to brand an ONC RPC telephone vociferation upward to a detail version of a detail ONC RPC service must offset contact the port mapper on the server automobile to create upward one's take heed the actual TCP or UDP port to use.
Versions three as well as four of the protocol, called the rpcbind protocol, map a plan number/version number pair, as well as an indicator that specifies a carry protocol, to a transport-layer endpoint address for that plan number/version number couple on that carry protocol.
The port mapper service e'er uses TCP or UDP port 111; a fixed port is required for it, every bit a customer would non survive able to larn the port number for the port mapper service from the port mapper itself.
The port mapper must survive started earlier whatsoever other RPC servers are started.
Example portmap instance
This shows the dissimilar programs as well as their versions, as well as which ports they use. For example, it shows that NFS is running, both version 2 as well as 3, as well as tin survive reached at TCP port 2049 or UDP port 2049, depending on what carry protocol the customer wants to use, as well as that the mountain protocol, both version 1 as well as 2, is running, as well as tin survive reached at UDP port 644 or TCP port 645, depending on what carry protocol the customer wants to use.
$ rpcinfo -p
plan vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100024 1 udp 32770 status
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100024 1 tcp 32769 status
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 nlockmgr
100005 1 udp 644 mountd
100005 1 tcp 645 mountd
100005 2 udp 644 mountd
100005 2 tcp 645 mountd
100005 3 udp 644 mountd
100005 3 tcp 645 mountd
Thanks for reading.
Note: This sure enough fixed my work (I don’t usage NFS), however, I am interested to know if this fixed your work every bit well. Let me know, move out a comment. Thanks.
