[Bug 688550] Re: portmap/statd can not be restarted
lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as Won't Fix. ** Changed in: portmap (Ubuntu Lucid) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Branch linked: lp:ubuntu/lucid-proposed/portmap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
portmap 6.0.0-1ubuntu2.3 restarts correctly even with open connections. However, when upgrading to portmap 6.0.0-1ubuntu2.3 from 6.0.0-1ubuntu2.2, portmap fails to restart if there's an open connection. (Because the old version wasn't using SO_REUSEADDR, the new version can't take over the port.) I'm not sure this can be avoided though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688550] Re: portmap/statd can not be restarted
On Mon, Dec 10, 2012 at 08:34:05PM -, Steve Atwell wrote: portmap 6.0.0-1ubuntu2.3 restarts correctly even with open connections. However, when upgrading to portmap 6.0.0-1ubuntu2.3 from 6.0.0-1ubuntu2.2, portmap fails to restart if there's an open connection. (Because the old version wasn't using SO_REUSEADDR, the new version can't take over the port.) I'm not sure this can be avoided though. It was discussed that the maintainer script should include a very long timeout between stopping and restarting portmap on upgrade for this reason. I don't know if this was implemented; I did argue that unless something like this was implemented, we should not SRU for this issue alone, due to the fact that the SRU itself triggers the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
I wasn't aware of the specifics wrt to the maintainer script before changing hands to me so I based my conclusion on https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/comments/9 If this is not the case and we need to extend the timeout (I assume greater than 30 seconds?) We need to invalidate this SRU and I can implement the timeout portion of the upgrade process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688550] Re: portmap/statd can not be restarted
Adam, On Mon, Dec 10, 2012 at 10:11:52PM -, Adam Stokes wrote: I wasn't aware of the specifics wrt to the maintainer script before changing hands to me so I based my conclusion on https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/comments/9 If this is not the case and we need to extend the timeout (I assume greater than 30 seconds?) The timeout needs to be 240 seconds. See https://bugs.launchpad.net/bugs/925717 for the full discussion. In particular, comment #9 has my skeleton code for this. We need to invalidate this SRU and I can implement the timeout portion of the upgrade process. Yep, marking v-failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Thanks will get this fixed up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Steve/Goswin, Were either of you able to test that this package resolves your issue? Thanks Adam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
portmap doesn't exist beyond lucid, unsetting all those tasks. ** Changed in: portmap (Ubuntu Maverick) Status: Triaged = Invalid ** Changed in: portmap (Ubuntu Natty) Status: Triaged = Invalid ** Changed in: portmap (Ubuntu Oneiric) Status: Triaged = Invalid ** Changed in: portmap (Ubuntu Lucid) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Uploaded into lucid-proposed. Currently in the unapproved queue. You can check the status here: https://launchpad.net/ubuntu/lucid/+queue?queue_state=1queue_text= Unsubscribing ubuntu-sponsors. Please subscribe again if you want to SRU this change into other releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Changed in: portmap (Ubuntu Lucid) Assignee: (unassigned) = Adam Stokes (adam-stokes) ** Changed in: portmap (Ubuntu Maverick) Assignee: (unassigned) = Adam Stokes (adam-stokes) ** Changed in: portmap (Ubuntu Oneiric) Assignee: (unassigned) = Adam Stokes (adam-stokes) ** Changed in: portmap (Ubuntu Natty) Assignee: (unassigned) = Adam Stokes (adam-stokes) ** Changed in: portmap (Ubuntu Lucid) Milestone: None = lucid-updates ** Changed in: portmap (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: portmap (Ubuntu Lucid) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Changed in: portmap (Ubuntu Lucid) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Patch removed: portmap_lp688550_lucid.debdiff https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+attachment/2725043/+files/portmap_lp688550_lucid.debdiff ** Patch added: portmap_6.0.0-1ubuntu2.1.lucid.debdiff https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+attachment/3402923/+files/portmap_6.0.0-1ubuntu2.1.lucid.debdiff ** Description changed: Binary package hint: portmap - When restarting portmap / statd the old portmap process does not - properly free its socket causing the new portmap process to fail and - upstart to stay stuck in pre-start trying to stop statd. + [Impact] + Anyone attempting to upgrade portmap on Lucid with a currently running portmap process in an established state. + + [Test Case] + When restarting portmap / statd the old portmap process does not properly free its socket causing the new portmap process to fail and upstart to stay stuck in pre-start trying to stop statd. beo-15:~# stop portmap Dec 10 14:20:07 beo-15 init: Connection from private client Dec 10 14:20:07 beo-15 init: portmap goal changed from start to stop Dec 10 14:20:07 beo-15 init: portmap state changed from running to pre-stop Dec 10 14:20:07 beo-15 init: portmap pre-stop process (1996) Dec 10 14:20:07 beo-15 init: portmap pre-stop process (1996) exited normally Dec 10 14:20:07 beo-15 init: portmap state changed from pre-stop to stopping Dec 10 14:20:07 beo-15 init: Handling stopping event Dec 10 14:20:07 beo-15 init: statd goal changed from start to stop Dec 10 14:20:07 beo-15 init: statd state changed from running to pre-stop Dec 10 14:20:07 beo-15 init: statd state changed from pre-stop to stopping Dec 10 14:20:07 beo-15 init: Handling stopping event Dec 10 14:20:07 beo-15 init: statd state changed from stopping to killed Dec 10 14:20:07 beo-15 init: Sending TERM signal to statd main process (1053) Dec 10 14:20:07 beo-15 rpc.statd[1053]: Caught signal 15, un-registering and exiting. Dec 10 14:20:07 beo-15 init: statd main process (1053) exited normally Dec 10 14:20:07 beo-15 init: statd state changed from killed to post-stop Dec 10 14:20:07 beo-15 init: statd state changed from post-stop to waiting Dec 10 14:20:07 beo-15 init: portmap state changed from stopping to killed Dec 10 14:20:07 beo-15 init: Sending TERM signal to portmap main process (1033) Dec 10 14:20:07 beo-15 init: Handling stopped event Dec 10 14:20:07 beo-15 init: portmap main process (1033) killed by TERM signal Dec 10 14:20:07 beo-15 init: portmap state changed from killed to post-stop Dec 10 14:20:07 beo-15 init: portmap post-stop process (1998) Dec 10 14:20:07 beo-15 init: portmap post-stop process (1998) exited normally Dec 10 14:20:07 beo-15 init: portmap state changed from post-stop to waiting Dec 10 14:20:07 beo-15 init: Handling stopped event beo-15:~# start statd Dec 10 14:20:11 beo-15 init: Connection from private client Dec 10 14:20:11 beo-15 init: statd goal changed from stop to start Dec 10 14:20:11 beo-15 init: statd state changed from waiting to starting Dec 10 14:20:11 beo-15 init: Handling starting event Dec 10 14:20:11 beo-15 init: statd state changed from starting to pre-start Dec 10 14:20:11 beo-15 init: statd pre-start process (2001) Dec 10 14:20:11 beo-15 init: Connection from private client Dec 10 14:20:11 beo-15 init: portmap goal changed from stop to start Dec 10 14:20:11 beo-15 init: portmap state changed from waiting to starting Dec 10 14:20:11 beo-15 init: Handling starting event Dec 10 14:20:11 beo-15 init: portmap state changed from starting to pre-start Dec 10 14:20:11 beo-15 init: portmap state changed from pre-start to spawned Dec 10 14:20:11 beo-15 init: portmap main process (2003) Dec 10 14:20:11 beo-15 init: portmap main process (2003) executable changed Dec 10 14:20:11 beo-15 init: portmap main process (2003) became new process (2004) Dec 10 14:20:11 beo-15 init: portmap state changed from spawned to post-start Dec 10 14:20:11 beo-15 portmap: Removing stale lockfile for pid 1033 Dec 10 14:20:11 beo-15 portmap[2004]: cannot bind tcp: Address already in use Dec 10 14:20:11 beo-15 init: portmap post-start process (2005) Dec 10 14:20:11 beo-15 init: portmap main process (2004) terminated with status 1 Dec 10 14:20:11 beo-15 init: portmap main process ended, respawning Dec 10 14:20:11 beo-15 init: portmap goal changed from start to respawn Dec 10 14:20:11 beo-15 init: portmap post-start process (2005) exited normally Dec 10 14:20:11 beo-15 init: portmap goal changed from respawn to start Dec 10 14:20:11 beo-15 init: portmap state changed from post-start to stopping Dec 10 14:20:11 beo-15 init: Handling stopping event Dec 10 14:20:11 beo-15 init: statd goal changed from start to stop Dec 10 14:20:25 beo-15 init: Connection from private client beo-15:~# status portmap portmap start/stopping beo-15:~# status statd statd
[Bug 688550] Re: portmap/statd can not be restarted
Steve, Assuming no blockers are present with this please wait until it is released into -proposed and if you have extra cycles to re-test this that would be greatly appreciated. Thanks Adam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Changed in: portmap (Ubuntu) Assignee: Chris J Arges (christopherarges) = Adam Stokes (adam-stokes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Changed in: portmap (Ubuntu) Assignee: (unassigned) = Chris J Arges (christopherarges) ** Changed in: portmap (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Note that portmap has been dropped from precise as obsolete, entirely superseded by rpcbind. We should probably target this bug at the releases you are considering SRUs for (lucid-oneiric?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
I agree, this should be an SRU. Currently lucid is being targeted, but this is fairly small fix and thus we could apply to lucid-oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
** Changed in: portmap (Ubuntu) Status: Triaged = Won't Fix ** Also affects: portmap (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: portmap (Ubuntu Maverick) Importance: Undecided Status: New ** Also affects: portmap (Ubuntu Natty) Importance: Undecided Status: New ** Also affects: portmap (Ubuntu Oneiric) Importance: Undecided Status: New ** Changed in: portmap (Ubuntu Lucid) Status: New = Triaged ** Changed in: portmap (Ubuntu Maverick) Status: New = Triaged ** Changed in: portmap (Ubuntu Natty) Status: New = Triaged ** Changed in: portmap (Ubuntu Oneiric) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
This patch backports the patch 06-615641-reuse-socket.diff from debian experimental. I have built a test package for verification on lucid: http://people.canonical.com/~arges/lp688550/ Thanks ** Patch added: portmap_lp688550_lucid.debdiff https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+attachment/2725043/+files/portmap_lp688550_lucid.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Tested portmap 6.0.0-1ubuntu3~lp688550 on Lucid and verified that it can restart after being stopped with an active connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Debian package portmap 6.0.0-5 in experimental has patch 06-615642 -reuse-socket.diff that makes portmap set SO_REUSEADDR. I do not understand what the LOOPBACK_SETUNSET #define actually do, but it basically removes it. It's also worth noting that rpcbind suffers from bug #924593, which is quite similar and that upstream resolved by setting the SO_REUSEADDR option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: portmap (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
This happens every time that portmap is stopped while something has a connection open to it. The problem can be reliably reproduced like this: # nc localhost sunrpc [1] 14894 # stop portmap [1] + done nc localhost sunrpc portmap stop/waiting # start portmap start: Job failed to start You can see from netstat that the server-side socket is sitting in TIME_WAIT, blocking portmap from starting: # netstat -a | grep sunrpc tcp0 0 localhost:60269 localhost:sunrpcTIME_WAIT tcp0 0 localhost:sunrpclocalhost:33281 TIME_WAIT I would expect portmap to use SO_REUSEADDR to deal with this case, but apparently it only does this if the weird LOOPBACK_SETUNSET #define is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688550] Re: portmap/statd can not be restarted
This problem does not allways occur. Sometimes portmap starts up just fine right after being stoped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
