This is fixed in 3406.

[quote=“Wayne Workman, post: 47472, member: 28155”]So literally you just put in the host serial and mac address and the dev server’s IP and that’s it?

That’s pretty sweet, I gotta say.[/quote]

yep, that’s all you have to do

What OS are you running FOG 1.1.2 on?

What do you mean by “Not booting client side” ? Can you give a specific error or a photo of the error?

I run FOG in a VM with 4 cores assigned, and 4 gigs of ram assigned.

I never see the CPU utilization go above 12% ish.

I’ll add that I had accidentally assigned 1 core recently on a new build (just forgot to set that) and ended up installing 32 bit Fedora 21 server. Just the web functionality was so slow, it was unacceptable. I ended up rebuilding after assigning the normal 4 cores, and all is well.

That’s just my experience.

I just decided to make the one that is working the master. The other two will still accept images and deploy them.

I’m not good at debugging init scripts. It seems that the init script claims a PID, but the PID never shows up in top on the ones that aren’t working. This is also evidenced when I do a stop of the FOGImageReplicator script, I get an error that says can’t kill PID 3325 (or whatever the PID is). If I do a stop again it says OK. So something isn’t firing right, but it’s not that big of a deal to me since one is working.

Thanks for all your work on this. Much improved over the last 6th months.

[quote=“Junkhacker, post: 47394, member: 21583”]if you upgrade to a development version, the “quick image” option will allow the imaging of non-registered hosts[/quote]

This is true. Capone is depreciated in the trunk versions and has been replaced with a better method, but I believe it works in 1.2.0

Ok so all working now, I used the latest kernel download and named the kernel via FTP bzimage and then copied that file and renamed bzimage to bzimage32, so the same kernel for both 64 32 bit which seems to work fine now. So that seems to be the issue sorted out so thanks to everyone who added a reply on this.

Regards

[quote=“sysadmininstalls, post: 47327, member: 28544”]this is the result of someone changing the image type to raw when it is not.
This was solved by switching the image type back to the correct option.[/quote]

Good deal.

Hello,

I restarted the service and now it works fine. Thanks you very much!!!

Solution:
sudo service FOGMulticastManager restart

No payment but I mean requesting the ability to do a :runas override

Clean up the snapinJobs/snapinTasks tables.

I pulled the updates with svn from the trunk directory and started the installer from the trunk/bin directory.

hmm…

Maybe try re-installing MySQL ?

Did someone change your MySQL password? What version of FOG is this?

This worked for me! Thank you.

Had MBR/GPT Partition

that worked like a charm! thank you very much.

Hi,

In my install : /opt/fog/.fogsettings

Regards,
Ch3i.

Adding to what Tom said
changing the storage node location Local

If the storage node location is local make sure it is mounted in /etc/fstab
example:
UUID=b2584c6a-dddd-4939-9f86-f77a816fad8a /media/images2 ext4 errors=remount-ro 0 0 Change the info on the web interface to reflect your new Storage Group, mine was local, so I just reused the same Ip, made sure the user, pass were set to one that matches a user on the Linux box with the same 777 permissions on the destination
example:
chmod -R 0777 /where/you/want/to/put/your/shit copy all the files from the original /images folder specifically /images/dev, /images/.mntcheck, /images/postdownloadscripts to the new location
example:
cp -rp /images/* /where/you/want/to/put/your/shit
##########################################################################
This is what worked for me to get rid of the

“Mounting File System…Failed”

problem I encountered after moving the storage node to a larger local disk
##########################################################################
4. Edit the /etc/exports file to reflect the new datastore location, don’t forget to copy the files over as mentioned above
example:
From:
/images
/images/dev
To:
/where/you/want/to/put/your/shit
/where/you/want/to/put/your/shit/dev

#save

#restart the service

service nfs-kernel-server restart

No problem. Glad to see it was resolved!

From my experience, when the menu reverts back to the main menu, it’s something to do with the boot file or the chain loading.

There are lots of threads and WiKi articles about chain loading. Past that, someone with more experience in this area would need to chime in. Check back here to see if others post.