Have to image 8 labs by Monday

[Tom Elliott]

try removing rpcbind and nfs-kernel-server
then try to have apt install them

I don’t know what else to work on then.

[Tyler Wright]

Yeah, I remove and then try to install them; I get this:

nfs-kernel -server: Depends: nfs-common (>= 1:1.0.1-1) but it is not going to be installed

I then try to install nfs-common and that conflicts with portmap.

I’m lost. I’ve even tries reinstalling Fog itself with no luck.

[Tom Elliott]

try this:

apt-get remove portmap;
apt-get install nfs-kernel-server nfs-common

[Tom Elliott]

apt-get install apache2 php5 php5-gd php5-cli php5-mysql php5-curl mysql-server mysql-client isc-dhcp-server tftpd-hpa tftp-hpa nfs-kernel-server vsftpd net-tools wget xinetd sysv-rc-conf tar gzip build-essential cpp gcc g++ m4 htmldoc perl libcrypt-passwdmd5-perl lftp openssh-server php-gettext clamav-freshclam rpcbind nfs-common

[Tyler Wright]

This post is deleted!

[Tyler Wright]

I get nfs-common: Depends: portmap (> 6.0.0-1ubutnu2.1) E: Broken packages when I try to install all of those things.

[Tom Elliott]

Looking into this further, try removing rpcbind and just:

apt-get install nfs-common nfs-kernel-server portmap

[Tyler Wright]

It gets stuck at “Starting NFS kernel daemon.”

Before that, it says:

exportfs: /etc/exports [1]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export “:/images" exportfs: /etc/exports [2]: Neither ‘subtree_check’ or ‘no_subtree_check’ specified for export ":/images/dev”

[Tyler Wright]

I just added another storage node and when I PXE boot, it attempts to mount it but still ends up with the RPC connection refused error.

[Tom Elliott]

Looked up the issue and found a page with similar issues as yours:

[url]http://fogproject.org/forum/threads/fog-32-on-ubuntu-11-10-unable-to-upload-image.852/[/url]

It sounds like nfs-kernel-server is having issue actually mounting. One issue I ran into on my setup was RPC, but I’m running centos which is redhat based. I just installed rpcbind and had to add fsid=1 to images and fsid=2 to images/dev so my exports looks like:

/images *(rw,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2)

[Tyler Wright]

Alright. I’ll try to modify my exports file in a second.

What’s interesting is that the NFS share mounts perfectly fine through an NFS client on Windows. I don’t know why PXE can’t get to it.

[Tom Elliott]

It isn’t pxe unable to mount it at that point. It’s the kernel. bzImage is that kernel. What version are you using? Try upgrading and see if that’ll help maybe?

[Tyler Wright]

I upgraded this morning to the latest version of the kernel.

[Tyler Wright]

I think that we’re close to figuring this out!

I just tried to upload an image from a machine on the same subnet as the Fog and DHCP server and it worked!

Any ideas on why it’s not having my machines on other subnets route to the NFS share correctly?

[Tom Elliott]

Maybe check firewall on the fog system or network.

[Tyler Wright]

There’s no internal firewall on the network and the Ubuntu Server that Fog is running off of has its firewall disabled.

I’m thinking about when I first installed Fog. It asks me what my router’s IP address was and I set it to the IP of my Windows DHCP Server.

[Tom Elliott]

Maybe see if you can change the router to the gateway that all the subnet’s can communicate with each other across. This would typically be the DHCP server itself which, as far as I can tell, works perfectly fine. Maybe have your switches forward the nfs ports to your fog server. 111 and 2049 are the typical ports.

Other than that, I don’t know. Maybe setup dhcp for tftp to use the same LAN as your fog server?

[Tom Elliott]

Just a track for understanding,

All systems are communicating via PXE and able to load bzImage and init.gz to attempt to start. After that, when it tries to connect to the NFS <fogserverip>:/images/dev and systems not within the same subnet cannot connect?

As your systems within the same subnet of the fogserver communicate properly, it isn’t a storage node user configuration issue, as far as I can tell. It also wouldn’t be a storage_ftp user issue either as you’ve already uploaded the images.

The only thing it seems like, is the internal network can’t route through to the fog server’s ip address to connect to the nfs share. This is why I would suggest port forwarding, for each of the switches in the path, to point directly to the fog server.

[Tyler Wright]

That’s something that I’ll look into! I’ll see what I can do tomorrow morning and hopefully, I’ll be able to get it working. I think that you’re right though. I’ll keep you posted on how it goes tomorrow!

[Tyler Wright]

I GOT IT!

I read this post earlier today and didn’t think much of it. Turns out, it fixed my issue.

I had to edit my.conf and change bind-address to my Fog server IP instead of 127.0.0.1.

Thank you so much, Tom! I couldn’t have fixed it without your support. I greatly appreciate it!