@tlyneyor said in Connection time out (4c0a6035): However unfortunately I am running through the imagine process and it is painfully slow. To the point where selecting the image and the group etc needed 3 or 4 attempts each, and it is currently downloading the image at around 50MB/min. It screams network issue to me, but there are no other network problems at all that I can see, and I have run another machine in the same switch with no latency or connectivity problems. That sounds like it could be a duplicate IP. You’ll get a ton of slowness and intermittent transmissions with a duplicate IP.

Can you confirm The FOG webgui is reachable On the switch where the target computer is: Ensure that spanning tree is configured for fast-STP or RSTP or place an unmanged switch between the target computer and the building switch.

@tom-elliott Wow, you’re awesome! We’re actually getting a new network because of E-Rate within the next month. I am logging your explanation/suggestions and will run this by the guys installing the switches. Thanks.

@Mike-Fahey As George said, the ACPI messages should be ok to ignore for now. About the CPU stall, find some posts from other users in the forums: https://forums.fogproject.org/topic/8918/fog-boot-to-fos-rcu_sched-self-detected-stall-on-cpu Not sure if this is the same issue. Please read through the whole post start to end and see if it helps.

@billabos I don’t fully understand your current system configuration. Will you do the following steps and show me the configuration as FOS sees it? Schedule another deploy session, but this time before you schedule it, tick the debug box then schedule the task. PXE boot the target computer, after a few enter key presses it will drop you to a linux command prompt. (these next two steps aren’t required but will make your life easier. From the FOS command prompt key in ip addr show and detect the IP address of the target computer. Set root’s password with passwd Just give it a simple password like hello. By doing this, it will allow you to connect to FOS using putty from a windows computer. It will make copy and pasting the next steps a bit easier. From the FOS command prompt key in lsblk This command will print out all of the block devices (storage media) that FOS sees. It will be interesting to know what FOS sees as your disk layout. Post the results back to this forum.

@tom-elliott I’ll try the update and see if that helps Issue #2. I’ll report back. I could easily see timing out being a lot of the issue. There are a lot of clients attached and a lot of nodes with several sites imaging. I’ll keep an eye on this and see if it settles down. Wayne mentioned that I needed to lengthen the check-in time for the clients too. Hopefully, that helps. Thanks!

@wayne-workman Thanks. I changed it to 15 minutes. I’ll see how that does.

@wayne-workman Thank you workman, I will read the Wiki page. Thanks again.

FOGPrep hasn’t really been needed, though it certainly didn’t hurt anything. It still exists, just not readily available. Sysprep is recommended, but also not necessarily required.

@quazz @george1421 well, disabling secure boot seemed to do it. Thank you sooo much for the help. I will continue on with the process and hopefully all goes well.

@nt_tech I’ll reply to myself! :) I dumped the database as a backup and used PHPMyAdmin to delete the first 1000 entries in the imaginglog table. It all works now! There was obviously a bad record somewhere in there that was breaking the report. As a side note, the imaging log issue was arrarently fixed. When I change the definition on a host is DOES NOT change the record of what was previously imaged…as it should be. Glad I upgraded. Brian

Fog version 1.5.4 Cent OS 7 php version 5.6.36

Found the problem, needed to disable TPM 2.0 security in the Bios prior to deployment. Tom

@Wayne-Workman No they are not

@tom-elliott for the installer?

@tom-elliott said in Replicated image not showing up under "List All Images": If your other node is a server in its own right, then this is to be expected. Images aren’t automatically populated in the database, each one requires a definition to be available. So replicating an image from one server to another is fine, but it doesn’t automatically populate the receiving server with the definition. oh, ok thanks.