Well, you led me to the solution!

We have four different storage groups with their respective master nodes. In our ‘main’ group, we were retiring our server “fog1” and replacing it with “fog2.” Last night, I made the switch: I disabled “fog1” from master and set “fog2” to master on the ‘main’ group.

The issue wasn’t with those settings, but “fog2” still had “max clients” set to 0. Setting this to 10 fixed the issue. I had only looked at the configuration summary – which looked fine to me! (master node set correctly).

Thanks!

correct

Hi Tom,

Thanks for that! Adding the password to the correct config.php file was the ticket! I was able to do the schema update with only this (hopefully inconsequential) error:
[CODE]The following errors occured
Update ID: 36 - 5

Database Error:

Duplicate entry ‘400-28’ for key ‘gmHostID’
Database SQL:

ALTER TABLE fog.groupMembers ADD UNIQUE ( gmHostID, gmGroupID )[/CODE]

Thanks again!

Jeff

[COLOR=#555555] [/COLOR]

It was actually our image that was busted, so we’re good with imaging with multicast now! Sorry for the confusion, updating fog somehow made the image break.

I had a go on my failing system today, when I rename run.php to something else I get the problem back, i.e. no options for capone.
I’ve tried clearing the browser cache, on both Firefox on the server and ie8 on xp, and it makes no difference.
My home system is fine, I’ll try building a new one and see if I can reproduce the problem.

Just the one time, because you will upload this “now good” image and push that to your other hosts.

That’s correct, unless you tell it to image in raw format.

If you imported hosts, then it is most likely because the host modules are not set.

we have other systems that have a functioning ipxe environement. I’ll try to image the systems seperatly.

will report back

Hi,

When I changed the file to indionly.kkpxe it won’t start- doesn’t even get to the FOG menu…
I solved this problem by changing the [FONT=Ubuntu][COLOR=#555555]FOG_PXE_MENU_TIMEOUT value in the fog configuration menu-> FOG boot settings…[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#555555]Thanks for all the help[/COLOR][/FONT]

hello,
thank you for your quick response.
Ok this has resolved to worry.
I noticed that you could not change a field in printer management, host management, I feel that the update button does not work change.
You can not add a printer to a group, this is not reflected in the host.
thank you

Hello from France

apache error

root @ fog: ~ # tail-f / var/log/apache2/error.log
[Fri Jun 13 8:35:48 2014] [error] [client 192.168.1.68] PHP Warning: in_array () Expects parameter 2 to be array, null Given in / var / www / fog / service / servicemodule-active.php on line 41

root @ fog: ~ # cat / proc / version
Linux version 3.5.0-17-generic (buildd @ allspice) (gcc version of 4.7.2 (Ubuntu / Linaro 4.7.2-2ubuntu1)) # 28-Ubuntu SMP Tue 9 Oct 2012 7:31:23 p.m. UTC

fog subversion 1813
hello,
merci de votre rapidité d’intervention.
Ok cela a resolu se soucis.
J’ai remarqué que l’on ne pouvais pas modifié un champ dans printer management , host management, j’ai l’impression que le bouton update ne fonctionne pas en modification.
On ne peut pas non plus ajouter une imprimante à un groupe, ce n’est pas repercuté dans le host.
merci

Bonjour de France

I’m happy to test any of the kernels for the Dell 755/760/780 and provide feedback.

When you set the undionly.kpxe line up in dhcp, did you restart the dhcp service? This, of course, is assuming you’re using dhcpd.conf from linux, otherwise does you network use other DHCP information? Option 67 would likely be the culprit.

Thank you Tom! with
[CODE]sudo service FOGScheduler restart[/CODE]

it works fine now!
I had done it before but for some reason it did not work. Also I wonder why it did not work after many linux (different distros)/fog reinstallations.
Anyway, not it is OK!
Thank you again! 🙂

clear your browser cache

is the capacity on your hard drive is at 100% you should run this command to verify [B]df-h[/B] so if delete something to start mysql service[B] [/B]

Thanks for the quick feedback guys. Sorry I’m so delayed in responding, I’d already returned my test VM’s to snapshots and just hadn’t been able to return to this until yesterday.
1.1 seems to have resolved the issue for me. The nodes now behave as expected with regard to the ‘master’ setting. I’m hoping that this is something that was fixed in 1.1 and I’m not just losing my mind…

One other slight problem I’m seeing now:

The disk information does not display for the SN. It does work correctly for the default member.
If i click just below the ‘Failed to connect to’ text, I’m brought to a hardware info page which does contain the file system information I’d expect to see on the chart.

I’ve changed the FOG_BOOT_EXIT_TYPE to GRUB and the problem was solved!
Thank you very much for the support.

Ok. Well, it’s summertime here (which is when I actually use FOG the most) so it might get moved to an end of summer - after imaging or a middle of winter project. Thanks for the info.

[quote=“Tom Elliott, post: 29976, member: 7271”]What is the OS of the image?

What is the type of the image (raw, single disk, multi-part?)

It looks like the mbr or gpt tables aren’t being written back. At least not properly.[/quote]

I may have found something that fixes this.

I did a deploy-debug on both PC’s.

Then at the debug prompt:
# fdisk /dev/sda and then “w” to write it out
# fog

Both PC’s seems to be loading. Though I don’t know if this is one-time or I will need to manually do this every time I want to load these machines. Any ideas?

(got this from: [url]http://fogproject.org/forum/threads/partition-table-error.1234/#post-10305[/url] )