02-13-2002
NFS server problems
I have a machine A NFS mounted on machine B
I am doing a build from machine B on the MFS mounted dir of machine A but I keep getting the following:
NFS server A not responding still trying.
I go to machine A and can log onto machine A and everything seems fine.
How do I go about finding the problem ?
Thanks
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I've got a really old system we use for call logging. The OS is SCO 3.2
uname -a output
SCO_SV bts7053 3.2 2 i386
the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are... (1 Reply)
Discussion started by: johno12345
1 Replies
2. Linux
Hi,
my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client.
I always got the messages no permission.
Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies
3. UNIX for Advanced & Expert Users
I am having a really bad day today.
I am trying to get an nfs mount to work. I want to have a mount from machinea:/home going to /home on machineb. I can mount machinea:/home on any mount point EXCEPT /home and see the files. I can not see the files or list the directory (it hangs) when I mount... (17 Replies)
Discussion started by: mbathrick
17 Replies
4. Debian
I'm trying to share some directories with NFS among Debian machines. In order to do so, I installed nfs-common and nfs-kernel-server on the server machine. It seemed that starting portmap daemon lasted a long time and I get the following messages in /var/log/messages:
Jan 30 18:18:03 masternode... (26 Replies)
Discussion started by: bellman
26 Replies
5. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
6. AIX
Hi,
I have two machines (AIX) each on a different VLAN.
Need to mount a filesystem using nfs on the other one.
When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Discussion started by: aixromeo
6 Replies
7. Red Hat
Hi All,
I hoping someone can help me get my NFS working properly. I don't know why I'm having little issues... Overall, NFS is working, therefore, the problem may not be with NFS. I can ssh to remote nodes and view NFS shared directories (/home). Here is the problem, when on a node and I open a... (2 Replies)
Discussion started by: Bic121
2 Replies
8. Red Hat
Hi all,
i have some doubts in a situation that i fail to get an answer in Google.
I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.
The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies
9. AIX
Hi 2 ALL,
try to run NFS Server in AIX 7.1 :
1. Step by step on NFS Server node
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test-- create export directory (fs)
mknfsexp -d /tmp/test -t ro
exportfs -va
show mount -e
:/# exportfs -av
exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
LEARN ABOUT XFREE86
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)