Image task not going through

[Tom Elliott]

It appears this machine was deleted, then somebody put it through quick registration potentially? Then tried doing a full registration? I’m only guessing. Pending hosts typically pop up because of the FOG Client installed on the machine checking in with the server. It will use the name the machine currently has associated to it at the time it checks in to register, which in this case appears to have been its mac address.

[JackieJack]

@tom-elliott Deleted hosts, put fog service smart installer, tried quick regist but not full.

So, uninstall fog service, delete pending host and re-register?

[Tom Elliott]

@jackiejack Just delete the host and reregister, before deleting the pending host, just power off the machine so it doesn’t accidentally pop back in.

[JackieJack]

@tom-elliott Deleted smart installer and all hosts and images and all pendings. Re-registered host. Re created image. Associated host with image. Same error. Task not going through. Red icon by hosts, image no valid data. The host restarted no problem.

[Tom Elliott]

@jackiejack I’m so confused.

Why do you keep deleting all hosts and images, all pendings.

Just delete the host in question.

What image is associated? You are doing capture or deploy? Did you capture the image first?

[Tom Elliott]

Red icon is just “Ping Hosts” this has no bearing on the ability to image.

[JackieJack]

@tom-elliott Doing a capture
After I created an image, I go back to my host and click host image and choose the image definition, update. Then hosts, capture image to create task. Then USB on host, and choose deploy/capture.

I even tried a brand new host - a windows 8.1 old dell. New host, new image def (win 8.1), associate, no smart installer, capture task, USB host capture, it goes well then when host reboots, FOG server task still swirling. No valid image data.

(I keep deleting everything so I would start back from scratch/noob fears)

[Tom Elliott]

@jackiejack what version of fog are you running?

[JackieJack]

@tom-elliott latest one 144

[JackieJack]

@jackiejack Right, so what I did was got another new host, and registered it.

It shows up with red icon in host management. Yes, right there in the beginning just after registering. So? I thought that my USB FOS was the problem. Created a new one, using the george fos-usb.img, Win32DiskImager. Exact same error.

At first register, red icon. No pending hosts

[Sebastian Roth]

@tom-elliott said in Image task not going through:

Red icon is just “Ping Hosts” this has no bearing on the ability to image.

See what Tom said about the red icon. Nothing to do with imaging.

So what error exactly do you get now? As you seem to have registered the client, just schedule a task for it and reboot to see what’s happening. Post a picture in case you run into an error.

[JackieJack]

@sebastian-roth Yes sir, doing that right now. (I am racists against red exclamation marks lol). Will give you an update first thing tomorrow (Partclone is taking a while)

[JackieJack]

@jackiejack

[JackieJack]

@jackiejack

If you want more/closer screenshots lemme no

[Sebastian Roth]

@JackieJack Well now there is something wrong with your FTP account that is used in the background to move the image files from /images/dev/ to /images/ after upload. Be careful when using the fog user account for administration as well. This is intended as sort of “internal FOG account”.

Please follow this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

[JackieJack]

@sebastian-roth Right, I completed this as per george’s instructions:

Should I do them over? I mean I ftp to my fog server normal user account regularly. Upload and download files.

[JackieJack]

@jackiejack Did it over, everything seems to be fine.
It asked to update mysql but when I went to the fog site nothing to update. No button. Other than that, all is well.

[JackieJack]

That root user owner on the second line is okay? Running chown -R fog:root /images solve problem?

[Tom Elliott]

@jackiejack The second line refers to the “parent” directory (/) so yes it’s perfectly fine. A chown -R fog:root /images won’t solve the problem if you’re still having problems as, based on what I can tell, the permissions are already setup as fog:root.

[JackieJack]

@tom-elliott

Change interface from n to enp5s0 on storage management?