Deploy all snapins is confused
-
This is the only snapin that isn’t working? Snapins are designed for executables, I’m not sure how they would work with a non-executable.
What you might be looking for are SnapinPacks. You can deploy a batch file along-side this text file, to copy the file where it needs to go. You can find some details here:
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks -
@Wayne-Workman said in Deploy all snapins is confused:
This is the only snapin that isn’t working? Snapins are designed for executables, I’m not sure how they would work with a non-executable.
What you might be looking for are SnapinPacks. You can deploy a batch file along-side this text file, to copy the file where it needs to go. You can find some details here:
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacksNo I saw the same issue with several executable snapins.
And deploying alone is ok.
For a long time, I deployed msi, bat, copy files on client, etc …And yes I have seen this new feature, snapin pack, wich is wonderfull.
The first time I saw this issue was with snapin packBut I could try again to verify with only snapin pack
-
@Claude-Girard Can you post a screen shot of the snapins for “All Snapins” task? There should be a single entry in Task Management, but several under “active snapin tasks”.
-
@Wayne-Workman said in Deploy all snapins is confused:
@Claude-Girard Can you post a screen shot of the snapins for “All Snapins” task? There should be a single entry in Task Management, but several under “active snapin tasks”.
Active tasks:
Active snapin tasks:
For the first one like I said before, my txt file is downloaded but is rename like the exe file of the second snapin.
I opened it with note pad and it’ my real txt file, not an exe one.I’ll try to invert them and I’ll tall you what happen
-
So if I change order for my snapins:
Now my exe one is the first
But on client when deployed:
The name of the downloaded file is the one for the text file, but with size of my exe one !!!
Can I have a database problem if no other user has this problem ?
-
I’m pretty certain this is a bug. Passing it off to @Tom-Elliott.
Please work with him and answer any questions he asks. -
@Claude-Girard Can you provide steps to - from scratch - replicate the issue? We’re trying to but haven’t succeeded. We don’t have your snapins, so we need replication steps from scratch.
-
@Wayne-Workman said in Deploy all snapins is confused:
@Claude-Girard Can you provide steps to - from scratch - replicate the issue? We’re trying to but haven’t succeeded. We don’t have your snapins, so we need replication steps from scratch.
Yes I’ll try tomorrow.
I say try because it’s difficult to reproduce from scratch, it’s not really clear, I tried several combination, but with no success for finding at least one rule I can repeat.If necessary I can share my files and snapins config
But I will try with no snapin at all, and adding some of them.
In my last try, removing one of them solved the issue, but I can’t affirm that THIS snapin was the causeSo after a good night, maybe …
-
@Claude-Girard said in Deploy all snapins is confused:
If necessary I can share my files and snapins config
If this is what you choose, you can do a export of all snapins from Snapin Management, it’s in the left menu. You could email this export and the snapin files to me or @Tom-Elliott. Don’t post your snapin files on the forums. Contact us via forums messaging for our email addresses (top right, talk bubble).
-
I can confirm I have this exact same problem. After imaging a computer I deployed all snap-ins and the process failed on the first snap-in saying that the hash does not match. If I install a single snap-in, it works fine.
-
@Brian-David said in Deploy all snapins is confused:
I can confirm I have this exact same problem. After imaging a computer I deployed all snap-ins and the process failed on the first snap-in saying that the hash does not match. If I install a single snap-in, it works fine.
I have sent my snapin files and my test results to Wayne.
But maybe can you try this to confirm my analyze:- remove all snapins for this host
- add sanpin 1
- add snapin 2
- deploy all snapins, it fails
- remove all snapins
- add snapin 2
- add snapin 1
- deploy all snapins, it works
Just revert order, but I can’t say if alphabetical order of snapin name or alphabetical order of file name should be the cause, or anything else
-
@Claude-Girard et al.
I will try confirming this myself though my own testing thus far has failed to produce the same issue currently.
For what it’s worth, everything is handled by sorting by names. It sounds, to me, more like the file names are coming in out of order but only in strange cases. Hopefully i can get more information for you by my tonight.
-
@Claude-Girard Here’s the test I just ran:
- Removed all snap-ins from host.
- Added two snap-ins (both at once): Inkscape and Python
- Ran ‘All snapins’ on host.
The SnapinClient originally errored out on Python with this message:
9/15/2016 4:06 PM Client-Info Client Version: 0.11.5
9/15/2016 4:06 PM Client-Info Client OS: Windows
9/15/2016 4:06 PM Client-Info Server Version: 1.3.0-RC-10
9/15/2016 4:06 PM Middleware::Response Success
9/15/2016 4:06 PM SnapinClient Snapin Found:
9/15/2016 4:06 PM SnapinClient ID: 326
9/15/2016 4:06 PM SnapinClient Name: Python
9/15/2016 4:06 PM SnapinClient Created: 2016-09-15 16:05:11
9/15/2016 4:06 PM SnapinClient Action:
9/15/2016 4:06 PM SnapinClient Pack: False
9/15/2016 4:06 PM SnapinClient Hide: False
9/15/2016 4:06 PM SnapinClient Server:
9/15/2016 4:06 PM SnapinClient TimeOut: 0
9/15/2016 4:06 PM SnapinClient RunWith: msiexec
9/15/2016 4:06 PM SnapinClient RunWithArgs: /qn /i
9/15/2016 4:06 PM SnapinClient Args: ALLUSERS=1
9/15/2016 4:06 PM SnapinClient File: python-2.7.10.msi
9/15/2016 4:06 PM Middleware::Communication Download: http://fog/fog/service/snapins.file.php?mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&taskid=326
9/15/2016 4:06 PM SnapinClient C:\Program Files (x86)\FOG\tmp\python-2.7.10.msi
9/15/2016 4:06 PM SnapinClient ERROR: Hash does not match
9/15/2016 4:06 PM SnapinClient ERROR: --> Ideal: D7334A6C5D6EDC8494E59E4A24B39DADEB39C63B4275F2F79E2C36422783C6A40DEC3227C81BE9990E033AD8630107279440035A55D4C1C9CDB667D39D0AF6A9
9/15/2016 4:06 PM SnapinClient ERROR: --> Actual: 91975CAE1F0111F655AF5EB66D92EA75A2638D97B06A32C18DAB14F9CFFBB00B6F5782AEB83FAA528816F6C5B6AB58B58ABAFD1B4DEFB0F640E1B812E14B3589
9/15/2016 4:06 PM Middleware::Communication URL: http://fog/fog/service/snapins.checkin.php?taskid=326&exitcode=-1&mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&newService&jsonTwo minutes later Python successfully installed with this message:
9/15/2016 4:08 PM Client-Info Client Version: 0.11.5
9/15/2016 4:08 PM Client-Info Client OS: Windows
9/15/2016 4:08 PM Client-Info Server Version: 1.3.0-RC-10
9/15/2016 4:08 PM Middleware::Response Success
9/15/2016 4:08 PM SnapinClient Snapin Found:
9/15/2016 4:08 PM SnapinClient ID: 327
9/15/2016 4:08 PM SnapinClient Name: Python
9/15/2016 4:08 PM SnapinClient Created: 2016-09-15 16:05:11
9/15/2016 4:08 PM SnapinClient Action:
9/15/2016 4:08 PM SnapinClient Pack: False
9/15/2016 4:08 PM SnapinClient Hide: False
9/15/2016 4:08 PM SnapinClient Server:
9/15/2016 4:08 PM SnapinClient TimeOut: 0
9/15/2016 4:08 PM SnapinClient RunWith: msiexec
9/15/2016 4:08 PM SnapinClient RunWithArgs: /qn /i
9/15/2016 4:08 PM SnapinClient Args: ALLUSERS=1
9/15/2016 4:08 PM SnapinClient File: python-2.7.10.msi
9/15/2016 4:08 PM Middleware::Communication Download: http://fog/fog/service/snapins.file.php?mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&taskid=327
9/15/2016 4:08 PM SnapinClient C:\Program Files (x86)\FOG\tmp\python-2.7.10.msi
9/15/2016 4:08 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Installing Python”,\r\n “message”: “Please do not shutdown until this is completed”\r\n}”
}
9/15/2016 4:08 PM Bus Emmiting message on channel: Notification
9/15/2016 4:08 PM SnapinClient Starting snapin…
9/15/2016 4:08 PM SnapinClient Snapin finished
9/15/2016 4:08 PM SnapinClient Return Code: 0
9/15/2016 4:08 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Python Installed”,\r\n “message”: “Installation has finished and is now ready for use”\r\n}”
}
9/15/2016 4:08 PM Bus Emmiting message on channel: Notification
9/15/2016 4:08 PM Middleware::Communication URL: http://fog/fog/service/snapins.checkin.php?taskid=327&exitcode=0&mac=E4:B3:18:E1:AC:70|E6:B3:18:E1:AC:6C|E6:B3:18:E1:AC:6D|E4:B3:18:E1:AC:6C|C8:5B:76:30:78:76&newService&jsonFog made no attempt to install Inkscape, yet still registered the task as complete after this. Inkscape never installed.
After this, I repeated the process i.e. removed the snap-ins, re-added them, and ran ‘All snapins’. This time, both Inkscape and Python installed correctly.
-
Mind running:
wget -O /var/www/fog/lib/client/snapinclient.class.php https://raw.githubusercontent.com/FOGProject/fogproject/working-RC-11/packages/web/lib/client/snapinclient.class.php
And testing another set of “all snapin” deployment? I’m hoping this was simply an ordering issue so the first iteration was out of whack. Why it worked with some and not others I don’t know, but I also am trying to make sure the snapins able to be “priority based” simply by the name of the snapin. I had it this way, but didn’t think much of it. Basically I think it was getting the snapins in order of the name, but the “index” it was looking for of the snapin tasking was mis represented.
-
@Tom-Elliott said in Deploy all snapins is confused:
Mind running:
wget -O /var/www/fog/lib/client/snapinclient.class.php https://raw.githubusercontent.com/FOGProject/fogproject/working-RC-11/packages/web/lib/client/snapinclient.class.php
And testing another set of “all snapin” deployment? I’m hoping this was simply an ordering issue so the first iteration was out of whack. Why it worked with some and not others I don’t know, but I also am trying to make sure the snapins able to be “priority based” simply by the name of the snapin. I had it this way, but didn’t think much of it. Basically I think it was getting the snapins in order of the name, but the “index” it was looking for of the snapin tasking was mis represented.
It seems ok now for me with this new version of snapinclient.class.php
Snapins are deployed in alphabetical order, seen in active snapin tasks windows.With old version, when looking at active snapin tasks, they was deployed in same order than declaring them in host snapins.
I mark this solved.
Thank you Tom, it was so strange that it was a pain to explain
.
-
I can confirm that this fix works on my end, too. I deployed an image and then sent out all snapins, and everything worked as expected.
Thanks, Tom.