similar to: service nfs start hangs on CentOS 4

Displaying 20 results from an estimated 20000 matches similar to: "service nfs start hangs on CentOS 4"

2002 May 14
3
network boot nfs as root
Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error
2005 Aug 23
6
NFS-root problem
I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:
2012 Mar 04
1
Unable to start nfs server
An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120304/04099724/attachment.html>
2010 Feb 03
2
cannot mount NFS share, portmap problems, what todo?
Hi all, I want to map an NFS share from a remote server to a local CentOS 5.4 server, but have a problem with portmap: root at mercury:[~]$ service portmap restart pmap_getmaps rpc problem: RPC: Unable to receive; errno = Connection reset by peer Stopping portmap: [FAILED] Starting portmap: [ OK ] root at
2006 Sep 25
1
Pls help on configuring autofs on NFS
Hi all, I'm trying to setup this scenario on NFS and autofs on Centos 4.3: - useradd nfstest on an NFS server (192.168.1.247) - Setting up this NFS server /etc/exports: /home/nfstest 192.168.1.252/255.255.255.0(rw,sync,no_root_squash) - useradd nfstest on a client machine (192.168.1.252) - make sure that the uid and gid are the same on the server and the client - setting up
2008 Feb 13
1
Linux client cannot mount to NFS-Root: Portmap RPC call returned error 101
Hello all, I have seen various reports on this error posted in the past few years, but was unable to find a resolution to the various postings. I've googled the error messages too, and have hit on various sporadic similar problems encountered with no resolutions .. Apologize if this has been exhaustively queried upon in the past; however, I'd like to try asking again, nevertheless:
2007 Aug 15
1
nfs installation
Im trying to install nfs on my server. i tried to do apt-get install nfs nfs-lock portmap. but portmap is the only one available. Is there a new name for nfs and nfs-lock nowadays? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070815/ad008576/attachment.html>
2005 Sep 06
2
network probs trying to get nfs root to work
Hi. trying to get a domU (dom1) up using nfs root. never done this before ;-). I have dom0 up (2.6.12-xen0) and i have an external nfs server with a nice root disk populated. i get this after xm create -c dom1 vmid=1 . . . IP-Config: Complete: device=eth0, addr=172.31.205.229, mask=255.255.255.0, gw=172.31.205.2, host=vm%d, domain=, nis-domain=(none),
2004 Dec 31
2
CUPS/NFS
Is there anyway to remove CUPS and NFS on the system, I'd like to stop these services, close the ports, and uninstall the software as I don't use NFS for anything on my system, and for sure don't use printing on the server. Regards, Joshua Strzalko President, Eleet Technologies, Inc. Office: 407.977.2857 Mobile: 407.923.6926 Fax: 321.244.9435 josh at eleet-tech.com
2005 Sep 28
1
NFS Mount - RH7.3 Server - CentOS 4.1 Client
Hi Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1 Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server. When i try and mount the NFS share on the CentOS box i get the following error # mount /mnt/cvs mount to
2010 Feb 18
3
NFS client firewall config?
Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to
2007 Apr 13
8
Many Fedora 6 packages in CentOS 5
Why are there so many Fedora 6 packages in CentOS 5? Are there something wrong with the build system? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20070413/2a65a831/attachment-0004.bin>
2010 Oct 21
1
Some client problems with TCP-only NFS in Gluster 3.1
I see that the built-in NFS support registers mountd in portmap only with tcp and not udp. While this makes sense for a TCP-only NFS implementation, it does cause problems for some clients: Ubuntu 10.04 and 7.04 mount just fine. Ubuntu 8.04 gives "requested NFS version or transport protocol is not supported", unless you specify "-o mountproto=tcp" as a mount option, in
2014 Sep 25
1
daemon for nfs client
In days of old, in Solaris there was a daemon for NFS Client, and NFS server (actually several including portmap...). I am unable to find reference to the daemon that runs NFS client But the RedHat Documentation does not explain the NFS client daemon. Is this a service or something else. on centos6.5 I previously posted about a really weird root filesystem. It started on another non critical
2020 Nov 20
1
Desktop Over NFS Home Blocked By Firewalld
On 11/20/20 1:26 PM, Michael B Allen wrote: > Thanks for the inputs but my problem has nothing to do with NFS. Do you think that because you saw "krbupdate" in /etc/services? The problem you've described is definitely an NFSv3 problem.? The connections causing the client to hang are portmap connections. They're dynamic, and don't necessarily conform to /etc/services.
2006 Nov 29
1
TCP checksum change in RPC replies within XEN, NFS lockup (SLES10)
Hello, my apologies for not being sure whom to tell this problem, but it is very strange. Let me tell the story: I''m using XEN (3.0.2) with SLES10 (x86_64, SunFire X4100). On one machine I have three virtual machines ("DomU") that are very identically configured (SLES10 x86_64 also). There is also a SLES9 (i386) acting as a multi-homed NFS server. I can mount and access a
2007 Apr 13
1
Install of CentOS fails on systems less 256MB RAM
When try to install CentOS 5 via ftp on an system with less then 256MB RAM it fails. After select the ftp server witch contains the data, some files are loaded, then the dialog witch prompt for the ftp sever is shown again. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic
2008 Apr 10
1
OT: get files with wget
Hello, how can I get all files from an directory of an web server. An simple wget http://www.foo.bar/sample/* will not work:( Thanks for your help. Frank -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic Signature URL:
2017 Sep 22
0
BUG: After stop and start wrong port is advertised
I've already replied to your earlier email. In case you've not seen it in your mailbox here it goes: This looks like a bug to me. For some reason glusterd's portmap is referring to a stale port (IMO) where as brick is still listening to the correct port. But ideally when glusterd service is restarted, all the portmap in-memory is rebuilt. I'd request for the following details from
1998 Dec 15
1
portmap & tcpwrappers
I don't know if this is RedHat 5.1 specific, but be aware that the version of portmap distributed is the enhanced (Wietse Venema) version. That's great, except for two things. The first is documented, but easy to overlook: "In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name...The upshot of all this is that only network