FOG not saving images in the directory

[davidgoncalves]

I have multiple images on our FOG server, and all of them can be deployed with success.
However, I’m trying to create new images, and every time I capture them, a text file with the name of the supposed directory is created on /images, but the image files are not there.
There’s enough disk space and there’s no error during capture. Using Ubuntu 18.04.5.
Any idea of what could it be? Thank you!

[george1421]

@davidgoncalves If you look in /images/dev directory do you see sub directories there that appear to be mac addresses? These should be consistent with mac address of the source computer. Under normal conditions there should not be any of these directories in the /images/dev folder unless there is an active capture going on.

[Sebastian Roth]

@davidgoncalves Also please run the following commands on your FOG server shell and post output here:

mount
df -h
ls -al /images/dev

[BrightPipe]

@george1421 sorry for bringing back this old topic, but I am running into this same issue. But I am on Ubuntu 24.04 and FOG 1.5.10

When I run a capture task it completes successfully, but its not moving the files to /images. There is an empty locked document in /images with the name of the image. In the /images/dev there is a folder with the mac address of the client I captured from.

I’ve tried running the following commands to fix the permissions:

sudo chown -R fogproject:root /images
sudo chmod -R 777 /images```

then ran the capture again, but had the same result.
Any idea on how to fix this?

[george1421]

@BrightPipe OK what is happening here is, the FOS engine has uploaded the image to /images/dev/<mac_address> using NFS. Then the FOS engine connects to the fog server using FTP as the fogproject user. Then it issues a mv (move) command from /images/dev/<mac_address> to /images/<image_name> directory.

So you are saying there is a directory name in /images that matches <image_name> but the files stay in /images/dev directory? If yes then it appears that the fogproject user doesn’t have rights to ‘move’ the files out of /images/dev , but it does have rights to create the directory in /images.

That gives me a clue that the fogproject user doesn’t have permissions to /images/dev/<mac_address> directory.