Your message dated Sun, 14 Nov 2010 13:11:29 +1100
with message-id <[email protected]>
and subject line Re: Bug#603263: Please close this bug
has caused the Debian Bug report #603263,
regarding portmap: Portmap won't start correctly nor stop at all
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
603263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: portmap
Version: 6.0.0-2
Severity: normal
Portmapper stopped working on my Testing system a while ago.
Can't really tell when, but NFS worked ok for a long time
and then one day about a month ago I noticed that it just
didn't work. Didn't really debug the problem until now...
As for symptoms, stopping portmapper hangs forever (even when
shutting down the system):
x301:~# /etc/init.d/portmap stop
Stopping portmap daemon...
rpcinfo hangs too:
x301:~# ps -fu daemon | grep portmap
daemon 23200 1 0 12:49 ? 00:00:00 portmap -v
x301:~# rpcinfo -p
NFS mounts hang forever:
x301:~# mount nas:/install /mnt
Even trying to manually debug portmapper does absolutely nothing:
x301:~# ps -fu daemon | grep portmap
daemon 23200 1 0 12:49 ? 00:00:00 portmap -v
x301:~# kill -9 23200
x301:~# rm /var/run/portmap*
x301:~# portmap -d
The foreground portmap hangs forever and won't even close if
I ctrl-c it... Killing does work. Shouldn't "portmap -v" give
me a version number and then exit? That does absolutely nothing
on my system....
Granted, I'm on a frankendebian system with packages from Testing,
Unstable, Experimental and Ubuntu... But apart from the 2.6.36
kernel form Experimental anything related to portmapper are
from Testing. And I'm 99% sure portmapper didn't work with the
standard Testing kernel either (because I only upgraded the
kernel about a week ago).
[after a quick reboot]
Yup, portmap is just as stuck with the default Testing kernel
2.6.32-5-amd64.
- Kim
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (500,
'lucid-updates'), (100, 'lucid'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.36-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages portmap depends on:
ii debconf [debconf-2.0] 1.5.36 Debian configuration
ii libc6 2.11.2-7 Embedded GNU C Library:
ii libwrap0 7.6.q-19 Wietse Venema's TCP
ii lsb-base 3.2-23.1 Linux Standard Base 3.2
portmap recommends no packages.
portmap suggests no packages.
-- debconf information:
portmap/loopback: false
--- End Message ---
--- Begin Message ---
Version: 6.0.0-2
On Sat, Nov 13, 2010 at 12:01:12PM +0200, Kim Holviala wrote:
>I had messed up my /etc/network/interfaces so that interface lo never
>got up properly. That was the reason for non-working portmap...
>
>- Kim
Thank you.
--- End Message ---
