UPDATE:
Checked permissions fogproject:apache user has full rights to all snapins, why it is the apache group I don’t really know.
also changed the www.conf file.
No change unfortunately.
Latest posts made by borg
-
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
-
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
@george1421 will try that when I get back to the mines tomorrow, an let you know.
@Sebastian-Roth the “/opt/fog/snapins/BMS_genveje.ps1” do exist I checked, did not check permissions though, Will do tomorrow.
on a weird note the FOG server was very slow on accepting new snapins? when I deployed a new snapin it lasted up till 60s before the GUI told me it was updated I thought it strange, but put it down to bad links, sorry for not including this in the original post. -
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
on your note I did change the /etc/httpd/conf.d/fog.conf to include a proxy timeout, saw this on an older post. but not working solution.
-
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
No we did not change anything, we run a vanilla CENTOS 7 and a vanilla FOG 1.5.9-RC-1 and RC2 fresh install, no changes, only thing in that matter I can think of is that we run it as an ESXI client.
-
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
thank you for your support,
We are running 1.5.8 with no problems.
on a note, this is also the server we “copied” the original Image from.
the clients were running FOG client 0.11.X if I remember correctly, not online with my servers at the moment.
that is why I updated our image with fog client 0.12.0 to work with 1.5.9-RCx. -
RE: Not able to capture Image
may I inquire,
Have you confirmed that the host has been registered with the server? on PXE boot there should be a screen telling you that the host is registered as [hostname]
Have you set DHCP option 60 and 67 (i hope I remember correctly, please correct if I am wrong)? -
RE: Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
we have 5 sites with 20 - 30 clients on each site.
no replication between servers, they are independent but the network is routed, for administrative purposes. the reason for this is that the sites need to be able to run independently if core network fails. -
Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
Hi there,
I am admittingly new to this forum, I have used FOG for years without any problems, and I am thankfull.Now I have encountered a problem I simply can’t figure out.
We have deployed a few new servers in the organisation within the last few months, and have now encountered problems deploying snapins to windows images.
The problem only resides on the 1.5.9-RC1 and RC2 versions.
The “old” servers we have in “production” works fine.Snapins are not being deployed, apparently it is an issue of access to a file. (snapins.file.php) or so I think.
running Centos 7 as a virtual client on an ESXI 7 server, deploying windows 10 1909.
deploying are not a problem everything works fine and as intended, only snapins are a problem.searching for similar problems on the forum as not produced a working solution.
logs captured are as follows:
FOG client log:
fogClient.logService master log:
servicemasterLog.txtApache error log:
apache errorlog.txtphp-fpm-error log:
php-fpm-errorlog.txtphp-fpm-www log:
php-fpm-www-log.txtsorry about all the data, please let me know if you need further data.
Also please ignore any weird snapin names, I am Danish…The servers are in a closed no internet network, separate sites no cloud, no replication. only stand alone servers, there are a routed network connection between sites. we have however used base images deployed from one server to capture on the next, only difference between servers is a reinstallation of the fogclient to pair with the “next” FOG server.
Again I am Danish so I hereby beg your pardon for spelling and grammar.
Any guidance will be highly appreciated.