Snapins do not deploy to VMs

[Wayne Workman]

@THEMCV Alright let me explain my thoughts on this. You’re saying you deployed all snapins to this VM guest. Yet when we look at the log, the log isn’t throwing any errors, it’s communicating properly with the FOG Server - and it doesn’t see any snapins. That doesn’t make sense.

Knowing that the FOG Client is very soundly built, I’m thinking there has to be a server problem. There just has to be - otherwise we’d be seeing errors in the fog client’s log file. Or you’re just somehow deploying to the completely wrong host in the web interface.

I would suggest running these cleanup commands (bottom of page) in your server - it might help: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Hosts_think_they_are_not_registered_.2F_can.27t_register_.2F_Already_Registered_.2F_other_registration_weirdness

Let us know if those queries affect any rows or not, then try to deploy all snapins again.

[THEMCV]

@Wayne-Workman Well narrowing it now a bit. Running “Deploy All Snpains” does not work for me. I tested “Deploy all snap-ins” on my machine which didn’t work, but if I deploy a single snapin, it goes fine. VM too.

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 2/10/2017 9:09 AM Client-Info Client Version: 0.11.9
 2/10/2017 9:09 AM Client-Info Client OS:      Windows
 2/10/2017 9:09 AM Client-Info Server Version: 1.3.5-RC-3
 2/10/2017 9:09 AM Middleware::Response Success
 2/10/2017 9:09 AM SnapinClient Snapin Found:
 2/10/2017 9:09 AM SnapinClient     ID: 1354
 2/10/2017 9:09 AM SnapinClient     Name: AutoHotKey
 2/10/2017 9:09 AM SnapinClient     Created: 2017-02-10 14:09:46
 2/10/2017 9:09 AM SnapinClient     Action: 
 2/10/2017 9:09 AM SnapinClient     Pack: False
 2/10/2017 9:09 AM SnapinClient     Hide: False
 2/10/2017 9:09 AM SnapinClient     Server: 
 2/10/2017 9:09 AM SnapinClient     TimeOut: 0
 2/10/2017 9:09 AM SnapinClient     RunWith: 
 2/10/2017 9:09 AM SnapinClient     RunWithArgs: 
 2/10/2017 9:09 AM SnapinClient     Args: /S
 2/10/2017 9:09 AM SnapinClient     File: AutoHotkey_1.1.24.03_setup.exe
 2/10/2017 9:09 AM Middleware::Communication Download: http://10.4.200.150/fog/service/snapins.file.php?mac=00:0C:29:16:F1:A6||00:00:00:00:00:00:00:E0&taskid=1354
 2/10/2017 9:09 AM SnapinClient C:\Program Files (x86)\FOG\tmp\AutoHotkey_1.1.24.03_setup.exe
 2/10/2017 9:09 AM Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"Installing AutoHotKey\",\r\n  \"message\": \"Please do not shutdown until this is completed\"\r\n}"
}
 2/10/2017 9:09 AM Bus Emmiting message on channel: Notification
 2/10/2017 9:09 AM SnapinClient Starting snapin...
 2/10/2017 9:09 AM SnapinClient Snapin finished
 2/10/2017 9:09 AM SnapinClient Return Code: 0
 2/10/2017 9:09 AM Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"AutoHotKey installed\",\r\n  \"message\": \"Installation has finished and is now ready for use\"\r\n}"
}
 2/10/2017 9:09 AM Bus Emmiting message on channel: Notification
 2/10/2017 9:09 AM Middleware::Communication URL: http://10.4.200.150/fog/service/snapins.checkin.php?taskid=1354&exitcode=0&mac=00:0C:29:16:F1:A6||00:00:00:00:00:00:00:E0&newService&json

So the issue lies in the “Deploy All” it would seem.

Want me to still ruin those commands?

[Wayne Workman]

@THEMCV said in Snapins do not deploy to VMs:

Want me to still ruin those commands?

It wouldn’t hurt anything, could only help.

So next thing, check that there are snapins associated to the machines you’ve tried to deploy all snapins to. So go to that individual host in the web interface, on the left click “Snapins”. Anything there?

[THEMCV]

@Wayne-Workman Ran it.

And yep, each host is assigned the snapins it is supposed to have. I always set them when I register PCs.

[Wayne Workman]

@THEMCV said in Snapins do not deploy to VMs:

And yep, each host is assigned the snapins it is supposed to have.

Ok next, we deploy all snapins via the below method on one of these hosts:
Web Interface -> Host Management -> [search for host, click host name] -> Basic Tasks -> Advanced -> All Snapins -> Schedule Instant selected -> Create all snapin tasks
After doing this, go to:
Web Interface -> Task Management -> Active Snapin Tasks and Active Tasks
What do you see? Did the snapins associated to that host appear in the Active Snapin Tasks list?

[THEMCV]

@Wayne-Workman No, it did not make it appear in the active tasks.

Single does, however.

[Wayne Workman]

@THEMCV ok. Immediately after doing “All Snapins” like normal, check the apache error logs. Web Interface -> FOG Configuration -> Log Viewer -> Apache Error Log, sort the list from newest to oldest, and post what you find into a code box. The log entries are timestamped (your server’s time is correct, right?). The relevant logs should be easy to find.

[THEMCV]

@Wayne-Workman Nothing really in the logs except for where I tried to view the apache logs from FOG and now /var/logs/apache/

[Fri Feb 10 09:49:05.169555 2017] [:error] [pid 20645] [client 10.4.69.52:53031] PHP Warning:  fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/fog/status/logtoview.php on line 86, referer: http://10.4.200.150/fog/management/index.php?node=about&sub=logviewer

That’s it though.

[Wayne Workman]

@THEMCV I just realized you’re on 1.3.5 rc3 - I should have thought of this sooner. Move to the latest 1.3.5 RC please, I think Tom is up to 5 now.

[THEMCV]

@Wayne-Workman Updated, still Deploy All is still not in the Active Snapin Tasks

[Wayne Workman]

@Tom-Elliott I’m all out of ideas for this. We’ve moved him to the latest RC, we’ve checked for apache errors, and I’ve walked him through doing it the way I know to work. He can deploy single snapins but when he does “All Snapins” they don’t appear in task management -> active snapins at all. What do you think?

[THEMCV]

@Wayne-Workman @Tom-Elliott got a fix going. It’s in working-1.3.5, so I think we can mark this solved.

[Wayne Workman]

@THEMCV Not solved until you can confirm it’s solved. Come back after you’ve tried the fix and let us know.

[Tom Elliott]

@Wayne-Workman He’s telling you that’s what he did.

[Wayne Workman]

@Tom-Elliott Oh. So confirmed fixed? It wasn’t clear to me.

[Tom Elliott]

@Wayne-Workman Yes, it was confirmed.

I realized the problem, but was on a meeting call. I asked him to test the “fix” and he confirmed with me on chat.