@Fog_Newb Thanks for the detailed report. Your diagnosis was right on all three points.

1b, runs a day late: the chart read TIMESTAMP columns as DATETIME. In the 26 hours after the move to UTC, that made a UTC time look like New York time. Your fix is in, and it covers the imaging, storage, inventory and fleet charts. This one also corrects itself once the 26 hours pass.

1a, 1.5 history missing: the upgrade added the image name column but did not fill it on old rows. A new schema step fills it from the task’s image. A run whose task or image was deleted cannot be recovered.

2, the tooltip: the asterisk on new captures is expected for the first 26 hours, and then it goes away. The tooltip wording was wrong. It now says the value “can be in America/New_York time or in UTC”.

PR: https://github.com/FOGProject/fogproject/pull/2056. It reaches the Patches channel when it merges to dev-branch. Run the schema update after you update, so the history backfill runs.

@Tom-Elliott Thanks Tom! Glad the SSH_PORT report turned up the other six settings too.

For the exports, I went a different route that keeps FOG managing its own lines: NFS also reads /etc/exports.d/*.exports, so I put the Kubuntu export in /etc/exports.d/kubuntu.exports. The installer rebuilds /etc/exports but never touches that folder. I’ll confirm it survives the next update.

@Tom-Elliott Thanks Tom. 1.5.10.2344 seems to be capturing fine. No additional null tasks were created and the PC had no problem checking in and starting the capture.

I’d swear, not only with this version but the earlier ones that were malfunctioning during check in and creating additional tasks, I had to create the task twice. Like I went through the process of setting up a capture but nothing showed up under tasks then had to do it again.

I can’t seem to duplicate it though. Setting up a 2nd capture for the laptop, I only had to do it once (and no additional null tasks were created).

PC finished the capture no problem and laptop checked in and is capturing now. Looks like 2344 did it!

Thanks again.

@Tom-Elliott Tom, looks like everything has been resolved after going from 2144 to 1.5.10.2218! No errors and I was able to capture no problem. Thanks

@Sebastian-Roth Can I bother you with this quick question ^^^

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

@Tom-Elliott Yes, everything is working as expected. For the longest time, FOG would always show UTC time for when an image was captured or deployed, now it is correctly showing local time and no more zombie processes! Thanks

@Tom-Elliott Thanks, going to switch back to 1.6 very soon.

@Fog_Newb Yep, it’s as I suspected:

The Line:

Subsystem sftp /usr/lib/openssh/sftp-server

should be changed to:

Subsystem sftp internal-sftp

Then restart ssh services: systemctl restart sshd

Then your Storage Node testing should succeed!

@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.

I ran chkdsk prior to capturing and it came up clean

alt text

UPDATE: So I tried everything for the ntfsresize error … turns out, I had to shrink the partition in windows a bit then expand it. After that, I could capture.

@Tom-Elliott sounds good!

@Fog_Newb probaly just typoed it and i went with it too lol.

@Small0145 No, it’s not.