Posts made by Psycholiquid

@Wayne-Workman No it is the same server I have always had, the image is no more than 2 weeks old.

@Wayne-Workman Not sure what your asking. If I updated to latest yes. I am fully updated. I saw a commit with a new client was put in. I think it is version 0.9.7 not so I am 2 version behind at the time of imaging

When imaging a new machine after updating to Trunk 4555 none of my clients can update the FOG Client. (Using Client 0.9.4 before update.) If I uninstall and reinstall the new client everything works as intended. So here is what I am seeing after an image:

Client Images without issue.
Once Sysrep Completes the services are turned on for FOG Client
The service will constantly restart on its own
Error from FOG client Log is the following for the Client Updater:

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 11/19/2015 11:44 AM Client-Info Version: 0.9.5
 11/19/2015 11:44 AM ClientUpdater Running...
 11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=34:64:A9:29:2F:7D||00:00:00:00:00:00:00:E0&newService=1
 11/19/2015 11:44 AM Middleware::Communication Response: Success
 11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/service/getversion.php?client&newService=1
 11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/client/FOGService.msi
 11/19/2015 11:44 AM ClientUpdater ERROR: Unable to prepare update helpers
 11/19/2015 11:44 AM ClientUpdater ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\FOGUpdateHelper.exe' because it is being used by another process.
------------------------------------------------------------------------------

 11/19/2015 11:44 AM Bus {
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 11/19/2015 11:44 AM Bus Emmiting message on channel: Update
 11/19/2015 11:44 AM Service-Update Spawning update helper
 11/19/2015 11:44 AM Bus Registering ParseBus in channel Power
 11/19/2015 11:44 AM Update Helper Shutting down service...
 11/19/2015 11:44 AM Service Stop requested
 11/19/2015 11:44 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 11/19/2015 11:44 AM Bus Emmiting message on channel: Status
 11/19/2015 11:44 AM Update Helper Killing remaining FOG processes...
 11/19/2015 11:44 AM Update Helper Applying MSI...
 11/19/2015 11:44 AM Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="" HTTPS="0" WEBADDRESS="fog-server" WEBROOT="/fog" ROOTLOG="1"
 11/19/2015 11:44 AM Data::RSA CA cert found
 11/19/2015 11:44 AM Update Helper Starting service...
 11/19/2015 11:45 AM Bus Became bus server
 11/19/2015 11:45 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 11/19/2015 11:45 AM Bus Emmiting message on channel: Status```

I am not seeing this issue when replicating in my environment.

I was able to set Client to Deploy then delete the task without issue. I am also not seeing the typo:

I get the location request and I hit ? and it just loops back to asking again and again. I know the numbers and can hit 7 or 8 which are the DB number assigned to my locations but they never show up on the menu when requested.

Not showing locations when pressing ?

Fog Trunk Version 5445

@Wayne-Workman roger that. Appreciate the input.

@Wayne-Workman You think I should wait for the transfer to finish before I do that? Don’t want to delete it in that state, might cause an issue.

@Wayne-Workman I think I will go the route of recreating and allow the DB to do the deleting to make it cleaner , but I am getting more schooling on how everything is working. I am glad you all are here to push me along, now back to my setup post to help others.

Everything is working like a champ got two running in CINCINNATI at the same time one using 12GB a min and one using 2GB a min which is very good. I also have one in NASHVILLE working at the same time as the others moving 10GB a min all from their respective images. The only thing I am seeing now that worries me is the CINCINNATI master is transferring something to the NASHVILLE node (I think it is the other images I had but told the FOG system to delete.) The files are there but not in the DB so we may need to look at the deletion of the files when removing an image from the GUI. .

@Tom-Elliott I will be able to test here in a bit, my network admin jsut killed my switch in Nashville waiting for the onsite tech to get to work. Kids and their sleeping in.

@Tom Elliot showed me the fix. The storage node setup for Management wasn’t set correctly.

Pulled user and pass from .fogsettings on the node and entered into the web interface on the storage node.

This resolved the FTP error.

Once I setup the locations I get this from the Nashville location:

Now the error is simple and I understand it. what I dont understand is why it works when it is pulling from the wrong side and when it is setup correctly it doesn’t work at all.

OK lets add a littel bit of troubleshooting to this. So I had the groups setup for locations. Once I removed them all and left the image as it was the first time it pulls form teh right location. So lets look at the layout.

I have two locations right now.

Cincinnati
Nashville

I have one image in my FOG system, that has seemed to replicate from Cincinnati to Nashville without problem.

Without setting up locations I can pull the image from the Cincinnati location from both Cincinnati and Nashville (all be it is slow from NAS)

If I setup the locations like so

It starts to pull from Nashville for some odd reason.

Also to add I cannot image more than one machine at a time. I am not talking multi-casting but if I start and image the next one I start says:

Not really sure what is going on here, anyone have any ideas.

@Wayne-Workman said:

@Psycholiquid What version are you using? Are both the main server and the nodes all on the same version?

Yes version 5233, I know there are other revisions but I cant update at the moment but there weren’t any updates pertaining to this issue in the commits that I noticed.

Yeah but I had to remove the locations, when I had them setup it wasn’t allowing PCs to boot into FOG at all. Again this is something I have setup wrong I am just not sure what I am doing wrong.

To get around this I am turning off the second node and it will allow pulling fo\rom the correct location.

Setup Multi Node FOG implementation. Now images are being pulled from the wrong node (Over my WAN). I am sure I have something setup wrong.

Little help?

Claiming for further editing

OK lets try this again, going to start working on this again. Got tied up in other work functions and was torn away form this.

Claiming for further editing

Claiming for further editing