Should be fixed in current. I’m no longer flushing all the output.

Registration works fine now - We’ve pointed the separate buildings DHCP 66 and 67 to the main fog server. Works.

@Tom-Elliott said:

What VM is FOG in? I may need to remote in once I get back from my appointment to see your issue. Right now, Wayne’s issue is not related to fog in any way. It is because he’s running a hyper-v VM and the systemd-udev is using all the cpu trying to set a file it can’t access.

Our two FOG servers are both physical boxes.

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

If the filesize a are the same this would explain why they where in defunct status. The commands run but have no work to perform. I believe the defuncts you’re seeing are simply because of this. If you’re daring you could delete one of the images from the annex node and restart the replicator on the master. Then check your bandwidth and see if things are happening.

Remoted in and fixed.

Issue is ubuntu had docroot of /var/www/ but really the files existed in /var/www/html. So the current was placed in /var/www/fog, but web was looking at /var/www/html/fog.

Fixed by removing /var/www/html/fog, moving /var/www/fog /var/www/html/fog, and creating a link from /var/www/html/fog to /var/www/fog.

Seeing as the problem of getting the boot menu was the problem of this posting, I’m solving this thread.

Please create a separate issue in regards to the registration problem. You can link back to this thread too so you don’t have to rewrite all the details. Just give the new posting a title that says (Using /dev/sda) Host Registration Hung or something like that.

Thanks as always Tom for the quick fix - all good now, this can be marked as solved.

Ref the Apache and php files error - think that was an additional symptom of the sed missing character.

Well… if we didn’t hear from him this morning, that probably means the FOG server stayed up all week. Thread solved.

not yet, been on the road will test when I get back on Monday

Hopefully things will be better, though I don’t have a good way to test. Please let me know. I changed up the logic a bit and made the taskqueue class use a try/catch statement too.

@Mark-Buteyn What is your internet connection speed (up and down)?

(Just trying to draw a connection here) Do you have known intermittent internet access issues? I’m pretty sure they are still using wget to pickup the kernels and inits. I wonder if we added a longer wait time for wget that would resolve (or at least mask) the issue.

@Wayne-Workman Thanks, I needed to change the time under General Settings. Thanks again! I think I’m golden now.

Peace!

@BlueTech said:

Also what with the changes to Fedora in regards to the package deploy and mariadb replacing mysql…

The installer takes care of that. 🙂

Fedora 21 used MySQL, while newer Fedora uses MariaDB, and MariaDB is what’s installed by the installer if it doesn’t detect anything present already.

One other thing that when you do that the documentation could with an overhaul. Seems to be all over the place.

What does that mean? Do you want to see a migration video?

@jonathanh Excellent. Glad to help!

Marking this issue resolved (or not, no option to…)

@FlowLive Hey that’s great to hear that someone can repeat my madness… 😓

@Wayne-Workman Le me see if I can clean it up a bit. I need to see if I can integrate what @Sebastian-Roth noted in this thread about using a logical to represent the fog server IP. I think I can make it work.

@Wayne-Workman Thanks Wayne… understood.

I do use the Location plugin for this very reason. I guess because it had worked in a previous trunk, I just assumed that the way I had it set up originally was how it worked. In any case, I can easily change this and put all the storage nodes in to the one storage group, making Sydney the Master node.

You can set this one as resolved.

@Tom-Elliott Thanks Tom. Just pulled and installed and it’s working for me too.

I went ahead and solved this. First, the issue wasn’t something FOG was, or wasn’t, doing. Second, the issue (as I understood it) was the host memory.

SUCCESS! I have successfully created and deployed the images for these machines in efi mode. Thank you for all the help!