Bug#619877: rpc.mountd: svc_tli_create: could not bind to requested address

Hello Lukas, it's this bug you're seeing: https://bugzilla.linux-nfs.org/show_bug.cgi?id=190 I think you have to remove the --port from the option /etc/default/nfs-kernel-server as a workaround. -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--port 32767

Bug#619877: rpc.statd[9340]: failed to create RPC listeners, exiting

Hello Jim, you have to uninstall portmap and install rpcbind. cheers, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions| Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917- | Amtsgericht

Bug#621471: upgrade to 1:1.2.3-1 breaks statd, prevents mounting

Package: nfs-common Version: 1:1.2.3-1 Severity: grave After upgrading to 1:1.2.3-1, statd does not start with error: Apr 7 09:46:04 nux19222 rpc.statd[2129]: failed to create RPC listeners, exiting This prevents NFS mounting. -- System Information: Debian Release: wheezy/sid APT prefers

Bug#562737: failed with Starting NFS common utilities: statd failed!

Package: nfs-common Version: 1:1.2.3-1 Followup-For: Bug #562737 Just got this. The problem seems to be that portmap listens only on IPv4, due to the -i 127.0.0.1 option: # lsof -c portmap portmap 25012 daemon5u IPv4 964900 0t0UDP localhost:sunrpc portmap 25012 daemon

Bug#619877: rpc.mountd: svc_tli_create: could not bind to requested address

Package: nfs-kernel-server Version: 1:1.2.3-1 Followup-For: Bug #619877 Got exactly the same problem, considered it IPv6-related and managed to solve it by 1) replacing portmap with rpcbind (apt-get purge portmap was enough, rpcbind was installed automatically on this). 2) disabling

Bug#621471: nfs-kernel-server has same problem

nfs-kernel-server has also this problem with mountd unable to create RPC listeners. -- Erwan DAVID This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com

Bug#621471: upgrade to 1:1.2.3-1 breaks statd, prevents mounting

using rpcbind instead of portmap works here. cheers, MArc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions| Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917- | Amtsgericht Hildesheim, HRA 2686 |

Bug#621027: Invalid shell option in start-statd

Hello, updating to version 1.2.3 of nfs-common froze my system and made it unbootable (the boot sequence blocked on statd). It still booted in rescue mode, where I could downgrade nfs-common to 1.2.2 and the system works again. I don't know if the problem is the same as the one reported

Processed: Patch from upstream

Processing commands for cont...@bugs.debian.org: forwarded 619781 https://bugs.freedesktop.org/show_bug.cgi?id=35910 Bug #619781 [linux-2.6] i915: mplayer video playback sometimes causes GPU hang Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=35910'. tags 619781

Bug#597489: Solution for this bug

I backported 2.6.38 from sid to squeeze, and the machine is running fine since then. I tried to reproduce the problem with my test case, with no luck. So, it seems that changes that have been performed to the MM subsystem (specifically, the patch I referred to in a previous post) do solve this

[bts-link] source package linux-2.6

# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #620374 (http://bugs.debian.org/620374) # *

Processed: severity of 620516 is important, found 620516 in 2.6.32-31

Processing commands for cont...@bugs.debian.org: severity 620516 important Bug #620516 [linux-2.6] linux-image-2.6.38-1-amd64: Random freezes on 2.6.38-1-amd64 kernel Severity set to 'important' from 'serious' found 620516 2.6.32-31 Bug #620516 [linux-2.6] linux-image-2.6.38-1-amd64: Random

Processed: tagging as pending bugs that are closed by packages in NEW

Processing commands for cont...@bugs.debian.org: # Thu Apr 7 20:03:30 UTC 2011 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: linux-2.6 tags 620204 + pending Bug #620204 {Done: Ben Hutchings

Bug#619781: Patch from upstream

reassign 619781 xserver-xorg-video-intel 2:2.14.0-4 tag 619781 - moreinfo thanks Upstream has provided with a fix to xf86-video-intel, please help to test and integrate. commit 23f9b14df7c102c1036134835dd5d1a508059858 Author: Chris Wilson ch...@chris-wilson.co.uk Date: Sat Feb 12 10:42:34 2011

Re: [Pkg-alsa-devel] Processed: reassign 617743 alsa-driver

On Sun, Apr 03, 2011 at 04:25:16AM +0100, Ben Hutchings wrote: On Fri, 2011-04-01 at 01:03 -0500, Tarek Soliman wrote: On Thu, Mar 31, 2011 at 08:01:37PM +0100, Ben Hutchings wrote: On Thu, Mar 31, 2011 at 08:30:23PM +0200, Elimar Riesebieter wrote: * Debian Bug Tracking System [110331

Bug#621471: upgrade to 1:1.2.3-1 breaks statd, prevents mounting

Hello, I was hit by this bug too, and using rpcbind instead of portmap also works for me. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#620059: nfs-kernel-server: This happens to me following uprade in the last week. What can I wind back to get round it?

Package: nfs-kernel-server Version: 1:1.2.3-1 Followup-For: Bug #620059 The fault shows up during boot. It appears to be mountd that fails. The modified script is because I added -d all to the rpc.mount options in an attempt to find out what was going wrong. It didn't help. rpcinfo -p shows

Re: [Pkg-alsa-devel] Processed: reassign 617743 alsa-driver

On Thu, 2011-04-07 at 16:02 -0500, Tarek Soliman wrote: On Sun, Apr 03, 2011 at 04:25:16AM +0100, Ben Hutchings wrote: On Fri, 2011-04-01 at 01:03 -0500, Tarek Soliman wrote: On Thu, Mar 31, 2011 at 08:01:37PM +0100, Ben Hutchings wrote: On Thu, Mar 31, 2011 at 08:30:23PM +0200, Elimar

Processed: reassign 617743 to linux-2.6, tagging 617743

Processing commands for cont...@bugs.debian.org: reassign 617743 linux-2.6 Bug #617743 [alsa-driver] linux-image: found another USB midi cable with a 4 byte limit Bug reassigned from package 'alsa-driver' to 'linux-2.6'. tags 617743 - sid Bug #617743 [linux-2.6] linux-image: found another USB

Processed: tagging 617743

Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 617743 + pending Bug #617743 [linux-2.6] linux-image: found another USB midi cable with a 4 byte limit Added tag(s) pending. End of message, stopping processing

Processed: tagging 617743

Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 617743 + pending Bug #617743 [linux-2.6] linux-image: found another USB midi cable with a 4 byte limit Ignoring request to alter tags of bug #617743 to the same tags

Processed (with 1 errors): forcibly merging 621471 619877 620088, reassign 621471 to libtirpc1

Processing commands for cont...@bugs.debian.org: forcemerge 621471 619877 620088 Bug#621471: upgrade to 1:1.2.3-1 breaks statd, prevents mounting Bug#619877: rpc.mountd: svc_tli_create: could not bind to requested address Mismatch - only Bugs in the same package can be forcibly merged: Bug

Bug#621707: nfs-common fails to start during boot

Package: nfs-common Version: 1:1.2.3-1 Severity: normal During boot I get numerous errors regarding NFS and particulary on nfs-commons failing to start. There was a just recent bug (~March 16th) regarding inability to install/reinstall nfs-commons and that this problem was fixed with latest

Processed: reassign 619877 to libtirpc1, reassign 620088 to libtirpc1, forcibly merging 621471 619877 620088

Processing commands for cont...@bugs.debian.org: reassign 619877 libtirpc1 Bug #619877 [nfs-kernel-server] rpc.mountd: svc_tli_create: could not bind to requested address Bug reassigned from package 'nfs-kernel-server' to 'libtirpc1'. Bug No longer marked as found in versions

Bug#621707: nfs-common fails to start during boot

On Fri, 2011-04-08 at 03:34 +0200, Adnan Hodzic wrote: Package: nfs-common Version: 1:1.2.3-1 Severity: normal During boot I get numerous errors regarding NFS and particulary on nfs-commons failing to start. There was a just recent bug (~March 16th) regarding inability to install/reinstall

Processed: tagging 621707

Processing commands for cont...@bugs.debian.org: tags 621707 + moreinfo Bug #621707 [nfs-common] nfs-common fails to start during boot Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 621707:

Processed: tagging 621707

Processing commands for cont...@bugs.debian.org: tags 621707 - moreinfo Bug #621707 [nfs-common] nfs-common fails to start during boot Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 621707:

Processed (with 2 errors): cloning 621471, reassign 621471 to nfs-common, block 621471 with -1

Processing commands for cont...@bugs.debian.org: clone 621471 -1 Bug#621471: upgrade to 1:1.2.3-1 breaks statd, prevents mounting Bug is marked as being merged with others. Use an existing clone. reassign 621471 nfs-common Bug #621471 [libtirpc1] upgrade to 1:1.2.3-1 breaks statd, prevents

Bug#610323: Question regarding software...

Out of curiosity - when you have experienced this bug, have you been running the Chromium browser (or Google Chrome) when you hibernated? I've been able to replicate, fairly repeatably, this same BUG, by attempting to hibernate with chromium running (I receive the exact same backtrace). Without

Bug#562737: failed with Starting NFS common utilities: statd failed!

On Thu, 2011-04-07 at 09:48 +0200, Gábor Gombás wrote: Package: nfs-common Version: 1:1.2.3-1 Followup-For: Bug #562737 No, this is a different bug. Just got this. The problem seems to be that portmap listens only on IPv4, due to the -i 127.0.0.1 option: # lsof -c portmap portmap 25012

Bug#621471: Protocol selection for access to rpcbind is broken

On Fri, 2011-04-08 at 04:51 +0100, Ben Hutchings wrote: Package: libtirpc1 Version: 0.2.1-1 X-Debbugs-Cc: 621...@bugs.debian.org On Fri, 2011-04-08 at 03:24 +0100, Ben Hutchings wrote: libtirpc really does a terrible job of protocol fallback. When trying to connect to rpcbind/portmap,

Bug#621471: libtirpc is incompatible with portmap

On 04/08/2011 04:24 AM, Ben Hutchings wrote: libtirpc really does a terrible job of protocol fallback. When trying to connect to rpcbind/portmap, it iterates over the protocols listed in /etc/netconfig (nice choice of name, oh yeah) and tries to create a socket for each in turn. Then it