public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John Blinka" <john.blinka@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] help with the dreaded mount: RPC: Program not registered
Date: Fri, 21 Sep 2007 19:45:47 -0400	[thread overview]
Message-ID: <e6b926b90709211645p34086bbei7c99afcb0076b102@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

Hi, all,

I have 2 gentoo machines, lotus and tobey.   tobey is an nfs server to
lotus.
Today I upgraded tobey, and now nfs doesn't work.  Previously, it worked for
years.  The symptoms are:

1)  mount -v /mnt/tobey on lotus returns
     mount: RPC: Program not registered

2)  /etc/init.d/nfs start on tobey produces no output, no running
    nfsd daemons, and exit code 1.

3) There is nothing particularly informative (to me)
    in the system logs.  There is one instance of

    tobey rc-scripts: ERROR:  cannot start nfs as rpc.statd could not start

    after the reboot following today's upgrade.

    I've started rpc.statd by hand and then attempted to start nfs,
    but nfs still does not start.  There is no information in the system
    log explaining why.

4) I've done the usual google search, and followed the advice of
    other people who have had this problem, and I have read the
    available Gentoo Wiki documents that discuss this problem
    and followed the advice there.  The result:  nfs still does not
    start.

5) tobey is a machine which doesn't like to start various daemons
    when it boots despite their being managed by rc-update.  I have
    no idea why - this situation started a few months ago after an
    upgrade.  I start them by hand after reboots.

6) I always do revdep-rebuild and always follow the post installation
    instructions mailed by portage's elog facility.

So, any brilliant ideas about why I can't start nfs or how to debug the
problem?

As always, thanks for your help!

John Blinka

[-- Attachment #2: Type: text/html, Size: 2029 bytes --]

             reply	other threads:[~2007-09-21 23:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 23:45 John Blinka [this message]
2007-09-22 11:52 ` [gentoo-user] help with the dreaded mount: RPC: Program not registered Emil Beinroth
2007-09-22 20:58   ` John Blinka
2007-09-23 10:11     ` Emil Beinroth
2007-09-23 12:24       ` John Blinka
2007-09-23 13:55         ` Emil Beinroth
2007-09-23 19:37           ` John Blinka
2007-09-23 21:29             ` Emil Beinroth
2007-09-24 12:07               ` John Blinka
2007-09-25  0:19                 ` Bogo Mipps
2007-09-25 12:17                   ` John Blinka
2007-09-25 21:26                 ` Emil Beinroth
2007-09-28 11:21                   ` John Blinka
2007-09-24  1:04         ` Alex Schuster
2007-09-22 16:51 ` Dan Farrell
2007-09-22 21:12   ` John Blinka
2007-09-24  3:32     ` Dan Farrell
2007-10-09  1:54 ` [gentoo-user] Re: [SOLVED] " John Blinka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e6b926b90709211645p34086bbei7c99afcb0076b102@mail.gmail.com \
    --to=john.blinka@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox