On 07/06/17 07:10, Amadeus W.M. wrote:
> Tried that and it worked and it also worked when I restored the original
> exportfs and nfs files. The reboot took a LONG time - stuck at shutting
> down some nfs processes (can't remember which, lockd maybe).
>
> Everything seems to be back to normal
On Tue, 04 Jul 2017 14:45:19 +0800, Ed Greshko wrote:
> On 07/03/17 12:44, Amadeus W.M. wrote:
>> I need a fix for my problem.
>
>
> I have one thing for you to try. As root
>
> cd /etc
>
> cp exports exports-orig
>
> cat /dev/null > exports
>
> cd sysconfig
>
> cp nfs nfs-orig
>
>
Allegedly, on or about 03 July 2017, Tom Horsley sent:
> Here's something to check: Some recent versions
> of nfs fail utterly if they can't lookup the IP
> address of even 1 system mentioned in the exports
> file. You'd think ignoring that 1 would be nicer,
> but it refuses to do anything
On 07/03/17 12:44, Amadeus W.M. wrote:
> I need a fix for my problem.
I have one thing for you to try. As root
cd /etc
cp exports exports-orig
cat /dev/null > exports
cd sysconfig
cp nfs nfs-orig
cat /dev/null > nfs
reboot
After reboot check to the status of nfs-server
systemctl
On 07/03/17 23:24, Tom Horsley wrote:
> Here's something to check: Some recent versions
> of nfs fail utterly if they can't lookup the IP
> address of even 1 system mentioned in the exports
> file. You'd think ignoring that 1 would be nicer,
> but it refuses to do anything instead.
Well, that
On 07/04/17 02:30, Tom H wrote:
> [root@localhost ~]# cat /etc/sysconfig/nfs
> RPCNFSDARGS="--udp"
>
>
> [root@localhost ~]# systemctl restart nfs-server.service
> Job for nfs-server.service canceled.
>
>
> [root@localhost ~]# systemctl status nfs-server.service
> ● nfs-server.service - NFS server
I deleted the new "/etc/nfs.conf". With
# cat /etc/sysconfig/nfs
RPCNFSDARGS="--udp"
I get
[root@localhost ~]# rpcinfo -p
program vers proto port service
104 tcp111 portmapper
103 tcp111 portmapper
102 tcp111 portmapper
10
On Mon, Jul 3, 2017 at 8:19 AM, Amadeus W.M. wrote:
>
> Thank you Tom and Ed for taking the time to help. My F25 was upgraded
> from F24, where nfs was working perfectly (as well as in all versions
> before that). Here is my configuration:
You're welcome.
All your config
Here's something to check: Some recent versions
of nfs fail utterly if they can't lookup the IP
address of even 1 system mentioned in the exports
file. You'd think ignoring that 1 would be nicer,
but it refuses to do anything instead.
___
users mailing
On Mon, Jul 3, 2017 at 6:02 AM, Ed Greshko wrote:
> On 07/03/17 17:50, Tom H wrote:
>>
>> "rpcinfog -p" or "rpcinfo -s" will output the nfs versions if you
>> don't have "nmap" installed.
>
> Thanks for the reminder about rpcinfo.
>
> Of course if it is rpc.nfsd not
On 07/03/17 20:19, Amadeus W.M. wrote:
> Thank you Tom and Ed for taking the time to help. My F25 was upgraded
> from F24, where nfs was working perfectly (as well as in all versions
> before that). Here is my configuration:
No problem. I enjoy a challenge.
> $ cat /etc/fedora-release
>
Thank you Tom and Ed for taking the time to help. My F25 was upgraded
from F24, where nfs was working perfectly (as well as in all versions
before that). Here is my configuration:
$ cat /etc/fedora-release
Fedora release 25 (Twenty Five)
$ rpm -q nfs-utils
nfs-utils-2.1.1-5.rc3.fc25.x86_64
On 07/03/17 17:50, Tom H wrote:
> "rpcinfog -p" or "rpcinfo -s" will output the nfs versions if you
> don't have "nmap" installed.
Thanks for the reminder about rpcinfo.
Of course if it is rpc.nfsd not getting started the info it would return would
be
missing nfs info. :-)
--
Fedora Users
On Mon, Jul 3, 2017 at 1:47 AM, Ed Greshko wrote:
>
> PORT STATE SERVICE VERSION
> 21/tcp open ftp vsftpd 3.0.3
> | ftp-anon: Anonymous FTP login allowed (FTP code 230)
> |_drwxr-xr-x1 00 0 Dec 01 2016 pub
> 22/tcp open
On 07/03/17 12:44, Amadeus W.M. wrote:
> I need a fix for my problem.
>
Oh, and I just restarted the nfs server and this was the journal recording
[root@f25f ~]# journalctl -b -0 | grep -i nfs | grep 14:52
Jul 03 14:52:05 f25f.greshko.com systemd[1]: Stopping NFS server and services...
Jul
On 07/03/17 12:44, Amadeus W.M. wrote:
> Yes, I know it should work, but I need a fix for my problem.
Oh, I'm sorry. When you said "I mean, really, nfs not working on a major
distribution?" I thought you were thinking it isn't working at all for anyone.
> I wonder if in my case it's some stale
Yes, I know it should work, but I need a fix for my problem.
I wonder if in my case it's some stale configuration from previous Fedora
versions, because I've been doing upgrades (as opposed to new installs)
for a long time. I imagine you installed F25 anew on the VM, right?
How do I even
On 07/02/17 08:00, Amadeus W.M. wrote:
> Upgraded to F25 a couple of months ago and nfs stopped working. I was
> hoping there would be a fix by now, but the problem persists. I had nfs
> running on F24 and earlier with no issues, now it won't even start. Both
>
> systemctl start
Upgraded to F25 a couple of months ago and nfs stopped working. I was
hoping there would be a fix by now, but the problem persists. I had nfs
running on F24 and earlier with no issues, now it won't even start. Both
systemctl start nfs-server.service
systemctl stop nfs-server.service
hang. If
19 matches
Mail list logo