linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* RPC problems
@ 2008-08-08 20:38 Richard Nairn
  2008-08-08 21:04 ` Axl Purushu
  0 siblings, 1 reply; 4+ messages in thread
From: Richard Nairn @ 2008-08-08 20:38 UTC (permalink / raw)
  To: linux-admin@vger.kernel.org

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?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: RPC problems
@ 2008-08-08 21:02 Max Gribov
  0 siblings, 0 replies; 4+ messages in thread
From: Max Gribov @ 2008-08-08 21:02 UTC (permalink / raw)
  To: Richard Nairn, linux-admin

Off the top off my head and frm cellpphone - check foor any secuurity style acls like selinux/auditd on that machine - yuu may have to explicitly allow file and/or net socket ooperations. I had a similar problem once with a net service and that was the issuue
 

-----Original Message-----
From: Richard Nairn <Richard@nairnconsulting.ca>
Sent: Friday, August 08, 2008 4:38 PM
To: linux-admin@vger.kernel.org <linux-admin@vger.kernel.org>
Subject: RPC problems

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RPC problems
  2008-08-08 21:04 ` Axl Purushu
@ 2008-08-08 21:02   ` Richard Nairn
  0 siblings, 0 replies; 4+ messages in thread
From: Richard Nairn @ 2008-08-08 21:02 UTC (permalink / raw)
  To: anup.purushu; +Cc: linux-admin@vger.kernel.org

selinux is not enabled.

On Fri, 08 Aug 2008 15:04:26 -0600, Axl Purushu  
<anup.purushu@katalystpartners.com> wrote:

> 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
>>



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RPC problems
  2008-08-08 20:38 Richard Nairn
@ 2008-08-08 21:04 ` Axl Purushu
  2008-08-08 21:02   ` Richard Nairn
  0 siblings, 1 reply; 4+ messages in thread
From: Axl Purushu @ 2008-08-08 21:04 UTC (permalink / raw)
  To: Richard Nairn; +Cc: linux-admin@vger.kernel.org

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
> 


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-08-08 21:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-08 21:02 RPC problems Max Gribov
  -- strict thread matches above, loose matches on Subject: below --
2008-08-08 20:38 Richard Nairn
2008-08-08 21:04 ` Axl Purushu
2008-08-08 21:02   ` Richard Nairn

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).