@tgidwani Ahhh, I see, got that wrong, sorry. I will take a look at our code again to see if I can figure out what might be causing this.

Just to be sure, Do you still get the full list of exact same ftp_… messages in the log everytime even when SELinux is disabled/permissive?

@Chris-Whiteley Ok, this partition layout looks fine as well. In the pictures we see that it seems to try to expand the partitions and doesn’t hit any obvious error but the outcome is not what we expect. So we need to dive into this even more. Please add the following as Kernel Parameters to this hosts’ settings and run another debug deploy: isdebug=yes ismajordebug=1

When you get to the “Attempting to expand/file partitions” (that’s before the blue partclone screens) pay attention and take pictures again. It should give us more details this time.

@Chris-Whiteley I can’t imagine this being the exact same image as you posted the files contents from. The partition layout below tells us it’s a GPT layout with four partitions. The pictures on the other hand show a legacy MBR layout with just two partitions. So either there is something going terribly wrong in our scripts or you got the wrong files.

@tgidwani said in Failing to Update Database after capture of image is complete on the client:

I cleared all three error log files today

Don’t you get new log entries when doing a new capture? There is no possible way we can help you without getting more evidence on what exactly is causing this. Logs are usually the best way to figure this out.

@tgidwani Alright, FTP is not an issue I am fairly sure now. Seems like I was miss-lead by the messages we saw in the php-fpm log file. Those probably came from the time before you disabled SELinux… I reckon.

So do you still see it failing on database update at the end of the task?

Please check the log files again but this time only take a look at the last 10 lines: tail -10 /var/log/php-fpm/www-error.log

@tgidwani Seems like we need to work this out manually. Use a ftp command line utility (Windows or Linux) and connect to the FOG server using the credentials you see in /var/www/html/fog/lib/fog/config.class.php.

Try connecting, then create and rename a directory just to see if things work like expected:

shell> ftp 192.168.2.5
Connected to 192.168.2.5.
220 (vsFTPd 3.0.3)
Name (192.168.2.5:roth): fogproject
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> pwd
257 "/home/fogproject" is the current directory
ftp> cd /images/dev
250 Directory successfully changed.
ftp> mkdir test12345
257 "/images/dev/test12345" created
ftp> rename test12345 12345test
350 Ready for RNTO.
250 Rename successful.
ftp> rm 12345test
250 Remove directory operation successful.
ftp> quit
221 Goodbye.

@tgidwani said in Failing to Update Database after capture of image is complete on the client:

with CentOS 7

Why didn’t I see this any earlier?!??!

Please run command getenforce on your FOG server and post output here.

Sure you wanna read this: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#Continue_pre-config

@tgidwani Please as well run grep USERNAME /var/www/html/fog/lib/fog/config.class.php and post results here.

@Chris-Whiteley Partition layout looks perfectly fine from my point of view. This layout should expand properly. But sure I believe when you say it doesn’t. Can you please schedule a debug deploy task and step through the whole process while taking pictures of all the messages you see on screen? Possibly we find something that prevents from expanding the last partition.

@jlthompsonpsd said in Image capture issues:

There are no error messages to forward. It just hangs indefinitely at Reading Partition tables.

How long have you waited?

Please schedule a fresh task for this host but this time tick the check box for debug! Boot up the client, hit ENTER twice to get to the shell. Now run the following command to find out which disk is being recognized: lsblk

Now with that run the following commands as well to see which one is the one that hangs:

udevadm settle
blockdev --rereadpt /dev/...
lsblk -I 3,8,9,179,202,253,259 -lpno KNAME,TYPE /dev/...

For the blockdev command you need to put in the correct disk device name that you got from the initial lsblk. Maybe it’s /dev/sda or /dev/nvme0n1 or …