@Sebastian-Roth When I was experiencing said error the intermediary directory was never being created.

It is working now. As mentioned in my previous reply asking about the default gateway, I think it has something to do with the Gateway configured in my network interface’s configuration file.

Within the config file, GATEWAY= was pointing to an IP address that was not assigned to any machine on the current network when I moved networks. When I removed the GATEWAY= line from the config and ifdown and ifup my network interface, the update database error was resolved.

Does FOS when communicating with the FOG server go through the default gateway even when both the client running FOS and the FOG server are on the same network?

@Sebastian-Roth Good to know about some of the warnings. Here are the screenshots:

@Sebastian-Roth My apologizes for the confusion. I meant I cleared them only today to eliminate the possibility of looking at stale logs entries.

I do get new log entries every time I run a capture. I continue getting the same error every time. Update database failed with the same ftp_put failure. Would you like me to re-run the capture? Since I have not changed anything I am not why the problem would go away?

Do you think it is a version issue? I am running 1.5.6? Does updating the database process depend upon DNS or a default gateway by chance?

@Sebastian-Roth I cleared all three error log files today before posting the screenshots here. With or without SeLinux disabled I keep getting the same failed to update database error.

@Sebastian-Roth Here is the screenshot:

@Sebastian-Roth I followed all the steps in the mentioned article when setting up my CentOS 7 VM and before installing FOG.

Here is the screenshot:

When I got the update database failure, I disabled and stopped firewalld and set selinux=disabled in /etc/selinux/config and restarted my CentOS 7 VM. Re-ran the capture process but still continued to get the same failure of updating database.

@Sebastian-Roth Here is the screenshot:

@Sebastian-Roth Appreciate your help and quick response. Here is the screenshot:

@Sebastian-Roth if by fog-client software you mean the service that runs in the background I have not installed that service on the Windows 10 OS I am trying to capture with FOG. Currently, I am only working with 1 physical PC.

Here is the workflow I am following:

• PXE boot physical PC
• Perform full host registration and inventory on physical PC using FOS
• Using the FOG web UI, schedule a capture task for this physical PC
• PXE boot the physical PC and the capture task begins running
• Capture completes but encounters a update database failed error

I have gone through the entire troubleshoot guide here and still I continue getting the failed to update database error.

Here are the screenshots from the 3 main error log files:

@george1421 Here are the screenshots of the entire process that my client goes though once a capture task has been scheduled:

No, I do not see any error message (before the failed to update database) that mentions anything about ftp_put.

Yes, those passwords match the password stored in /opt/fog/.fogsettings