hi
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
thanks
* T mlist4suntong@yahoo.com [20060717 18:15]:
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
Because you might run userauth via NIS. You didn't notice this before because Debian runs portmapper by default - which grml doesn't.
regards, -mika-
On Mon, 17 Jul 2006 20:23:49 +0200, Michael Prokop wrote:
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused [...]
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
Because you might run userauth via NIS. You didn't notice this before because Debian runs portmapper by default - which grml doesn't.
Ahh, no wonder, thanks for the explanation. Any quick fix?
PS. I didn't touch any userauth or NIS setting after the HD installation.
thanks
PPS. I don't have any package that begins with yp installed.
* T mlist4suntong@yahoo.com [20060717 22:02]:
On Mon, 17 Jul 2006 20:23:49 +0200, Michael Prokop wrote:
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused [...]
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
Because you might run userauth via NIS. You didn't notice this before because Debian runs portmapper by default - which grml doesn't.
Ahh, no wonder, thanks for the explanation. Any quick fix?
Start portmapper or just ignore it. Nothing to care about, it just works and does not break anything.
PS. I didn't touch any userauth or NIS setting after the HD installation.
Yes, that's Debian's useradd.
PPS. I don't have any package that begins with yp installed.
But something like nis/nfs/portmap/passwd. ;)
regards, -mika-
On Mon, 17 Jul 2006 22:09:03 +0200, Michael Prokop wrote:
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused [...]
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
Because you might run userauth via NIS. You didn't notice this before because Debian runs portmapper by default - which grml doesn't.
Ahh, no wonder, thanks for the explanation. Any quick fix?
Start portmapper or just ignore it. Nothing to care about, it just works and does not break anything.
PS. I didn't touch any userauth or NIS setting after the HD installation.
Yes, that's Debian's useradd.
So to conclude, Debian's useradd tried to run userauth via NIS by default, which will make rpc calls/connections.
Portmap is a server that converts RPC program numbers into DARPA protocol port numbers. It must be running in order to make RPC calls.
grml doesn't runs portmapper, and I never need to make RPC calls.
- is it ok to remove the Portmap from my system? - is there any way to disable Debian's useradd from using NIS and making rpc calls/connections?
PPS. I don't have any package that begins with yp installed.
But something like nis/nfs/portmap/passwd. ;)
hmm... not quite
slocate portmap/passwd slocate nfs/portmap
both above return nothing.
slocate portmap returns only the following files:
/etc/default/portmap /etc/init.d/portmap /sbin/portmap /usr/share/doc/portmap
Incoming from T:
- is it ok to remove the Portmap from my system?
If you don't need it, certainly. Disable it, then verify nothing's broken. Since grml doesn't enable it by default, it's likely unnecessary until you enable stuff that needs it (NFS/NIS/yp...). portmap is considered a security risk. Too chatty/informative.
- is there any way to disable Debian's useradd from using NIS and making
rpc calls/connections?
Scrounge around in /etc/init.d for stuff that does that. Turn it off.
/etc/default/portmap
# By default listen on all interfaces OPTIONS="-i 127.0.0.1"
Incoming from T:
On Mon, 17 Jul 2006 20:50:33 -0600, s. keeling wrote:
- is there any way to disable Debian's useradd from using NIS and making
rpc calls/connections?
Scrounge around in /etc/init.d for stuff that does that. Turn it off.
?
(0) heretic /home/keeling_ al /etc/init.d ./ discover* hwclockfirst.sh* mysql* skeleton* ../ dns-clean* ifupdown* networking* smartmontools* README esd_init* ifupdown-clean* nfs-common* ssh* atd* exim4* inetd* ntp-server* stop-bootlogd@ aumix* fam* initrd-tools.sh* nviboot* sudo* bootclean.sh fauxident* keymap.sh* portmap* sysklogd* bootlogd* fetchmail* klogd* ppp* udev* bootmisc.sh* gdm* lpd* pppd-dns* udev-mtab* checkfs.sh* halt* lprng* procps.sh* umountfs* checkroot.sh* hdparm* makedev* rc* umountnfs.sh* console-screen.sh* hdparm_init* module-init-tools* rcS* urandom* cron* hostname.sh* modutils* reboot* xfree86-common* dbus-1* hotplug* mountall.sh* rmnologin* dictd* hotplug-net* mountnfs.sh* sendsigs* dirmngr* hwclock.sh* mountvirtfs* single*
Hmmm ...
mountnfs.sh networking nfs-common portmap umountnfs.sh
egrep 'nfs|rsh|portmap|rpc|nis|...' /etc/init.d/*
JFYI:
* Michael Prokop mika@grml.org [20060717 22:09]:
- T mlist4suntong@yahoo.com [20060717 22:02]:
On Mon, 17 Jul 2006 20:23:49 +0200, Michael Prokop wrote:
whenever I add a user in grml, I get the following error:
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused [...]
I've never see this before, and would like to know why adduser need to do some rpc calls/connections.
Because you might run userauth via NIS. You didn't notice this before because Debian runs portmapper by default - which grml doesn't.
Ahh, no wonder, thanks for the explanation. Any quick fix?
Start portmapper or just ignore it. Nothing to care about, it just works and does not break anything.
Still valid.
PS. I didn't touch any userauth or NIS setting after the HD installation.
Yes, that's Debian's useradd.
Not true, I meant adduser. useradd does not include/execute nis-stuff.
PPS. I don't have any package that begins with yp installed.
But something like nis/nfs/portmap/passwd. ;)
It's nis. If nis is installed, adduser is executing 'rpcinfo -p' which leads to the above mentioned "error"-message.
A bugreport against adduser (on request by Marc 'Zugschlus' Haber, one maintainer of the adduser-package at Debian, thanks for taking care, Marc) has been sent to the Debian BTS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381923
Tip of the day: run 'debbug 381923' or 'debbugm 381923' on your grml-box. :)
Finally: grml 0.8 won't ship nis anymore, so you won't notice this warning message up from now at all.
regards, -mika-
participants (3)
-
Michael Prokop -
s. keeling -
T