Snapin unable to deploy

[Hanz]

--------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 10/22/2015 1:23 PM Client-Info Version: 0.9.5
 10/22/2015 1:23 PM SnapinClient Running...
 10/22/2015 1:23 PM Middleware::Communication URL: http://10.72.3.50/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=B4:99:BA:E9:B8:B8|0A:00:27:00:00:00|CC:52:AF:87:F3:DA||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 10/22/2015 1:23 PM Middleware::Communication Response: Success
 10/22/2015 1:23 PM Middleware::Communication URL: http://10.72.3.50/fog/service/snapins.checkin.php?mac=B4:99:BA:E9:B8:B8|0A:00:27:00:00:00|CC:52:AF:87:F3:DA||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 10/22/2015 1:23 PM Middleware::Communication Unknown Response: **Failed to find snapin file**
------------------------------------------------------------------------------

Fedora 22 SNV5044

Edit: Put log in code block

[ch3i]

@Hanz Hi, can you provide more informations ? like the snapin configuration (a screenshot of web UI)

[Hanz]

I’m afraid there’s not much to see here…The Server config has /opt/fog/snapins as snapin directory, all IP addresses are correct, /opt/fog/snapins on server is (owner-fog:apache chmod to 777) as shown below:

[bcs@fog-server ~]$ cd /opt/fog/snapins
[bcs@fog-server snapins]$ ls -la
total 1324556
drwsrwsr-x 4 fog apache 4096 Oct 22 12:53 .
drwxr-xr-x 6 root root 4096 Oct 21 12:07 …
drwsrwsrwx 2 fog apache 4096 Oct 16 09:25 CA
-rwxrwxrwx 1 fog apache 307200 Oct 16 10:25 ninite.exe
-rwxrwxrwx 1 fog apache 677099526 Oct 16 10:25 OfficeUninstall.exe
-rwxrwxrwx 1 fog apache 6144 Oct 22 12:53 Repin.exe
-rwxrwxrwx 1 fog apache 678899577 Oct 16 10:26 setup_silent.exe
-rwxrwxrwx 1 fog apache 11 Oct 16 10:26 shutdown.bat
drwsrwsrwx 2 fog apache 4096 Oct 16 09:25 ssl
[bcs@fog-server snapins]$

Is there a way to test this manually ?

[Tom Elliott]

@Hanz the code operates as:

Check if the file exists and is readable. It is done via ftp methods so if FTP is not correct this could be presented as well.

Essentially, if either the file doesn’t exist or the file is not readable to the FTP user, it will NOT be able to send the file.

I’d recommend verifying that the nodes that are expected to have the files actually have them, and that their ftp information is correct.

[Hanz]

@Hanz said All snapins are present, and permissions are correct…ftp shows “Index of /” (but nothing there)…Log Viewer is acting as though one of my other nodes is the server. With the Multicast, Scheduler information and so on. While the actual server still shows “no data to read”

[Sebastian Roth]

@Hanz said:

…ftp shows “Index of /” (but nothing there)…

Doesn’t really sound like FTP is working the way it shoudl?!?

[Hanz]

Yeah, Another node has assumed the role of Server after being set up as server first then /opt/fog/.fogsettings changed to accomodate Storage node install.

[Hanz]

As I mentioned before in another thread relating to MYSQL error, All nodes under Log Viewer are showing results as though they’re servers. I’m confused as to why one node has decided to become the server…Where in the database is a node “declared” as the main server node ?

[Tom Elliott]

Master Nodes

[Hanz]

@Tom-Elliott yes, all in their own groups, all show the following under Image/Snapin Replicator, but one node
“[10-23-15 11:15:39 am] * | This is not the master node” on everything except scheduler. My actual server shows “no data to read”

[Tom Elliott]

What I was answering is the systems who “register as servers” are those who are master nodes.

[Hanz]

FOG Configuration.docx

My Server “Fog-Server” is typically listed on this page, and it is not…kernel shows, but that’s it.

[Hanz]

@Tom-Elliott I was given an invalid random ftp password again from installer “/” character will error a lot of things out.

[Tom Elliott]

I don’t follow. The / should not error anything out. We are using single quote so there is no escaping of characters that should be happening.

[Hanz]

Sorry, they’re all master nodes, for each school, in it’s own group…I can only assume that the passwords were correct on all machines. Im 99% sure all nodes were double checked by removing and re-adding to .fogsettings then re-installing, and then fog user passwd updated, then GUI node password verified. The only thing I did was replace the “/” in the password with “1” and doing the afforementioned and it all worked correctly, immediately.

I think it might be worth looking into, since User passwords are mitigated to the eligible characters (could be global)

[Hanz]

This thread can probably be closed now…I appreciate your gentlemen’s help. I think the ftp wasn’t working correctly as @Uncle-Frank mentioned. Snapins are now functioning correctly.

[mp12]

Problem manually solved.
I also had a generated password with a “/”. When I tried to deploy a snapin, it failed with the same error @Hanz described.
A login with an an ftp-client redirected me into the users home directory. I changed “/” into a different character (passwd and GUI) and the ftp-client redirected me into /opt/fog/snapins.
Snapins now work without an error!

[Wayne Workman]

@mp12 so we should not allow passwords with slashes?

[mp12]

@Wayne-Workman maybe someone can reproduce the error, by creating a password with a “/” to eliminate individual mistakes from my site?

[Wayne Workman]

@mp12 Do you think it could be possible that the password was simply set incorrectly somewhere and you resetting it fixed it? I think this is the most plausible reason why it was fixed.