Location Plugin - ID Must Be Set To Edit Error

[tedd77]

@sebastian-roth @george1421 @Tom-Elliott
Indeed the table does not seem to be created.

How to go about that problem ?
thank you in advance

[george1421]

@tedd77 Well this is a bit strange.

can you run the following command for us.
md5sum /var/www/fog/lib/fog/plugin.class.php

It should produce an output that looks like this:

# md5sum  plugin.class.php
3834190099dd166ba0e6943ae95fa5f7  plugin.class.php

Please compare the above md5 hash to what you have installed.

[tedd77]

@tom-elliott @george1421

First please accept my apologies for the inconvenience I may have caused.
I discovered that I was writing the file in the wrong directory.
In fact I have 2 fog folders
/var/www/fog/lib/fog
/var/www/html/fog/lib/fog

The correct one is the second in the above list. I was writing to the first unfortunately and nothing was working for me.
Now after I dug properly things are working for me and I confirm the patch is perfect.

@george1421 I still do not mind to try the dev version, could you please send me the instructions ?

[tedd77]

@george1421

and also

They are 100% ok with your hash

[george1421]

@tedd77 Well since you fount the issue, there is no need to upgrade to the dev branch unless you really want to.

Here are the steps.

sudo -i
git clone https://github.com/FOGProject/fogproject.git /root/fogproject
cd /root/fogproject
git checkout dev-branch
cd bin
./installfog.sh

Now when 1.5.0 is released all you need to do is this.

sudo -i
cd /root/fogproject
git checkout master
git pull
cd bin
./installfog.sh

The checkout dev-branch and checkout master are the commands to switch the installer between to the installers.

[Tom Elliott]

@george1421 I’d also recommend, removing the /var/www/fog and /var/www/html/fog directories, and rerunning the installation.

In older FOG Versions, FOG would try to detect the location based on the OS, but since debian and ubuntu have now started using the /var/www/html path similar to redhat basis, on upgrades it was possible to have two separate instances of FOG installed, with one being the “primary”.

The installer does try to create a softlink to /var/www/fog from /var/www/html/fog in the case the /var/www/fog is still the default location. Removing both and reinstalling should make this so no matter which document root it’s using, it will work without issue.

[tedd77]

@tom-elliott @george1421
I will re-install 2 new ubuntu servers one on Dev and one on the current release.

Still having hard time figuring out how to make the FOG writes the images on a separate NAS server.
I looked onto youtube https://www.bing.com/videos/search?q=fog+location+management+tutorial&&view=detail&mid=ABF5CCD8147F2039673EABF5CCD8147F2039673E&FORM=VRDGAR
with no luck.
I created 1 extra group , 1 new storage node, as well as 2 locations
whenever I divert from the default group the machine fails to create an image however if I keep on the default group it works but
the image will be stored on the FOG server itself.

[george1421]

@tedd77 Storage nodes can only send images (normally). You can only send captured images to the master node of each storage group.

[tedd77]

@george1421
Thank you , what is the best method to capture images then to a large storage nas?
My Fog server is residing on a VM with limited storage .
The aim is to have a NAS on the same network to capture and distribute images. The Fog server will be the leader (orchestra leader) of all operations.

[george1421]

@tedd77 do you have the nas setup as a FOG storage node?

[tedd77]

@george1421

Yes I defined my nas as a storage node.
I created a user called fog , and a folder called fog on the nas. Given full rights to that user.
On the FOG server I created a storage node , pointed it to the NAS server.

[george1421]

@tedd77 Who makes your NAS. Because there is a setup required to turn a NAS into a storage node.

[tedd77]

@george1421
QNAP 431X with 10G interface

[george1421]

@tedd77 I’m sure someone wrote a how to for the QNAP. I did write one for a synology nas. Let me grab that one (and look for the qnap)

edit
https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

edit2 (jackpot)
https://forums.fogproject.org/topic/10973/add-a-nas-qnap-ts-231-as-a-storage-node-fog-v1-4

[george1421]

A fog storage node needs

1. NFS (set up a certain way)
2. FTP (to access the nfs share)
3. TFTP (if you want to pxe boot your clients)

Then when FOG is accepting that storage node and you can deploy, then switch and make the NAS the master node of its storage group. Its pretty easy to setup if you have only one site, a FOG server and a NAS. Its a little bit more complicated if you have multiple storage nodes across several sites. You can set that up, it just requires smoke and mirrors.

[tedd77]

@george1421
Very good tutorial , settings were done to the qnap.
Now i can see that Fog started pointing to my QNAP and the Fog attempts to write but fails after few seconds.
see screen capture

[george1421]

@tedd77 you need to ensure that the user account you created on the qnap has full rights to that directory structure, as well /share/images/dev needs to be writable by a root user. Not THE root user, but A root user. If you look at my tutorial for the synology, you will see I needed to enable extra rights on that nfs share. I can’t speak for the qnap tutorial since I did not write it. I did write one for MS Windows 2012 and had to set similar rights.

[tedd77]

@george1421
It is working now however every time I reboot the nas I have to execute the following from FOG server

mount -t nfs <nas_ip>:/share/images /mnt
mkdir /mnt/dev
touch /mnt/.mntcheck
umount /mnt

mount -t nfs <nas_ip>:/share/images/dev /mnt
touch /mnt/.mntcheck
umount /mnt

[george1421]

@tedd77 Um, why are you doing that? The NAS and the FOG server should be a stand alone servers. You should not need to cross mount anything.

[george1421]

@george1421 OK looking at what you are doing closer (and not assuming this time), it appears the NAS is not keeping the hidden files .mntcheck between reboots? And you need to recreate them every NAS reboot. That is pretty strange.