Yes, Wayne; I guess so…
We spent a couple of days recreating a new image from scratch and it’s working: we’ll use that.
Thanks everybody for the support.
Yes, Wayne; I guess so…
We spent a couple of days recreating a new image from scratch and it’s working: we’ll use that.
Thanks everybody for the support.
Dear Wayne,
thank you for your support.
If I deploy another image on the same client PC it can succesfully connect to the FOG server (so i don’t think is a problem on the switch or on the cable).
I’ve tried from several PC, some of them are on the same switch that FOG is connected to and some of them are connected to another switch; but the issue remains.
Right, i’ll clean the DB then. Thank you.
Thanks Trevelyan; we actually restarted the Service several time but without luck: the behaviour was the same (unable to contact the fogserver).
We don’t use SSD drive neither on server or client.
I’m wondering if it could be something related to the .NET libraries or to some other kind of restriction on the Microsoft side…
It seems also that the upd-sender process started with
min receivers=5 for the first session (the one set with msClients=7)
min receivers=3 for the second session (the one set with msClients=3)
that means that 2 PC were not depoloyed: in fact they are still waiting on the first PartClone screen.
Hi Tom,
thank you for the quick reply.
Yes, all the 10 PC in the same group are set with the same Image Id (ID: 9).
I can see the same ID also in the multicastSessions table, column msImage.
Usually I use the “classic” setup.exe.
But this time I tried both.
Hi all,
just a question: i created a group with 10 pc and I created a multitask deploy job for that group.
Fog created two different row in the multicastSessions table one with 7 msClients and one with 3 msClients.
This is slowing down the whole deploy process (more network traffic, server I/O contention because of the two udp-sender processes).
Is this behaviour normal? I supposed to have just one multicastSessions with 10 clients.
I’m using fog svn 3559 on Centos 6.6.
I’ve tried everything.
I removed the antivirus, disabled the firewall, uninstalled and reinstalled the Service (the IP address was correct). I uninstalled all the additional software too (skype, vlc, chrome, etc…).
I also tried to sniff traffic using Whireshark: I noticed that the client never starts the TCP connection to the server…
Few details to add:
Dear Support team,
we are facing a weird issue today.
We have been using FOG (version 1.2.0 on CENTOS 6.6) for several months so far; few days ago we installed it into a new LAB made up by 60 Pc.
When we installed the FOGService on the source PC the service can’t access the FOG host (server ip is 192.168.1.254).
The weird thing is that if we access the server from a browser (http://192.168.1.254/fog) we can successfully see all the fog webapp pages.
The FOG Log is:
11/06/2015 16.35 FOG::GUIWatcher Starting GUI Watcher...
11/06/2015 16.35 FOG::HostnameChanger Starting hostname change process...
11/06/2015 16.35 FOG::HostnameChanger Yielding to other subservices for 9 seconds.
11/06/2015 16.35 * Starting FOG.HostRegister
11/06/2015 16.35 FOG::HostRegister Starting host registration process...
11/06/2015 16.35 * Starting FOG.MODDebug
11/06/2015 16.35 FOG::MODDebug Start Called
11/06/2015 16.35 FOG::MODDebug Sleeping for 100 Seconds
11/06/2015 16.35 * Starting FOG.PrinterManager
11/06/2015 16.35 * Starting FOG.SnapinClient
11/06/2015 16.35 FOG::PrinterManager Starting interprocess communication process...
11/06/2015 16.35 FOG::SnapinClient Starting snapin client process...
11/06/2015 16.35 * Starting FOG.TaskReboot
11/06/2015 16.35 FOG::PrinterManager interprocess comm startup: OK
11/06/2015 16.35 FOG::TaskReboot Taskreboot in lazy mode.
11/06/2015 16.35 * Starting FOG.UserCleanup
11/06/2015 16.35 FOG::TaskReboot Starting Task Reboot...
11/06/2015 16.35 * Starting FOG.UserTracker
11/06/2015 16.35 FOG::UserCleanup Sleeping for 15 seconds.
11/06/2015 16.35 FOG::UserTracker Starting user tracking process...
11/06/2015 16.35 FOG::SnapinClient Sleeping for 462 seconds.
11/06/2015 16.35 FOG::DisplayManager Attempting to connect to fog server...
11/06/2015 16.35 FOG::HostRegister Attempting to connect to fog server...
11/06/2015 16.35 FOG::PrinterManager Attempting to connect to fog server...
11/06/2015 16.35 FOG::UserTracker Attempting to connect to fog server...
11/06/2015 16.35 FOG::HostRegister Failed to connect to fog server!
11/06/2015 16.35 FOG::HostRegister Impossibile effettuare la connessione al server remoto.
11/06/2015 16.35 FOG::HostRegister in System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
in System.Net.WebClient.DownloadString(Uri address)
in FOG.HostRegister.registerHost()
11/06/2015 16.35 FOG::HostRegister Sleeping for 1 minute.
11/06/2015 16.35 FOG::DisplayManager Failed to connect to fog server!
11/06/2015 16.35 FOG::DisplayManager Impossibile effettuare la connessione al server remoto.
11/06/2015 16.35 FOG::DisplayManager in System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
in System.Net.WebClient.DownloadString(Uri address)
in FOG.DisplayManager.doWork()
11/06/2015 16.35 FOG::DisplayManager Sleeping for 1 minute.
11/06/2015 16.35 FOG::UserTracker Failed to connect to fog server!
11/06/2015 16.35 FOG::UserTracker Impossibile effettuare la connessione al server remoto.
11/06/2015 16.35 FOG::PrinterManager Sleeping for 1 minute.
11/06/2015 16.35 FOG::UserTracker in System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
in System.Net.WebClient.DownloadString(Uri address)
in FOG.UserTracker.track()
11/06/2015 16.35 FOG::UserTracker Sleeping for 1 minute.
11/06/2015 16.35 FOG::HostnameChanger Attempting to connect to fog server...
(sorry but some words are in italian; Impossibile effettuare la connessione al server remoto means “Impossible to contact the remote server”).
We try to reinstall the service with a different users, we ran the installer as Administrator, we removed windows firewall, disable the antivirus, uninstall all the software but without any luck.
Another weird thing is that if we deploy an image used into another LAB, the FOGService starts normally and it can access the server.
Can someone help us?