database update issues following image capture

[george1421]

@epatterson So does the apache or php-fpm error logs give us any clue to why this is happening?

Out of curiosity, how many computers with the fog client installed is this fog server talking to? Or to ask it a different way, how many computer have the fog client installed on it?

[epatterson]

@george1421
Our setup is a single FOG server, with 2 network connections.
One to the main domain, and a second to a closed network that we use when imaging machines.
We aren’t actually installing a client on the machines. They are only connected to the FOG closed network to be imaged, or to capture an image back to FOG once updated.

I am running a test currently. I have imaged a machine, I am updating it, and will create a new image category to capture the image back to the system. I’ll update the thread once I have tried imaging back to the system. Thanks.

[george1421]

@epatterson Ok that is fine. I was just trying to think of a reason why on occasion we get this gateway timeout. Having 500 computers checking into the fog server while trying to image might do just that. But if you don’t have the fog client running anywhere then fog server performance isn’t the problem. The rest of your setup sounds typical for a business environment.

[epatterson]

@george1421
So, saving the image from the machine to a new image in FOG worked. Could we have a database issue?
It’s very odd that we can save a new image capture, but not a capture from an updated, established, image.

[george1421]

@epatterson So from the same machine do a back to back capture. The first time it will be a new image and the second time same machine, same relative time frame will be a replace image capture. See if your logic holds.

Are you running any other applications on your fog server that might make php-fpm slow to respond to apache? What does top show us?

[epatterson]

@george1421
The machine I was working with had to be sent out for the user. So, I imaged another machine, with the build I had created, updated the build, and imaged back. It worked w/o issue.
Our FOG server only runs the FOG processes. We aren’t using it for anything else.
Another thought. Because our machine is an older desktop and using the original hard drive, we have to make use of secondary attached storage. In doing so, we move images back and forth as needed. Could that be causing an issue with the images, or how the database “sees” them? Should we alter the image path to the attached storage, working all processes from there, instead of moving them back and forth?

[george1421]

@epatterson said in database update issues following image capture:

we have to make use of secondary attached storage

What method are you using to do this? Is it external DAS storage, NFS, or iSCSI?

[epatterson]

@george1421
We are using a USB, directly, attached MyBook storage unit. I then just run a move between the storage and the main machine.

[george1421]

@epatterson So moving the images may be the problem.

FWIW if you have DAS attached storage you can / could add a second hard drive to this computer, or if the USB hard drive is attached via USB3.0 you could image directly from that.

In fog you would just setup a second primary storage node in a new storage group. You would use all of the same settings as your default storage node. You do not want to add this alternate hard drive as a secondary storage node in your default storage group because then fog will just replicate from the internal hard drive to the usb hard drive. But if the usb hard drive is setup as a master node in its own storage group then FOG will be happy and you won’t have to fiddle with moving image files.

Is there an option to add a second physical hard drive to the existing fog server? I realize you use a usb attached drive for this today.

[epatterson]

@george1421
I’ll shut the machine down and do some checking. I’ll let you know. Thanks.