@Chris-Shipley I don’t think you follow, I’ll explain. /images IS a path, and an absolute path too in Linux terms. When you say “/images points to…” well that statement already says where it is. it means /images, which resides on /, which in your case is limited to 50GB. It’s like me saying my car which is currently in the front yard is in the backyard, or my keyboard which is currently on my desk is not on my desk. My /images are not located at /images makes no sense. Just say images, not /images. because /images is a literal path that literally means /images. /images indeed means /images. What actually is setup might be something else, and might not be /images. And if it is something else, your /etc/exports file needs updated to reflect the true path, your Storage Node’s images path and FTP path needs updated to the true path, and the .mntcheck files and dev folder need made in the true path. And your /opt/fog/.fogsettings file needs updated to reflect the true path.
I’ve built a new Fog server with Ubuntu 16.04 and Trunk Version 13
SVN Revision: 5948 (finally) and I have it up and going now, BUT, when I attempt to boot a client to it via PXE
it passes the TFTP connection but times out at the HTTP part.
Here is the kicker — and I know it is probably my fault — the TFTP has the correct IP address tftp://xxx.xxx.xxx.xxx/default.ipxe… ok for example but the HTTP IP address is incorrect and I get http://xxx.xxx.xxx.xxx/fog/service/ipxe/boot.php…connection timed out.
I’ve checked the .fogsettings config and the IP is correct there and I checked the storagenode IP and it is correct. Is there something that I have over looked that has the IP setting for the HTTP?