Snapins Issue : Hash does not match

[Sebastian Roth]

@DARUN974 Can you disable the Windows proxy setting for testing. Manually restart the FOGService (Windows service management) after disabling proxy and check fog.log again.

As well you might want to take a look at the 1 kilo byte file in FOG\tmp\ folder using a proper editor like Notepad++. I am wondering if it looks like binary content or maybe we find readable text as hint on why this fails.

[DARUN974]

I have disabled the Windows proxy setting. Manually restarted the FOGService.
I deleted the different snapins and created a new one.
It’s the same error in the fog.log file.
This is what the file contained in FOG \ tmp contains:
“#! er: Could not read snapin file”

[Sebastian Roth]

@darun974 said in Snapins Issue : Hash does not match:

“#! er: Could not read snapin file”

Ahh, well that’s a pointer to what’s going wrong. This messages comes from the FOG server as it’s not able to open that file for reading the binary data (code ref).

First check the path set in FOG Configuration -> FOG Settings -> FOG Client - Snapins -> SNAPINDIR to make sure this is pointing to the right directory. Should be /opt/fog/snapins/.

[DARUN974]

Hello,
The path defined in FOG Configuration -> FOG Settings -> FOG Client - Snapins -> is: / opt / fog / snapins /.
The rights to the Setup_SimpleStickyNotes.exe file are complete for everyone.

[Sebastian Roth]

@Tom-Elliott Have you seen this happen before? I have not tested snapins myself in a long time but I guess we would have heard about it if this is a general issue with FOG 1.5.9.

[Tom Elliott]

@sebastian-roth I would agree that if this were a common issue, some of our users who use Snapins a lot (@Greg-Plamondon) would have likely noted it for us already.

is /opt/fog/snapins a link to another directory on your FOG Server? Maybe to an NFS or CIFS mounted share? (ls -al /opt/fog should be sufficient to at least tell us if it’s local or linked at least.)

When the snapin is read, it’s read in binary mode. If, for some reason, the web service cannot read it (which we can see from /opt/fog/snapins being owned by fogproject:fogproject) it will give this issue. This should be fixed if you change the permissions from fogproject:fogproject to fogproject:www-data chown -R fogproject:www-data /opt/fog/snapins I would think.

[Sebastian Roth]

@Tom-Elliott Good point about maybe /opt/fog/snapins/ being on a different filesystem.
Don’t think it’s an ownership/access issue as rights are set to 777, so any user would be able to read that file. Same for the directory.

@DARUN974 Beside Tom’s command, please also run mount | grep opt and post output here.

[DARUN974]

Hello
FOG is installed on the root
There is no link.
Just a link for images.

I changed the permissions of fogproject: fogproject to fogproject: www-data
But still the same error.

Result of the command: mount | grep opt:

[Sebastian Roth]

@DARUN974 I am at a loss on why it runs into this problem. Just doesn’t make sense to me at the moment.

@testers Anyone using snapins with FOG 1.5.9 who can confirm this should be working??

[DARUN974]

Hello,
Thanks for your help.
On my side, I continue to check my network configuration: proxy …
I am in national education, we use the different modules of the EOLE distribution for our systems.
The installation of the FOG server was done using an eole_fog package provided by EOLE

[Sebastian Roth]

@darun974 said in Snapins Issue : Hash does not match:

The installation of the FOG server was done using an eole_fog package provided by EOLE

Well that is interesting. I have never heard of EOLE. @Tom-Elliott Do you know about this?

https://dev-eole.ac-dijon.fr/projects/eole-fog

Not sure if their setup process might have caused this. When I find a bit of time I might take a closer look at this. @DARUN974 Are you in contact with the developers of EOLE?

[Tom Elliott]

@sebastian-roth I’ve never heard of this either.

[DARUN974]

@sebastian-roth said in Snapins Issue : Hash does not match:

@DARUN974 Are you in contact with the developers of EOLE?

Hello,
I am not “really” in contact with the EOLE developers.
We use a forum to ask our questions: scribe@listeseole.ac-dijon.fr
I will see if other users have encountered this problem.

[sborgne]

Bonjour,

J’ai rencontré le même problème, la configuration de php est en cause.

Vérifiez dans le fichier php.ini que la variable allow_url_fopen est à On.
Redémarrez apache si vous faites la modification de Off à On, puis effectuez des tests.

Sous EOLE, lors de la mise à jour automatique, le “reconfigure” va écraser la configuration php et remettre la variable à Off, il faut créer un patch creole pour péréniser la configuration allow_url_fopen=On.

Le problème n’est donc pas lié à fog mais à EOLE.

MP si vous voulez sur stephane DOT borgne AT savoie DOT fr

Cordialement,

Hi,

It’s a php misconfiguration specific recurently applied by EOLE distribution update process.

Issue is not from fog.

Regards,

Stéphane

[Sebastian Roth]

@sborgne Oh, that sounds reasonable! Thanks heaps for posting here.

@DARUN974 Definitely take a look at the php.ini settings as suggested!

[DARUN974]

Hello,
Sorry for the delay, I just noticed the change made.
I can’t wait to try this tomorrow.
I will come back to you.

@sborgne Bonjour, Merci beaucoup . Je teste cela demain.

Regards.