From: Axl Purushu <anup.purushu@katalystpartners.com>
To: Richard Nairn <Richard@nairnconsulting.ca>
Cc: "linux-admin@vger.kernel.org" <linux-admin@vger.kernel.org>
Subject: Re: RPC problems
Date: Sat, 09 Aug 2008 02:34:26 +0530 [thread overview]
Message-ID: <1218229466.4412.22.camel@linux-nlnz.site> (raw)
In-Reply-To: <op.ufk4xpncizdgzp@w5-cal-h014058.nrn.nrcan.gc.ca>
Are there any error or messages in the audit.log. May be selinux is
blocking something.
-Anup
On Fri, 2008-08-08 at 14:38 -0600, Richard Nairn wrote:
> Hi,
>
> After upgrading to Fedora 8, RPC no longer seems to be working. I can't
> get ypserv, ypbind, NFS to work anymore.
>
> rpcbind seems to start happily, and rpcinfo will list it as working:
>
> program version netid address service owner
> 100000 4 tcp 0.0.0.0.13.93 portmapper superuser
> 100000 3 tcp 0.0.0.0.13.93 portmapper superuser
> 100000 2 tcp 0.0.0.0.13.93 portmapper superuser
> 100000 4 udp 0.0.0.0.13.93 portmapper superuser
> 100000 3 udp 0.0.0.0.13.93 portmapper superuser
> 100000 2 udp 0.0.0.0.13.93 portmapper superuser
> 100000 4 local /var/r portmapper superuser
> 100000 3 local /var/r portmapper superuser
> 100000 2 local /var/r portmapper superuser
>
>
> However, once I try and start ypbind, or ypserv I get a Unable to register
> (YPBINDPROG, YPBINDVERS,udp) in my log file, and a similary thing for
> ypserv.
>
> I have tried to reinstall the rpms for rpcbind, ypserv,ypbind but it still
> fails. Any suggestions?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-08-08 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 20:38 RPC problems Richard Nairn
2008-08-08 21:04 ` Axl Purushu [this message]
2008-08-08 21:02 ` Richard Nairn
-- strict thread matches above, loose matches on Subject: below --
2008-08-08 21:02 Max Gribov
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=1218229466.4412.22.camel@linux-nlnz.site \
--to=anup.purushu@katalystpartners.com \
--cc=Richard@nairnconsulting.ca \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).