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

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

@sebastian-roth
Good morning,
I imaged some new machines yesterday, updated their applications, etc, and ran captures, on 2 of them, back to FOG just now.
The image capture ran correctly, but the process, again, failed on the database update. Receiving a “504 Gateway timeout” again.
The successful capture Friday was on a completely new image, first time capture.
I will try looking into logs later today.

@sebastian-roth
OK. I will be doing some more testing next week. I will update the thread with results. Thanks.

@george1421
Well, holy mother of all that is good and green. The machine I just tested with completed w/o issue.

Could it have anything to do with the model, or image itself? We normally work with Lenovo T15 and/or T14 machines. However, I have an X1 Carbon that we needed to wipe prior to being sent in for repair, so I registered and inventoried it. Created a new image category, specifically for it, so we can put it back when it returns, and ran the capture.

I have another machine (T15) that I just built. I’ll try capturing it as well and see what happens. I’ll update the thread once done. Thanks for helping me out today.

@george1421
During the process, we have not had any issue accessing the site. I am able to PXE boot and register/inventory machines w/o issue. I am able to deploy an image w/o issue and monitor the process on the site from Active Tasks.

Additionally, when running a capture, I am able to monitor it on the site as well. I am testing a capture now, to get a recent log entry to look into. I may need some guidance locating the logs, as I am still learning linux. I know I have been in them before, when we had the memory issue with PHP.

@george1421
Thought the actual output might be more helpful:
sysadmin@fog:/$ systemctl status php7.4-fpm
● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-03-25 10:11:58 CDT; 1h 7min ago
Docs: man:php-fpm7.4(8)
Process: 1141 ExecStartPost=/usr/lib/php/php-fpm-socket-helper install /run/php/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (code=exited, st>
Main PID: 863 (php-fpm7.4)
Status: “Processes active: 0, idle: 6, Requests: 68, slow: 0, Traffic: 0req/sec”
Tasks: 7 (limit: 14143)
Memory: 28.9M
CGroup: /system.slice/php7.4-fpm.service
├─ 863 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
├─1136 php-fpm: pool www
├─1137 php-fpm: pool www
├─1138 php-fpm: pool www
├─1139 php-fpm: pool www
├─1140 php-fpm: pool www
└─1556 php-fpm: pool www

Mar 25 10:11:47 fog.it.nex-tech.com systemd[1]: Starting The PHP 7.4 FastCGI Process Manager…
Mar 25 10:11:58 fog.it.nex-tech.com systemd[1]: Started The PHP 7.4 FastCGI Process Manager.