@martinetwork There is no way we can help without you telling us more details about your network. Broadcast domains, VLANs, switches, routers/layer-3-switches, config, …

Quite often forwards are to be configured for one particular sender. So your PDQ waking properly does not mean much.

@wayne-workman as in RC12? Ok I have another Issue I will be posted but testing again to make sure I can replicate it before posting. Its with Snapins not reporting they are finished and then keep trying to run over and over again. Windows 10 and Windows 7.

Trying to avoid updating to RC and waiting for next stable but if its fixed in an RC we might have to go for it.

@D_quiros Please check the apache logs. See my signature…

@george1421 said in Target computer booting from router not fog:
1_1518442700261_Ubuntu_FOG-2018-02-12-14-32-36.png 0_1518442700157_Ubuntu_FOG-2018-02-12-14-32-02.png

@sebastian-roth That did the trick! That server can now update its kernel.

It’s interesting to see how two different causes have similar results.

@george1421 that’s what I told him too.

@orioliz Have you done a proper filesystem check on that system? Boot it up using a live Linux CD/DVD and run fsck /dev/sda1

@wayne-workman
Thanks, next time i will take some time before acting and wasting my time.
I keep this guide for the next time.
Thank.
Eric.

@msi said in Image capture task did not complete:

By the way, love the new look on the FOG

@Joe-Schmitt

@jburston see the wiki article called “password central”. If you need further help, please open a new thread for the new issue and post the last 200 or so lines from your fog.log file.

Fixed by changing memory size in php.ini

@tom-elliott yes it went back to the full amount.

@george1421 He’s referring to the autologout module, but you’re definitely not wrong.

@blkeller, duly noted. Updating the time restraints means updating the entry in SQL, not hard, and I can have that done fairly easily. Even not allowing the setting to hold on to anything less than 5 minutes isn’t too hard, though do I set it to 0 if it’s below 5? Just thoughts on how best to approach. I don’t think it should warrant an “error” to update the host because that field isn’t really necessary for normal imaging functions.

@wayne-workman Absolutely. As soon as I can I will.

@Julianh I am sorry to say that but your setup is quiet complex with so many disks mounted in various locations and I don’t think we’ll be able to reliably guide you through a migration here in the forums. I am not sure what to advice. As Wayne said, 1.4.4 can deploy 1.2 images. So unmounting and moving the disks to the new system should work.

@x23piracy Missing since RC10 - see here: https://github.com/FOGProject/fogproject/tree/1.5.0-RC-10/packages/tftp

@Tom-Elliott We should definitely put up a big note for the final 1.5 release.

@shad0wguy It would be helpful once you prove this setup as reliable, if you could write a tutorial explaining how you setup FOG on this device as well as what others need to watch out for. I don’t think the FOG Project developers will support this configuration directly, but I’m sure there are others in certain situations with your exact use case. Your configuration may help guide them.

Please consider contributing to the cause, if you can.

@tesparza well that would certainty do it. Reset Encryption Data is generally not advised to be done unless you specially do something to the client that would require it.

Hey Guys, thanks for leading me in the correct direction… one of our NEs worked with me today, what we found was… well… lets just say that I am glad I am a server engineer and not a network engineer.

We config’ed one port for Spanning tree fast port and it connects correctly. Now I have to go back to my Sys Eng and ask him WTF?!?!

Thanks again,

Rbryant

@dylanderr Please read through this:
https://wiki.fogproject.org/wiki/index.php?title=Password_Central#For_Storage_Nodes

The settings you set in the web UI only tells the fog services what credentials to use, it does not set the actual password in mysql. I will clarify this in the article, thanks for pointing it out.