Posts made by Tom Elliott

Don’t forget to restart the nfs services.

When you setup the task before uninstallation, did your systems start uploading their images?

I don’t know what else to suggest here.

I’d check your server and make sure NFS server is running.

Check your /etc/exports file to make sure it’s enabling the NFS Share to the correct shares.

NFS requires RPCBind to operate, so check that rpcbind service is running then make sure nfs server is running and/or can be started.

Ok,

For now I’ve removed the OS Association Field, and create new group menu from the submenu.include.php file, and for ease of use I moved submenu.include.php from:
{fogwebdir}/management/include/submenu.include.php
TO:
{fogwebdir}/commons/submenu.php

I’ll post this file and the updated:
{fogwebdir}/management/index.php

Also, I’ll post the GroupManagementPage.class.php file.

I’ll update my tarball as well with these changes so far.
Inventory of simple changes:

{fogwebdir}/management/index.php (just changed reference of submenu.include.php to submenu.php}
{fogwebdir}/commons/submenu.php (this file has OS Association removed from Group menu. Moved file from management/includes)
{fogwebdir}/lib/pages/GroupManagementPage.class.php (removed OS Association area, included parts for Image Association, and Removing hosts from membership field. Membership area, host names are links to edit host directly if needed.)

[url=“/_imported_xf_attachments/0/382_GroupManagementPage.class.php?:”]GroupManagementPage.class.php[/url][url=“/_imported_xf_attachments/0/383_submenu.php?:”]submenu.php[/url][url=“/_imported_xf_attachments/0/384_index.php?:”]index.php[/url]

I figured out the image association but I will not post the update until I work out the other sections a little bit. I think I’m getting to the point, that the only reason I have the includes folder is to reference these for the class building.

I hope you guys don’t mind the time as I am, as the true developers, working a full time job with all of this.

I’ve got a new kernel based on the core config for 3.10.7

I don’t have a lot of hardware to test on, so please test.

It can be downloaded from:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
OR
wget --no-check-certificate [url]http://mastacontrola.com/fogboot/kernel/bzImage[/url]

Then the next question is … Is /storage a raid system with a possible bad drive? I don’t know what else to check then and I’m sorry.

One last note,

If you do end up changing the /etc/exports file, make sure to restart the NFS server.

I think a simple:
/etc/init.d/nfs restart
will do the trick.

Does your fog server actually use /storage as the location for the images? Or is it the typical /images directory setup. If it’s /images, it’s trying to use your root system (120G) to store more than that worth of data which would fail. A bypass to that would be to move /images to /storage then link /storage/images to /images which could be done with->

mv /images /storage; ln -s /storage/images /

You wouldn’t have to make any configuration changes then. The other thing to check would be the /etc/exports file to see what your NFS system is trying to mount to store the image. My guess is it’s actually mounting /images even if your configuration is pointing to /storage

To fix that, you’d simply change the file reference to /storage and /storage/dev (assuming that’s how your system is setup)

Also check your .mntcheck files to see that they exist. They don’t actually contain information, but they need to be present. Make sure they exist by typing:

touch /images/.mntcheck; touch /images/dev/.mntcheck; touch /storage/.mntcheck /storage/dev/.mntcheck

chmod -R +x /images; chmod -R +x /storage

Of course remove the items you don’t need as I don’t know what your particular setup requires.

Then try again.

From the sounds of it, your storage node is full which would explain why it stops imaging at, very nearly, the same point every time. Maybe try adding some storage space, if you can, or add another storage node that has the space available on it.

Try this:

In FOG Configuration
Choose FOG Settings
Look for:
[FONT=Ubuntu][COLOR=#555555]FOG_QUEUESIZE and change the value there.[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#555555]Then, just to be on the safe side, go to your config file and make the change at:[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#555555]{fogwebdir}/commons/config.php[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#555555]Look for Like:[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#555555]QUEUESIZE and make the change there and save. You should be set to have more hosts imaging.[/COLOR][/FONT]

Alrighty then,

I finally got groups, sort of, working.

So it’s just like the old method for now where when you’re looking at the list of hosts, you can create your group and add systems to a group.

I can also add, under the group management icon, a link to create a new host directly from there. I haven’t, however (sorry guys) figured out how to add a host to a group from within the group management system. Though, if patient enough, I might be able to figure out a way to do so.

The Groups listing doesn’t display naturally. Simple fix, edit the css file. Open up:

{fogwebdir}/management/css/fog.css

Search for the line: action-box, there are 3 of them.

In the first line of action-box, there is a place that say’s, display: none

Set it to :

display: hidden

Then you’ll be good to go for creating and adding systems to groups the method we’re all used to.

I’ll update my fog package, but also post the changed file here as well. It’ll be a few for the tarball to be updated.

Inventory:

{fogwebdir}/management/css/fog.css
{fogwebdir}/lib/pages/GroupManagementPage.class.php

The GroupManagement part is fully working, but I wanted to give some semblance of operation in this. The membership options current work which didn’t even after I updated my fog.css file.

EDIT:
Tarball is up and running. I may need some help getting the Associative parts of Groups to work: e.g
Image
Snapins Add and Remove
Service Settings
AD
and Printers.

OS Association is there, but there really isn’t a need as we don’t need it for the hosts anymore. I’ll look into what else uses it and remove it as needed.

[url=“/_imported_xf_attachments/0/380_GroupManagementPage.class.php?:”]GroupManagementPage.class.php[/url][url=“/_imported_xf_attachments/0/381_fog.css?:”]fog.css[/url]

Can you try a system with a smaller image/partition table? Maybe even a different system altogether? This will let you know if it’s the system, or your fog server that can’t handle the issue.

Also, are you sure you have 1.2 T available? This sounds like your storage location is full.

Something odd looks to be happening. The Image File size says that it’s only 3.97 GB, but the data that’s being copied is 173.88 GB? Does that sound right to you? It looks like it’s copying the image file size (3.97GB) then aborting the upload because it’s reached the file size. What if you try creating a new image with Multiple Partition, All Disks Non-resizeable. Then assign that image to the machine, then try to upload?

so you have two tftp servers running on the same network?

So when the image is being uploaded/created, it tells you the size of the image upload. Is this Partition 2 the full size that it’s copying, or is there free space? Next question would be, what kind of Hard Drive is the 500 GB? Meaning, is it SATA/AHCI or SATA/IDE in the bios? Is it a Solid State, Solid State Hybrid, or regular Platter drive?

This is important, as through some of my testing, I’ve found that, especially hybrid SSD, actually causes my kernel to crash because it can’t open a solid read/write stream to the drive. It keeps hanging and will give this pigz error anywhere between 2 minutes, to 10 minutes into the image upload cycle.

I forget which file to edit would be, but you just need to add the line:

net stop “FOG Service”

Before the SAD2 tools start running.

Then after it’s complete, put in the same script:

shutdown -r -t 10

So that the system will reboot automatically after the install of the drivers are complete. This will prevent the FOG Service from restarting the system automatically.

Yes it could be the network. Not necessarily a network driver issue, but something is preventing the system from communicating with the FOG Server. On your alternate system, these aren’t occuring.

Is your Storage Node on a separate system?

What is the size of the image to be created? How much space is available to actually store the image?