Fatal Error: Failed to mount nfs volume timed out
-
Is this line absolutely what you’re seeing?
[code]* Mounting File System . . . mount: mounting 192.168.10.250:/ images/dev/ on /images failed: Connection timed out[/code]
-
Yes
[url=“/_imported_xf_attachments/1/1397_IMAG0175.jpg?:”]IMAG0175.jpg[/url]
-
Okay, so there isn’t a space in / and images, that’s good.
Have you ensured firewall is disabled?
[code]sudo service firewalld stop; sudo ufw disable[/code] -
Firewall stopped and disabled on system startup
-
Also, ensure the .mntcheck files are in place:
[code]sudo touch /images/.mntcheck
sudo touch /images/dev/.mntcheck
chmod -R 777 /images[/code] -
apl@Apl-Fog:~$ sudo touch /images/.mntcheck
apl@Apl-Fog:~$ sudo touch /images/dev/.mntcheck
apl@Apl-Fog:~$ chmod -R 777 /images
chmod: changing permissions of ‘/images’: Operation not permitted
chmod: changing permissions of ‘/images/dev’: Operation not permitted
chmod: changing permissions of ‘/images/dev/.mntcheck’: Operation not permitted
chmod: changing permissions of ‘/images/postdownloadscripts’: Operation not permitted
chmod: changing permissions of ‘/images/postdownloadscripts/fog.postdownload’: Operation not permitted
chmod: changing permissions of ‘/images/.mntcheck’: Operation not permittedDont really know how or what to do to resolve that . . . =(
-
I want to thank you for your time and help in resolving this issue.
Unfortunately I have to get going as we are closing at the moment. I wont be back in until Monday.
Again thank you I honestly didn’t expect a response let alone one almost immediately.
-
The chmod commands probably also need the sudo command prepended to it:
[code]sudo chmod -R 777 /images[/code]I don’t know if this will even work though considering, from what I can see, the nfs isn’t even mounting.
-
I do not get a return when using sudo
apl@Apl-Fog:~$ sudo chmod -R 777 /images
[sudo] password for apl: -
You need to type the apl user’s password.
-
I cut that off early. That was just a mistake it just goes back to prompt with out a return.
apl@Apl-Fog:~$ sudo chmod -R 777 /images
[sudo] password for apl:
apl@Apl-Fog:~$ -
that’s fine.
There shouldn’t be a return, if there is it means something has gone wrong.
-
Failed to mount NFS Volume again
-
[ATTACH]1410[/ATTACH]It Hangs on i8042 before moving on to checking in and getting stuck for a few minutes before failing[ATTACH]1409[/ATTACH]
[url=“/_imported_xf_attachments/1/1409_IMAG0177_BURST002.jpg?:”]IMAG0177_BURST002.jpg[/url][url=“/_imported_xf_attachments/1/1410_IMAG0176_BURST001.jpg?:”]IMAG0176_BURST001.jpg[/url]
-
This post is deleted! -
Just out of curiosity I recreated the upload task in the debug mode. When I list the directory from the client machine the /images directory is not visible. Is it a matter of file permissions / sharing ?
-
For give me if this is a stupid question. But I finally got the permissions issue sorted out. I can open the /images folder now.
Here is the stupid part of the question, and believe me I do feel stupid.
Is there supposed to be a visible file named .mntcheck?
As you can see by the screen shot the file is empty…
Again I’m very sorry if this a stupid waste of time.
[url=“/_imported_xf_attachments/1/1419_Screenshot from 2014-10-09 18:57:44.png?:”]Screenshot from 2014-10-09 18:57:44.png[/url]
-
Okay Yes I figured out there is supposed to be a file there from another post I however do not know how to regenerate them. I tried running the installer again but that wasn’t any help
-
I Tried this:
root@Apl-Fog:~# ls -l /images/.mntcheck
-rwxrwxrwx 1 root root 0 Oct 9 19:11 /images/.mntcheck
root@Apl-Fog:~# ls -l /images/dev/.mntcheck
-rwxrwxrwx 1 root root 0 Oct 8 14:03 /images/dev/.mntcheck
root@Apl-Fog:~# touch /images/.mntcheck
root@Apl-Fog:~# chmod 777 /images/.mntcheck
root@Apl-Fog:~# touch /images/dev/.mntcheck
root@Apl-Fog:~# chmod 777 /images/dev/.mntcheckHowever the directory is still empty
[url=“/_imported_xf_attachments/1/1420_Screenshot from 2014-10-09 19:22:01.png?:”]Screenshot from 2014-10-09 19:22:01.png[/url]
-
I’m only going on a limb and guessing you’re fairly new to the linux world?
Files that begin with a . are “hidden” from the filesystem. This would be why you’re seeing “contents: nothing”.
When you’re running the chmod commands I’d recommend using with the -R argument.
The reason is because chmod 777 <file/foldername> only affects the individual item.
chmod -R 777 <folder> means to set the persmissions recursively which is what you need.
