Location Plugin - ID Must Be Set To Edit Error

[tedd77]

@george1421
yes
-rw-r–r-- 1 www-data www-data 9327 Nov 19 21:42 plugin.class.php

[tedd77]

@george1421

Running Version 1.4.4
SVN Revision: 6077

[tedd77]

@george1421 Any other suggestions would be appreciated. I am bit stuck at this point as my storage is very small on the FOG server.

[george1421]

@tedd77 When you try to use the plugin and FOG throws the ID must be set to edit error, please inspect the apache error log to see if its posting something different than the OPs.

Also what plugin are you trying to load? I have a feeling that we might need to get the developers involved here, because replacing that file mentioned below fixes the issue.

[tedd77]

@george1421
in apache2
error.log is empty ( I cleared it before I attempted to create the location)
access.log is empty (I cleared it before I attempted to create the location)
other_vhosts_access.log has many entries but no errors in there.

The plugin is the Location Management , I need this in order to define a NAS as storage location for my images.

[george1421]

@tedd77 How do you feel about moving to the dev branch? (1.5.0RC10) understand that this is a one way street since 1.5.0 has the new gui interface?

@developers do you have any idea on this issue? The patch doesn’t seem to address the issue.

[Tom Elliott]

@george1421 is the plugin being removed and readded

[Sebastian Roth]

@tedd77 The actual issue is that when you install the plugin in FOG 1.4.4 the database table for it is not being created. This should be corrected when using the newer version of plugin.class.php. So to figure out why it doesn’t work in your case I think it’s a good start to see if the table is there or not.

shell> mysql -u root -p
Enter password:
...
mysql> use fog;
...
mysql> SHOW TABLES WHERE tables_in_fog LIKE '%location%';
...

Post a screenshot here.

[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.