Well,

I’d strongly recommend figuring out why. Eventually the machine will go down, whether you want it to or not. A storm could knock power out for hours, some jack— could hit a power pole with a garbage truck or something… and I’m willing to bet that none of us have more than some server-grade backup batteries that can hold out for hours…

It’s better to fix it now on YOUR time, rather than fix it later on CHANCE’s time.

I forgot to add if it helps that I upgraded fog 1.2.0 to 3318 via the Ubuntu terminal command, so this had an existing fog install working all be it the kernel problem I was having

How are replication tasks working? Nothing changed directly in how things transfer. The speed or lack of it sounds environmental more than something fog is doing or did.

I have found that often after an SVN update either the whole system or just the MySQL service require three restarts before it settles down. Like popping the lid off a pot of boiling pasta.

Having said that, my (Ubuntu 14.04.2 LTS) DEV server’s SVN3317 MySQL is misbehaving. hmm…

is it possible to change the name of my thread into “resolved”

Finally got a chance to get back to this!
Setting the usb nic flag doesn’t make a difference.

I went back to 1.2.0 …too much grief with the last couple of SVN’s for a live system! 🙂

Sorry, with the latest update of SVN 3316 it works.

Thank you!

We got it fixed. There was a permission issues on the folder that contains the image. Thanks for the help.

I believe the entire ISO is stored into RAM. So, you gotta have room for that plus space for running the OS and applications.

[quote=“Tom Elliott, post: 46238, member: 7271”]This is a well known problem, and I’ve tried everything I can think of to make it an asynchronous method caller. The jQuery isn’t what’s holding it up directly, rather the php methods are naturally blocking which is what’s causing the issue. I don’t know what I can do to make it better, but I’ve tried. Maybe somebody else knows of a better method.[/quote]

Thanks! I appreciate your efforts, for now I have just remedied the issue with jbsclm`s solution. Yes hopefully some day somebody will have a better method 🙂

Awesome.

I had the same problem just now.
The solution is to connect the host to the correct network.

Good luck!

BTW I’ve found FOG to be quite stable at rolling the kernel (bzImage and its ilk) backwards and forwards.

Now if I could bend Tom’s ear to add a feature to roll iPXE backwards and forwards too. 😉

No. It’s only written when you install.

Thanks. With the advanced boot configuration it works fine.

If somebody doesn´t want to search, here is my solution:

open /var/www and create a directory called (for example) isos put your isos into it go to advanced options an add your personal menu, for example

:MENU
menu
item --gap – ---------- My boot menu --------------
item Hirens Hirens Boot CD
item return go back
choose --default return --timeout 10000 target && goto ${target}

:Hirens
initrd [url]http://${fog-ip}/isos/hirens.iso[/url]
chain memdisk iso raw ||
goto MENU

:return
chain [url]http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac}[/url] ||
prompt
goto MENU

autoboot

Sweet thanks for the info.

mary,

verify if the [SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_PXE_IMAGE_DNSADDRESS has the dns address, I had the same issue and now itś downloading the main.cvd file. This configuration are in Fog setting -> TFTP Server[/COLOR][/FONT][/SIZE]

Ok I had to work on the MBR used FixParts and everything seems to be working now.

Fog web gui upload and check debug.
then start task when command line comes up type fixparts[space]/dev/sda
then y, w, y, fog [enter] until prompts it stops.

[SIZE=13px][FONT=arial][COLOR=#262626][code]fixparts <device>[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]y[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]w[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]y[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]fog[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626][Enter] 400 times[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]reboot[/code][/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626][/COLOR][/FONT][/SIZE]

The attachment you posted doesn’t work. So I can’t really help with whatever error you’re seeing. Please try posting the error again.

And, if you’re quick-registering hosts AND using the FOG client, then the computers will get named with the MAC address.

If you full-register a host AND use the FOG client, and then hit enter through every prompt, the computers will get named with the MAC address.

I’d highly suggest you don’t just blaze through registration. It’s there to make your life easier. FOG will name computers FOR YOU, and can join them to the domain FOR YOU if you simply give the host a proper name during registration, or give it a name later on in FOG’s web management console.