search for: rpcinfo

...nd use the system as you'd expect. I have done this before, however this time I decided to try using ClusterNFS so that the diskless clients can share the boot server's filesystem. Unfortunately during system boot up to test whether the RPC portmapper is loaded, the boot scripts run "rpcinfo -p" which causes the PC to sit there for about ten minutes and then eventually time out and continue with the boot process. This happens three times during boot, which needless to say means there's a *long* wait before I can log in. Does anyone have any idea why this would happen? Altho...

An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120304/04099724/attachment.html>

...ote nfs share. The first hurdle was that "portmap" didn't appear in the chkconfig list, it was installed with the initial packages but not added to chkconfig. Took me a while to figure this out. Adding and starting it up is no problem. But nfs still doesn't work and when I try rpcinfo -p that just hangs until it finally times out after a long while (rpcinfo to another machine is fine). An strace at that time indeed shows that it is stuck trying to connect to port 111 on localhost. Same when I try to connect with telnet. Port 111 shows up on lsof UDP and TCP and there's n...

...running, but ypbind is confirmed to be running #ps -ef | grep ypbind root 3033 1 0 15:11 ? 00:00:00 /usr/sbin/ypbind ypcat also does not work #ypcat netgroup No such map net group. Reason: Can't bind to the server which serves this domain I have double checked that the server is running #rpcinfo -u myServer ypserv program 100004 version 1 ready and waiting program 100004 version 2 ready and waiting The domain name seems to be set correctly as well #domainname myDomain I have tried disabling iptables and selinux, but that has no effect. I am probably missing something obvious, but NIS ha...

Morning Folks, should I prefer NFS with UCARP or native GlusterFS mounts for serving the system images to XCP? Which one performes better over 1G network links? NFS is probaby easier to setup due to existing tools like rpcinfo and showmount, both are used inside the storage container code, and there is some code for NFS, not for GlusterFS, except I write one. UCARP has the disadvantage that the cluster IP is moved away from dead systems, not from dead gluster server daemons, IMHO. What do you think about that? Best...

Hi,guys: I am trying to connect to a NFS-filesystem on a CentOS 5.3 i386 guest system. The host system is CentOS 5.4 x86_64. I set up the NFS server correctly and rpcinfo is also ok inside the guest system show. The problem is, I can't connect to, or see the open port from the outside. I use the Host-Only network setup with VirtualBox 3.1.0, the ip address in the guest system is 192.168.56.101 . and the host system ip address is 192.168.7.67 When I mount the...

...= "sarge-nfs" dhcp="dhcp" root = "/dev/nfs" nfs_server = ''10.10.24.141 <http://10.10.24.141>'' nfs_root=''/nfsroot'' extra = "2" /etc/exports on NFS server ************************* /nfsroot *(rw,sync,no_root_squash) rpcinfo -p output on NFS server program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100021 1 udp 1090 nlockmgr 100021 3 udp 1090 nlockmgr 100021 4 udp 1090 nlockmgr 100021 1 tcp 1036 nlockmg...

...ranges, but that doesn't seem to help. portmap & nfs is running as well. But as I say, as soon as I disable the firewall, it mounts fine. Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help. root at saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195...

...ter 3w-9xxx alias scsi_hostadapter1 usb-storage alias eth0 e1000e options lockd nlm_udpport=1011 options lockd nlm_tcpport=1011 and then restarting the pormap service. I've even tried restarting the network service, but unfortunately nothing seems affected: [root at stallion:/etc/init.d] $ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 55394 nlockmgr 100021 3 udp 55394 nlockmgr 100021 4 udp 55394 nlockmgr 100021 1 tcp 33704 nlockmgr 100021 3 tcp 33704...

...D_TCPPORT=32803 LOCKD_UDPPORT=32769 MOUNTD_PORT=892 STATD_PORT=662 As well as my /etc/services file: # Local services rquotad 875/tcp lockd 32803/tcp lockd 32769/tcp mountd 892/tcp statd 662/tcp rquotad 875/udp lockd 32803/udp lockd 32769/udp mountd 892/udp statd 662/udp [root at centos sy rpcinfo -p seems fine (although I understand that is not relevent with nfs4) [root at centos sysconfig]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 662 status 100024 1 tcp 662 status 1...

...r reply Josef. > In netstat -p |grep rpc I get: > dgram 56732 rpc.nfsd > dgram 55905 rpc.mountd > While client looks for socket 100003/2 or 100005/1, mine rpc.mountd is on socket 55905. Maybe it is a reason for an error 22. >The port numbers are RPC numbers, not sockets. Try 'rpcinfo -p' for these. rpcinfo -p 100005 mountd 100003 nfs So this looks ok I asume. ( cut it, have no Internet connection on that computer) >Looks like you exported the NFS directory wrong. Did you try to mount >this directory by another client? I have not tried yet to mount directory by a...

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

...CTDB begins to flap on an affected cluster node. Clients connected to that node see the NFS server not responding. 2) After the fail-over, the CTDB log on the affected node is full of complaints about event scripts timing out. The first script to time out *seems* always to be `61.nfstickle` or rpcinfo itself (perhaps rpcinfo running under the authority of the CTDB event scripts), followed by timing out of event scripts related to releasing IPs for takeover. Additionally, around the event, we see the IP-receiving peer logging a lot of errors about CTDB control traffic timing out. 3) Fail-back...

...ot; # Optional arguments passed to rpc.gssd. See rpc.gssd(8) #RPCGSSDARGS="" # Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8) #RPCSVCGSSDARGS="" # # To enable RDMA support on the server by setting this to # the port the server should listen on #RDMA_PORT=20049 And rpcinfo -p: program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100003...

...rver. These are my config files: /tftpboot/pxelinux.cfg/default I got: LABEL linux KERNEL bzImage APPEND root=/dev/nfs ip=dhcp nfsroot=192.168.1.1:/netboot/base /etc/exports: /netboot/base 192.168.1.0/255.255.255.0(rw,no_root_squash) /etc/hosts.allow: ALL:ALL /etc/hosts.deny: is empty rpcinfo -p : says portmapper, mountd and nfs are active. My log that logs all says nothing after DHCPPACK for ip assignment by dhcpd and "tftp: client does not accept options" which is normal I understand. I have also tried to use other kernels and root filesystems (in /netboot/base, client was...

Hi Everyone, I have been trying to setup an NFS v4 File Server but have come across an odd issue. Mounting the /nfs4exports/share appears to be successful and the information displayed about partition size and free space seem correct but if I try to do anything inside the mounted directory the client will just hang. Does anyone have any idea what I am missing?? I have try disabling all

...er. I stopped shorewall and tried again however it still would not connect which should eliminate shorewall. I am not sure that I have NIS set up correctly however I was wondering if anyone has got NIS working with shorewall and could supply me with a rule set to open the correct ports. I ran rpcinfo and opened the ports that I could see associated with ypserver and ypbind however this made no difference. As I said I am not at all sure that I had NIS set up correctly but I would like to see a working rule set if possible. Thanks

I'm trying to NFS-mount a CentOS directory on my Fedora laptop, but I find I can only do this is I turn off the firewall on the CentOS server. If instead I go to system-config-securitylevel-tui on the server, and allow NFS4, this does not do the trick. Nor does allowing port 2049. What do I need to allow? [I should say that the CentOS server is remote, and difficult to access directly; that

So I configured my Enterprise 5 server to have NFS configured on specific ports via the NFS Server menu option. Since having done that, I am unable to get my two CentOS 5 workstations to bind via YP. One worked just fine before the port reconfiguration, but broke after. The other never worked fine. NFS works fine on both, but NIS will no longer bind. What do I need to change on the client

...ndows NT share to solaris 8.0 using Redhat 8.0 nfs. Using smbmount I mounted windows share in Linux as /home/percipia/smb. I setup Linux as NFS Server and exported /home as nfs export. [root@ldap root]# cat /etc/exports /home 192.168.1.0/255.255.255.0(ro,nohide,insecure,sync) [root@ldap root]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 391002 2 tcp 32769 sgi_fam 100011 1 udp 639 rquotad 100011 2 udp 639 rquot...