FOG Client 0.11.3 - no config.json file
-
The fog client thinks my config.json file doesn’t exist, but it does. I don’t know what I’m doing wrong. I’m trying to deploy SmartNotebook 2016 as MSI + MST, and I do have an MST file in there, too.
------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 7/15/2016 1:13 PM Client-Info Client Version: 0.11.3 7/15/2016 1:13 PM Client-Info Client OS: Windows 7/15/2016 1:13 PM Client-Info Server Version: 8609 7/15/2016 1:13 PM Middleware::Response Success 7/15/2016 1:13 PM SnapinClient Snapin Found: 7/15/2016 1:13 PM SnapinClient ID: 4908 7/15/2016 1:13 PM SnapinClient Name: SmartNotebook2016 7/15/2016 1:13 PM SnapinClient Created: 2016-07-15 13:12:50 7/15/2016 1:13 PM SnapinClient Action: 7/15/2016 1:13 PM SnapinClient Hide: False 7/15/2016 1:13 PM SnapinClient TimeOut: 0 7/15/2016 1:13 PM SnapinClient RunWith: 7/15/2016 1:13 PM SnapinClient RunWithArgs: 7/15/2016 1:13 PM SnapinClient File: SmartNotebook2016.zip 7/15/2016 1:13 PM SnapinClient Args: 7/15/2016 1:13 PM Middleware::Communication Download: http://10.2.1.11/fog/service/snapins.file.php?mac=90:B1:1C:98:03:8C||00:00:00:00:00:00:00:E0&taskid=4908 7/15/2016 1:13 PM SnapinClient C:\Program Files (x86)\FOG\tmp\SmartNotebook2016.zip 7/15/2016 1:13 PM SnapinClient Processing SnapinPack SmartNotebook2016.zip 7/15/2016 1:13 PM SnapinClient Extracting SnapinPack 7/15/2016 1:13 PM SnapinClient Reading SnapinPack configuration 7/15/2016 1:13 PM SnapinClient ERROR: Invalid snapin object, no config.json 7/15/2016 1:13 PM Middleware::Communication URL: http://10.2.1.11/fog/service/snapins.checkin.php?taskid=4908&exitcode=-1&mac=90:B1:1C:98:03:8C||00:00:00:00:00:00:00:E0&newService&json ------------------------------------------------------------------------------
-
I would almost think it’s not downloading the .zip file from the fog server at all. I kept a close eye on task manager’s network performance. You would think a 2+ GB zip file would cause a significant spike for a minute. It never did.
-
I could be wrong but I think the config.json is to go into the snapin zip file, not the config.json IS the snapin.
-
@Tom-Elliott It’s in the zip file, in the root of the zip file. Look at the screenshot above.
-
SO … what do you mean? If you see the file in there, what’s not working?
-
@Tom-Elliott The above picture is the innards of the zip file that I uploaded - the fog client doesn’t appear to be downloading anything at all. The log is attached.
-
@Wayne-Workman I think my confusion is that the zip file should already contain what’s needed. So if the client has the zip the file has already been downloaded. Errors after that I’m not aware of sorry.
-
@Tom-Elliott The client doesn’t have the zip file.
I built the snapin on the computer in the screen shot. The zip file is on my desktop. I opened it to show that it does have a config.json file there.
The client did not download the .zip file. It’s about 2.5GB - I would have saw that on this computer’s network activity.
-
@Wayne-Workman is your FOG Server 32 or 64 bit?
-
@Joe-Schmitt at work, 64 bit. It has 4 cores assigned, running Fedora 21.
-
@Wayne-Workman I suspect this is a filesize issue, though I don’t know for sure.
I’ve updated the codebase to be more agnostic toward architecture but I don’t know if this will help for this particular issue.
It certains does seem odd of a problem. Maybe you can try to download the file the same way the client attempts? Does require a bit of work to get right but should work once we get done.
-
@Tom-Elliott I would just use the link in the log right? I guess the ID would need added by 1 after a failed deployment and redeployment, with the client turned off.
-
Figured out why there was no spike in network traffic, the file was zero size.
FYI, I ran thislscommand AFTER I went into the smart notebook snapin, clicked delete, and checked the box to delete files as well. So FOG 1.3.0 RC1 isn’t deleting snapins. I don’t see anything relevant in the apache error logs.[root@mb-fog snapins]# ls -laht /opt/fog/snapins/ total 395M drwxrwxr-x. 3 fog apache 4.0K Jul 19 12:21 . drwxr-xr-x. 5 root root 4.0K Jul 19 07:17 .. -rwxrwxr-x. 1 fog apache 0 Jul 15 13:01 Smart Notebook 2016.zip -rwxrwxr-x. 1 fog apache 51 Jul 12 07:13 Set_Timezone.bat -rwxrwxr-x. 1 fog apache 51M Jul 6 09:56 googlechromestandaloneenterprise64.msi -rwxrwxr-x. 1 fog apache 5.7M Jun 30 12:26 MerakiSM-Agent-mb.msi -rwxrwxr-x. 1 fog apache 254M Jun 30 09:17 avast-install-mb-domain.exe -rwxrwxr-x. 1 fog apache 2.8K May 27 10:09 Apply-Default-Profile-args.bat -rwxrwxr-x. 1 fog apache 2.9K May 18 12:27 DeployProfile.bat -rwxrwxr-x. 1 fog apache 45M May 6 07:40 googlechromestandaloneenterprise.msi -rwxrwxr-x. 1 fog apache 21M Mar 15 07:48 install_flash_player_21_plugin.msi -rwxrwxr-x. 1 fog apache 20M Mar 15 07:32 install_flash_player_21_active_x.msi drwxrwxr-x. 3 fog apache 4.0K Feb 25 08:44 ssl [root@mb-fog snapins]#I wonder if it’s due to the space in the filename?
-
I’m attempting to re-do the snapin now.
-
Don’t lie.
I just tested running 1.3.0-RC-1 deleting snapins works fine to remove files.
-
@Tom-Elliott It didn’t delete it. Note the space in the file name.
-
Well, this is highly interesting. I just re-built the snapin pack to use the new format, set it up in the GUI, and clicked add. I watched the percent count up in the bottom left of Chrome for the upload. After it got done, this is all that appears in
/opt/fog/snapins[root@mb-fog snapins]# ls -la total 317304 drwxrwxr-x. 3 fog apache 4096 Jul 19 12:46 . drwxr-xr-x. 5 root root 4096 Jul 19 07:17 .. -rwxrwxr-x. 1 fog apache 266245249 Jun 30 09:17 avast-install-mb-domain.exe -rwxrwxr-x. 1 fog apache 52764672 Jul 6 09:56 googlechromestandaloneenterprise64.msi -rwxrwxr-x. 1 fog apache 5885952 Jun 30 12:26 MerakiSM-Agent-mb.msi -rwxrwxr-x. 1 fog apache 51 Jul 12 07:13 Set_Timezone.bat -rwxr-xr-x. 1 fog fog 0 Jul 19 12:46 SmartNotebook2016.zip drwxrwxr-x. 3 fog apache 4096 Feb 25 08:44 ssl [root@mb-fog snapins]# -
Just confirmed that my server, Fedora 21, is 64 bit:
[root@mb-fog snapins]# arch x86_64 [root@mb-fog snapins]# -
Found some ftp logs in /var/log, they also show the 0 file size. Still digging…
cat /var/log/xferlog-20160718Fri Jul 15 11:25:32 2016 5 10.2.1.11 266245249 /opt/fog/snapins/avast-install-mb-domain.exe b _ o r fog ftp 0 * c Fri Jul 15 11:25:34 2016 11 10.2.1.11 266245249 /opt/fog/snapins/avast-install-mb-domain.exe b _ o r fog ftp 0 * c Fri Jul 15 11:26:03 2016 3 10.2.1.11 266245249 /opt/fog/snapins/avast-install-mb-domain.exe b _ o r fog ftp 0 * c Fri Jul 15 11:27:05 2016 1 10.2.1.11 5885952 /opt/fog/snapins/MerakiSM-Agent-mb.msi b _ o r fog ftp 0 * c Fri Jul 15 11:27:11 2016 3 10.2.1.11 5885952 /opt/fog/snapins/MerakiSM-Agent-mb.msi b _ o r fog ftp 0 * c Fri Jul 15 11:27:41 2016 3 10.2.1.11 5885952 /opt/fog/snapins/MerakiSM-Agent-mb.msi b _ o r fog ftp 0 * c Fri Jul 15 13:01:11 2016 1 10.2.1.11 0 /opt/fog/snapins/Smart_Notebook_2016.zip b _ i r fog ftp 0 * c Fri Jul 15 13:03:16 2016 1 10.2.1.11 0 /opt/fog/snapins/Smart_Notebook_2016.zip b _ o r fog ftp 0 * c Fri Jul 15 13:12:31 2016 1 10.2.1.11 0 /opt/fog/snapins/SmartNotebook2016.zip b _ i r fog ftp 0 * c Fri Jul 15 13:13:59 2016 1 10.2.1.11 0 /opt/fog/snapins/SmartNotebook2016.zip b _ o r fog ftp 0 * c Fri Jul 15 14:38:16 2016 6 10.2.1.11 266245249 /opt/fog/snapins/avast-install-mb-domain.exe b _ o r fog ftp 0 * c Fri Jul 15 14:39:48 2016 1 10.2.1.11 5885952 /opt/fog/snapins/MerakiSM-Agent-mb.msi b _ o r fog ftp 0 * c Fri Jul 15 15:04:09 2016 3 10.2.1.11 266245249 /opt/fog/snapins/avast-install-mb-domain.exe b _ o r fog ftp 0 * c Fri Jul 15 15:06:05 2016 1 10.2.1.11 5885952 /opt/fog/snapins/MerakiSM-Agent-mb.msi b _ o r fog ftp 0 * c -
i had an issue similar if not identical a while back. it went away after updating to a newer build, so i assumed it was a bug that was fixed. creating a snapin would create a 0 length file with the name, but obviously didn’t actually upload the file to the server. i don’t remember much more details than that, it was a week or two ago.