SOLVED images on separate nfs server
- FOG Version: 1.3.4
- OS: Ubuntu 14.04
I have a fog server x.x.x.59 and an NFS/FTP server x.x.x.155 where i store the images.
When I define the IP of the DefaultStoreageNode as x.x.x.59 the client boots, creates the image, updates the database and fails connecting to the NFS server. It tries x.x.x.59:/fog/dev, but it should x.x.x.155:/fog/dev
When I define the IP of the DefaultStorageNode as x.x.x.155 the client boots, creates the image, and fails updating the database. It tries probably tries x.x.x.155, which is not the database server, it’s the NFS server.
How can I work around this problem? I think when updating the database, fog should always use x.x.x.59 like it was in fog 1.2.0
Thanks for your help and suggestions to solve this problem.
@george1421 Thanks for clarifying. The ftp server was the problem. The “Updating Database” confused me into thinking, the fog database fails to update.
Tom Elliott last edited by
@MarkusK Again, what is your nfs device?
That device must have FTP service enabled or you will get a database update error. The error is a bit misleading. Since FOG moves the captured image from /images/dev/<mac_address> to /images/<image_name> just before it updates the database in the fog server.
@george1421 The nfs server is not the problem, it works. The problem is, that the IP for the database server (fog server?) changes, when I change the IP of the DefaultStorageNode.
What manufacturer is device x.x.x.155?
You will need these shares on your nfs/ftp server /images and /images/dev. They need to be shared via nfs and have ftp access to move the images from /images/dev to /images on the storage node.
If the remote ftp/nfs server is a nas like synology you can add this device as a storage node and then direct the images to that storage node.