On 12/7/19 9:09 PM, Tim via users wrote:
The notion of only rebooting when you really need it has gone right out
the window, to be replaced by the Windows-centric thinking that it's
easier just to reboot rather than assess whether it's really necessary.
Non-technical users don't need to run int
On 2019-12-08 14:59, Samuel Sieb wrote:
> On 12/7/19 6:10 PM, Bob Goodwin wrote:
>> [root@NFS-Server bobg]# exportfs -a
>> exportfs: Failed to stat /nfs4exports/home: No such file or directory
>>
>> Ok, I have been able to get this far before another failure. It may be time
>> to fix my /etc/expor
On 12/7/19 6:10 PM, Bob Goodwin wrote:
[root@NFS-Server bobg]# exportfs -a
exportfs: Failed to stat /nfs4exports/home: No such file or directory
Ok, I have been able to get this far before another failure. It may be
time to fix my /etc/exports.
Right, you still haven't answered what is possib
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote:
> As an aside, for some weird reason way beyond what makes sense on a
> machine with an inode-based filesystem, the Gnome software tool has
> a problem where it almost always wants to reboot to apply the
> changes. That's an inconvenience that
On 2019-12-07 18:55, Ed Greshko wrote:
[root@f31k ~]# cat /etc/exports
/home/egreshko 192.168.0.0/16(rw,sync,insecure,no_root_squash,no_subtree_check)
/home/egreshko
2001:B030:112F:::/56(rw,sync,insecure,no_root_squash,no_subtree_check)
[root@f31k ~]# exportfs -a
.
[root@NFS-Server bo
On 2019-12-08 09:11, Bob Goodwin wrote:
> [root@NFS-Server bobg]# etc]# firewall-cmd --zone=public
> --add-service=rpc-bind
> bash: etc]#: command not found
>
> Then this step fails?
You have copied/pasted in error.
You pasted "etc]# firewall-cmd --zone=public --add-service=rpc-bind "
You want
On 2019-12-07 18:55, Ed Greshko wrote:
So..
[root@f31k etc]# firewall-cmd --zone=public --add-service=nfs
success
[root@f31k etc]# firewall-cmd --zone=public --add-service=mountd
success
[root@f31k etc]# firewall-cmd --zone=public --add-service=rpc-bind
.
Followed you to here:
[root@NFS
On 12/7/19 2:54 PM, Bob Goodwin wrote:
On 2019-12-07 16:17, Samuel Sieb wrote:
On 12/7/19 1:13 PM, Bob Goodwin wrote:
Well it appears there must be something wrong with my server files
installation. /nfs4exports does not lead to /home1 or /home?
nfs4exports is part of /etc/exports:
Being in
On 2019-12-08 07:17, Bob Goodwin wrote:
>
> On 2019-12-07 17:19, Patrick O'Callaghan wrote:
>> Note that the GUI is not 100% reliable, i.e. it can misrepresent what
>> is actually configured.
>>
>> Seehttps://bugzilla.redhat.com/show_bug.cgi?id=1773273
>>
>> Also, try "firewall-cmd --get-active-zon
On 2019-12-07 17:19, Patrick O'Callaghan wrote:
Note that the GUI is not 100% reliable, i.e. it can misrepresent what
is actually configured.
Seehttps://bugzilla.redhat.com/show_bug.cgi?id=1773273
Also, try "firewall-cmd --get-active-zones" and "... --get-default-
zone" to make sure you're loo
On 2019-12-07 16:17, Samuel Sieb wrote:
On 12/7/19 1:13 PM, Bob Goodwin wrote:
Well it appears there must be something wrong with my server files
installation. /nfs4exports does not lead to /home1 or /home?
nfs4exports is part of /etc/exports:
Being in the /etc/exports file doesn't make a di
On Sat, 2019-12-07 at 13:58 -0500, Bob Goodwin wrote:
> On 2019-12-07 13:14, Patrick O'Callaghan wrote:
> > You're not seeing anything that says "allow NFS", which means that it's
> > blocked. The services line shows what should be let through.
>
> .
>
> Well I am lost in the Firewalld GUI with
On 12/7/19 1:13 PM, Bob Goodwin wrote:
Well it appears there must be something wrong with my server files
installation. /nfs4exports does not lead to /home1 or /home? nfs4exports
is part of /etc/exports:
Being in the /etc/exports file doesn't make a directory exist. Where is
the directory th
On 2019-12-07 15:19, Samuel Sieb wrote:
[bobg@Workstation-1 ~]$ showmount -e 192.168.2.128
clnt_create: RPC: Unable to receive
Is that the IP address of the NFS server or Workstation-1?
.
192.168.2.128 is the nfs server.
As Tim said, this should be:
mount 192.168.2.128:/nfs4exports/home
On 12/7/19 8:30 AM, Bob Goodwin wrote:
[bobg@Workstation-1 ~]$ showmount -e 192.168.2.128
clnt_create: RPC: Unable to receive
Is that the IP address of the NFS server or Workstation-1?
This computer's fstab has the line: 192.168.2.128:home1 /media/nfs
nfs4 rw,soft,intr,fg,comment=systemd.au
On 2019-12-07 14:09, Joe Zeff wrote:
Were you getting SELinux alerts? If not, it wasn't the issue, so why
did you think setting it to permissive would help?
.
I did not think it would help but there's always someone who suggests
stopping selinux. I never see any problems with it since most
On 2019-12-07 12:51, Tim Evans wrote:
Wouldn't this be?
mount 192.168.2.128:/nfs4exports/home1 /media/nfs
.
No, that doesn't connect either but I can't make any sense of my server
files, think I have something wrong there ... the home1 looks like the
problem area.
--
Bob Goodwin - Zuni
On 12/07/2019 11:58 AM, Bob Goodwin wrote:
Well I am lost in the Firewalld GUI with connections and zones,
permanent seems obvious, but I will have to learn more there. However
I've changed nothing in Firewalld in this computer and it did work
through the firewall just a few days ago, as I sai
On 2019-12-07 13:14, Patrick O'Callaghan wrote:
You're not seeing anything that says "allow NFS", which means that it's
blocked. The services line shows what should be let through.
.
Well I am lost in the Firewalld GUI with connections and zones,
permanent seems obvious, but I will have to
(on Thursday, 12-05-2019, George said...)
> From my experience, the drive has already lost or corrupted your data.
> You may be able to recover some of the files, but attempts to "repair"
> the filesystem risk destroying more data. You can try making a "clone"
> of the USB drive using dd, etc. ont
On Sat, 2019-12-07 at 12:20 -0500, Bob Goodwin wrote:
> I'm not certain what to look for but I don't see anything I recognize
> that says"no NFS"
You're not seeing anything that says "allow NFS", which means that it's
blocked. The services line shows what should be let through.
poc
_
On 12/7/19 11:30 AM, Bob Goodwin wrote:
This computer's fstab has the line: 192.168.2.128:home1 /media/nfs
nfs4 rw,soft,intr,fg,comment=systemd.automount 0 0
And at the server exports is:
[bobg@NFS-Server ~]$ cat /etc/exports
/nfs4exports/home1
192.168.2.0/24(rw,sync,insecure,no_root_squa
On 2019-12-07 12:02, Patrick O'Callaghan wrote:
Could be a firewall issue. Check the output of:
$ firewall-cmd --list-all
IIRC it should include nfs, nfs3, mountd and rpc-bind.
poc
I should have said I tried stopping the firewall and selinux
individually. I am seeing the following:
[root
On Sat, 2019-12-07 at 11:30 -0500, Bob Goodwin wrote:
> .
>
> Due to failure of a 3TB Seagate hard drive (DOM 28 April 2019) i am
> rebuilding the server again, this time with no backup to refer to. I am
> trying to work from references found searching google, my notes were in
> the server. I t
On 12/7/19 12:15 AM, Ed Greshko wrote:
On 2019-12-07 14:45, S.Bob wrote:
I've managed to install Fedora 31 on a new ASUS VivoBook Pro N705FD Notebook.
I've run a full dnf update. Every time I boot it boots to the setup screen (the
one you see at first boot), then the mouse goes away and it ha
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote:
> As an aside, for some weird reason way beyond what makes sense on a
> machine with an inode-based filesystem, the Gnome software tool has a
> problem where it almost always wants to reboot to apply the changes.
> That's an inconvenience th
.
Due to failure of a 3TB Seagate hard drive (DOM 28 April 2019) i am
rebuilding the server again, this time with no backup to refer to. I am
trying to work from references found searching google, my notes were in
the server. I think what I have should work even if not optimal but /am
unable
I update my desktop machine every few days, normally using the Gnome
software tool from the updates tab. This is a fast i7 with a good SSD
and 32GB of memory, and it normally boots to login in about 5 seconds.
As an aside, for some weird reason way beyond what makes sense on a
machine with an
On 12/6/19 3:22 PM, Robert McBroom via users wrote:
On 12/6/19 5:41 PM, Samuel Sieb wrote:
If this is an old install, you might need to update the bootloader
bits that are stored in the mbr. It might too old to support BLS.
That's why if it's not an EFI system, you should run grub2-install to
29 matches
Mail list logo
