Chat me up.

Maybe give me a teamviewer. I’m thinking the task is just “stuck”.

TaskID=1 is download tasks.

TaskID IN(18,19,20) are wipe tasks, for what its worth.

Thanks for your info. I will provide this information after a wedding.

For now I have resolved the problem by using the undionly.kpxe file from my previous install. However it seems after each SVN update, I need to restore the same file, I wonder if my future hardware is supported by it.

@siacotos said:

I got it thank you. turns out that the default storage group had the wrong credentials set.

🙂

tanks, that helped me a lot

@fjarken said:

Ah yes I have STP setup on my network, I came back to this thread again, cause I found a conflicting IP with my fog server…which I think was the root cause. A switch on my network had been configured with the same IP.

I’ll be sure to start asking this… seems its a more common problem than what one would think.

Gotta love happy endings.

Switchports are the same configuration?

Okay changed the partitions on the master to Primary Partitions instead of Logical Partitions and everything seems to be working fine now. I guess logical drives don’t really work well. In any case I’ll mark this solved because the issue has veered wildly from the initial question, which Tom answered for me. Thanks all.

I have acl/vlan (but they have not changed recently only my fog version have changed) and the fog server is on the same vlan as the computers

Hello,
after update to version 3594 everything looks good 😉
Thank for fast response.
Regards.
FOG forever 😉

@curvature Please note that the upload-task moves the image from /dev to /images via FTP after uploading completes. If there are old images stuck in /dev, you will just need to delete those.

If you upload an image and it moves correctly, you’re good to go.

@Wayne-Workman @Tom-Elliott Thanks for all your help

@Wayne-Workman Installed Fog Trunk and it works! I was able to register a host. Thanks for the suggestion, I had read up on it but never pulled the trigger. Still had to use .kkpxe for it to work, used .kpxe on last server, but that’s ok. Also fixed the need to manually restart the tftpd-hpa service after reboot, so all is good. Thanks again, Mick

[06-22-15 12:37:26 pm] * No Tasks Found! [06-22-15 12:37:36 pm] | Task (6) is new! [06-22-15 12:37:36 pm] | Task (6) /images/Image22062015 image file found. [06-22-15 12:37:36 pm] | Task (6) 1 client(s) found. [06-22-15 12:37:36 pm] | Task (6) sending on base port: 56438 [06-22-15 12:37:36 pm] CMD: cat /images/Image22062015/d1p1.img | /usr/local/sbin/udp-sender --interface eth1 --min-receivers 1 --max-wait 600 --portbase 56438 --full-duplex --ttl 32 --nokbd --nopointopoint;$ [06-22-15 12:37:36 pm] | Task (6) has started. [06-22-15 12:37:46 pm] | Task (6) is no longer running. [06-22-15 12:37:46 pm] | Task (6) has been cleaned as complete. [06-22-15 12:37:56 pm] * No Tasks Found!

Haha I found the problem lol, wrong Interface (!eth1 -> eth0) on Multicast ~_~, sorry for the topic and thanks for your fast answer.

Figured out how to boot the computers in legacy so we went that route instead of figuring out how to do it with UEFI. Thanks to all who helped, especially @Tom-Elliott, who is a very cool dude. Happy to finally get to work!

I’m not aware of any logs specific to this. Normally, people are able to post a photo of an error, or type an error out… the overachievers post videos - those are the best.

And you don’t have to upload an hour long (likely HD) video. If you see an error in your video, take screen shots of it and post the pictures here.

Could be a bug where imaging a pc isn’t clearing the security token anymore. @Tom-Elliott ideas?

@Wayne-Workman That is great! I will try it and see if it works thanks.

That is what I did. I will say I haven’t rebooted in a while so not sure if it worked for me but that is what I did.

@Gary-Kulovics

sudo mount 10.39.xxx.xxx:/images/ /images

The reason for the fstab error is because it didn’t have a place to be mounted to. (the /images part with out the colon)

If the argument isn’t setup properly, it scans for fstab to try automating mount point for you. If it can’t find it you get that error.