Snapins do not deploy to VMs

[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.