search for: 100005

...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: Unable to get nfsd port number from server, using default Looking up port of RPC 100005/1 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 -- My domain configuration *********************** kernel = "/boot/vmlinuz-2.6-xenU" memory = 128 name = "sarge-nfs" dhcp="dhcp" root = "/dev/nfs" nfs_server = ''10.10.24.1...

...4004 rquotad 100011 1 tcp 4004 rquotad 100011 2 tcp 4004 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 4003 mountd 100005 1 tcp 4003 mountd 100005 2 udp 4003 mountd 100005 2 tcp 4003 mountd 100005 3 udp 4003 mountd 100005 3 tcp 4003 mountd -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog:...

I am working with a longitudinal data set in the long format. This data set has three observations per grade level per year. Here are the first 10 rows of the data frame: >tenn.dat[1:10,] year schid type grade gain se new cohort 6 2001 100005 5 4 33.1 3.5 4 3 7 2002 100005 5 4 33.9 3.9 4 2 8 2003 100005 5 4 32.3 4.2 4 1 10 2001 100005 5 5 22.9 4.0 5 4 11 2002 100005 5 5 25.0 3.4 5 3 12 2003 100005 5 5 7.8 3.8 5 2 18 2001 100010 1 4 34.4 5...

Hi all: I solved the previous stated problem in something of a brute force way (but it works). I seem to now be running into one little hiccup using reshape. Here is a quick snip of the data in long format: grade stability year schid 6 Grade 4 3 2001 100005 7 Grade 4 3 2002 100005 8 Grade 4 2 2003 100005 10 Grade 5 2 2001 100005 11 Grade 5 2 2002 100005 12 Grade 5 1 2003 100005 18 Grade 4 2 2001 100010 19 Grade 4 2 2002 100010 20 Grade 4 2 2003 100010 22 Grade 5 2 2001...

...100021 3 udp 32769 nlockmgr 100021 4 udp 32769 nlockmgr 100021 1 tcp 32803 nlockmgr 100021 3 tcp 32803 nlockmgr 100021 4 tcp 32803 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 892 mountd 100005 1 tcp 892 mountd 100005 2 udp 892 mountd 100005 2 tcp 892 mountd 100005 3 udp 892 mountd 100005 3 tcp 892 mountd And services are running: [root at centos sysconfig]# service nfs status rpc.mountd (p...

...100011 2 udp 639 rquotad 100011 1 tcp 642 rquotad 100011 2 tcp 642 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 32787 nlockmgr 100021 3 udp 32787 nlockmgr 100021 4 udp 32787 nlockmgr 100005 1 udp 32788 mountd 100005 1 tcp 32815 mountd 100005 2 udp 32788 mountd 100005 2 tcp 32815 mountd 100005 3 udp 32788 mountd 100005 3 tcp 32815 mountd In Solaris, I was able to mount the Linux nfs share: bash-2.03# showmount -e 192.168.1...

...) I get one row and 10000 columns instead of what I want two columns and 10000 rows when I convert the list that dbApply returns to a Data frame. The list I want to convert looks like this structure(list("10000" = 123.85, "100003" = 59.7, "100004" = 61.5, "100005" = 61.525, "10001" = 124.525, "100016" = 64.93848, "100018" = 64.55, "10002" = 125.435, "100020" = 61.5714, . . . "9998" = 124.75, "99987" = 58.86503, "99989" = 61.93, "9999" = 123.8625, &q...

...are/samba/homes directory look like this root at fileserver:/var/share/samba# getfacl homes/ # file: homes/ # owner: MYDOMAIN\134administrator # group: MYDOMAIN\134domain\040admins user::rwx user:MYDOMAIN\134administrator:rwx group::rwx group:MYDOMAIN\134domain\040admins:rwx group:100004:r-x group:100005:rwx mask::rwx other::--- default:user::rwx default:user:MYDOMAIN\134administrator:rwx default:group::--- default:group:MYDOMAIN\134domain\040admins:rwx default:group:100004:r-x default:group:100005:rwx default:mask::rwx default:other::--- I noticed GIDs 100004 and 100005 are not resolved so I trie...

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

...t at fileserver:/var/share/samba# getfacl homes/ > # file: homes/ > # owner: MYDOMAIN\134administrator > # group: MYDOMAIN\134domain\040admins > user::rwx > user:MYDOMAIN\134administrator:rwx > group::rwx > group:MYDOMAIN\134domain\040admins:rwx > group:100004:r-x > group:100005:rwx > mask::rwx > other::--- > default:user::rwx > default:user:MYDOMAIN\134administrator:rwx > default:group::--- > default:group:MYDOMAIN\134domain\040admins:rwx > default:group:100004:r-x > default:group:100005:rwx > default:mask::rwx > default:other::--- > >...

...rnel 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 22 portmap: RPC call returned error 22 ROOT-NFS:unable to get nfsd port number from server, using default RPC: sendmsg returned error 22 mount: RPC call returned error 22 ROOT-NFS: server returned error -22 while mounting 192.168.1.1:/netboot/base VFS: c...

...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 100005 1 udp 597 mountd 100005 1 tcp 597 mountd 100005 2 udp 597 mountd 100005 2 tcp 597 mountd 100005 3 udp 597 mountd 100005 3 tcp 597 mountd 100003 3 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1...

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22

...tfacl homes/ >> # file: homes/ >> # owner: MYDOMAIN\134administrator >> # group: MYDOMAIN\134domain\040admins >> user::rwx >> user:MYDOMAIN\134administrator:rwx >> group::rwx >> group:MYDOMAIN\134domain\040admins:rwx >> group:100004:r-x >> group:100005:rwx >> mask::rwx >> other::--- >> default:user::rwx >> default:user:MYDOMAIN\134administrator:rwx >> default:group::--- >> default:group:MYDOMAIN\134domain\040admins:rwx >> default:group:100004:r-x >> default:group:100005:rwx >> default:mask::rw...

...Secondary Master), but it identifies three drives - clearly the server's drives. 2. Most importantly, it stops at this point: Looking up port of RPC 100003/2 on 172.20.0.1 RPC: sendmsg returned error 101 Root-NFS: Unable to get nfsd port number from server, using default Lookingup port of RPC 100005/1 on 172.20.0.1 RPC: sendmsg returned error 101 Root-NFS: Unable to get mountd port number from server, using default RPC sendmsg returned error 101 Mount: RPC call returned error 101 Root-NFS: Server returned error -101 while mounting / VFS: Unable to mount root fs via NFS, trying floppy. VFS: Ins...

...essary packages needed to suppport NFS version 3 intalled in my DomU (Debian) as well as NFS Server. But still they communicate using version 2. Why is that?? In the output of Xen while booting DomU we get these two lines ... Looking up port of RPC 100003/2 on 192.168.23.239 Looking up port of RPC 100005/1 on 192.168.23.239 (192.168.23.239 is my NFS Server IP) Does this tell something? Is it that Xen tries for NFS (100003) version 2 and mount (100005) version 1 despite what we write in the fstab file given in our DomU system?? Is it that we need to change some configurations in the Xen itself? ( N...

...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 100024 1 udp 54233 status 100024 1 tcp 32813 status 100005 2 udp 20048 mountd 100005 2 tcp 20048 mountd 100003 4 tcp 2049 nfs 100003 4 udp 2049 nfs 100021 3 udp 56990 nlockmgr 100021 3 tcp 40572 nlockmgr # systemctl status nfs ? nfs-server.service - NFS server and services Loaded: loaded (...

...fs -o vers=3 mdstor:/mnt/xfs1/apps tmpx -v mount.nfs: timeout set for Tue Feb 16 08:33:31 2016 mount.nfs: trying text-based options 'vers=3,addr=143.219.41.19' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 143.219.41.19 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 143.219.41.19 prog 100005 vers 3 prot UDP port 892 mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed Thanks, William

Hi, Thanks for your 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...

...Linux custom, Dragan Stancevic visitor at valinux.com 2000/11/15 Partiton Check: hda: hda1 Looking up port of RPC 100003/2 on 140.111.161.1 RPC: sendmsg returned error 101 Protmap: RPC call returned error 101 Root-NFS: Unable to get nfsd port number from server, using default Lookingup port of RPC 100005/1 on 140.111.161.1 RPC: sendmsg returned error 101 Protmap: RPC call returned error 101 Root-NFS: Unable to get mountd port number from server, using default RPC sendmsg returned error 101 Mount: RPC call returned error 101 Root-NFS: Server returned error !V101 while mounting /export/home/diskless...