Posts made by Wayne Workman

6 + the fog server, you need 7 ports minimum. I’d recommend none other than Cisco. And here’s a nice 8 port model: SG100D-08-NA Amazon and Newegg carries it. You might find one on ebay.

@eroldin at any rate, we greatly appreciate you trying to help out - we need more people helping out. If you find anything else, please do raise a new thread about it here.

@wattfun said in N00b_Here: Plz help! New Setup for a company imaging solution:

I have downloaded Centos 7 (not sure how to partition correctly) and Ubuntu 16.04

The default partitioning of Cent OS and Ubuntu are not ideal for FOG. Both crash when the root partition fills. There’s video in our CentOS 7 tutorial showing you how to partition it: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
For ubuntu, we have a video on Debian that applies to Ubuntu too. This video goes into great detail about Linux partitioning, and was created for newbies like yourself: https://wiki.fogproject.org/wiki/index.php?title=Debian_8 You can learn a ton about Linux partitioning by watching that.

@jackiejack said in How to use Snapin to shutdown computer:

Then when I check back my list of hosts tasks, I don’t see it listed

There’s different task lists. Look on the left of Task Management and go through all of those. Also - if the task has completed, then it will not be in any of those lists anymore.

@jackiejack It’s the one that says shutdown. There’s also the power management area for hosts that does the same thing. At my current job, I don’t have a FOG Server handy so I can’t go look, so I rely on memory while I’m at work to help out here on the forums. Just carefully read each of the advanced actions, and carefully look through the host’s menu. You’ll find it.

@wattfun said in N00b_Here: Plz help! New Setup for a company imaging solution:

VirtualBox w/Ubuntu 14.04

Please, use something newer than 14.04. There’s absolutely no reason to use 14.04 for a brand-new fog server, and I could list quit numerous reasons to use 16.04 (or anything newer for that matter). Go get a copy of 16.04 from here: https://www.ubuntu.com/download/server

@coxm said in Using FOG across 2 domains:

How can I stop the default FogSettings Active Directory settings impacting a specific host. Will the AD settings on the host be overwritten by FogSettings config?

How can I ensure that machines running fog images and fog client on the old domain (of which there are many) stay on that domain but that this single machine is on the new domain and doesn’t try to get auto switched back by fog?

We should first clarify - there are default AD settings that you can set in FOG, but the AD settings any particular host gets is defined on that individual host. What I’d recommend is putting in your new domain settings as the default so that new hosts get those values. Then as you are able, slowly change all the existing hosts to the new settings via groups.

If you don’t change a host’s domain settings, then it won’t get changed. Meaning imaging hosts with the old domain set on them will still use that info.

Also, you need to be extremely careful when using fog with hosts in multiple domains. Do not carelessly hit the save button when working with groups - validate the config before clicking save. Because if you save the incorrect domain settings onto hosts - fog will do what you told it to do - and there really won’t be any time to stop it.

@wattfun said in N00b_Here: Plz help! New Setup for a company imaging solution:

unless someone can recommend a better distro to use with a Fog setup

Ubuntu 16.04 for starters, the latest long-term-support version of Ubuntu.

Also, most likely you’re not having an IP problem but a NAT/Bridge problem on your laptop. What I’d recommend to you is finding an old computer to install FOG on, or to create a VM on a proper host like HyperV or VMware or Zen or KVM or something. If you use bare metal or a VM on a proper host, then any DHCP server you have on that subnet will treat it like any other host on the network and give it an IP - and you don’t have to fight with network settings.

@jackiejack Yep, that’s the one. Also, the immediate shutdown action will happen the next time the fog client on that host checks with the server. The default check-in sleep time is 30 seconds - so once you create an immediate action, it will begin happening anywhere from 0 to 30 seconds later. The minimum value for the sleep time is 30 seconds, even if you set it lower. So just be aware of that. People with thousands of deployed fog clients set the client sleep time higher - like 5 minutes, 15 minutes, or one hour - to reduce server load.

@jackiejack Don’t use snapins, use the shutdown command. It’s in the advanced commands section, right with image deployment/capture.

@tnotmotnotgwcrf You can network boot a PC without a disk.

I know a bit about mining concurrency - I hope you realize you’d run a negative ledger just in electricity bills alone if you tried to mine bitcoin or bitcoin cash or litecoin. The only one you even have a chance at with a conventional CPU right now is ripple.

That said, you must first create a script of some sort that does the mining you want and sends results to where you want. Once this is developed, you’d make that into either a postdownloadscript or a postimaging script. George wrote a pretty good tutorial on those here: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

Since this forum is focused on FOG and imaging, you’ll need to develop the scripts on your own unless someone here is willing to assist. Once you have that working, we can help you use postdownloadscripts or postimagingscripts.

@george1421 @joe-schmitt is that OEM example ok for the wiki? I thought there was licensing issues around that.

@f-kos said in Uploading Image Issues:

Kubuntu 14.04.5 and FOG version 1.2.

The latest stable release of FOG is 1.4.4 as of January 2018. Please either rebuild this box or update to the latest version of FOG. Here’s a reference on how to get the latest version: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG
FOG is supported by a volunteer community and we do not have the resources (nor desire) to support old versions of FOG. If you have any other problems, create a new thread please.

@sjensen Two questions initially:

• What version of FOG are you using?
• Any model numbers at all on the USB to Ethernet dongle?

@sebastian-roth said in CPU Usage high:

As well, post the contents of your /var/log/fog/fogscheduler.log here.

That log will be most important in this situation. Have logs moved? I remember them being inside /opt/fog/log ?

@sebastian-roth said in Cant PXE Boot = PXE-T01: File not Found:

So here is another reason to push for the next release.

I think we are ready for another RC.

@trebor said in two clients same image:

How do I delete those ‘old’ backups? How do I purge by MAC address?

I asked you to run some DB commands that would probably fix this. Give them a shot please.

@george1421 said in Location Plugin - enhancement of behavior:

Issues that will need to be addressed is location cidr addresses eclipsing other addresses.

Exactly, I thought about this too. And when there is overlap, as Joe said, we just pick the best match. If there’s a tie, just pick the first one in the tie.

@trebor You need to run the database maintenance commands found in the link below, and hopefully everything is solved for you:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

Also, as crazy as this might sound, we did have one community member find himself with two motherboards that infact had the exact same MAC addresses… (he sent them back to the manufacturer and got free replacements). In the off chance that this happened to you, check the MAC addresses to ensure they are different.

@lee-rowlett I see what your saying, and we should be able to associate multiple CIDRs for a node.

I’ve been looking at the database layout for locations and I’ve figured out how to do this. We add a CIDR field and add it to the composite primary key for the location table. This allows for a single storage node to have multiple locations associated with it - as long as each one has a different CIDR. Here’s my changes:

CREATE TABLE `location` (
       `lID` int(11) NOT NULL AUTO_INCREMENT,
       `lName` varchar(255) NOT NULL,
       `lDesc` longtext NOT NULL,
       `lStorageGroupID` int(11) NOT NULL,
       `lStorageNodeID` int(11) NOT NULL,
       `lCidr` varchar(50),
       `lCreatedBy` varchar(40) NOT NULL,
       `lCreatedTime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
       `lTftpEnabled` enum('0','1') NOT NULL,
       PRIMARY KEY (`lID`),
       UNIQUE KEY `index0` (`lID`),
       UNIQUE KEY `index1` (`lName`),
       UNIQUE KEY `index2` (`lStorageGroupID`,`lStorageNodeID`,`lCidr`)
     ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;

As you can see, there’s the new field lCidr that is optional. I’ve also added lCidr to the composite primary key. Next, I inserted some data:

insert into location(lName,lDesc,lStorageGroupID,lStorageNodeID,lCidr,lCreatedBy,lCreatedTime,lTftpEnabled) VALUES ('Floor2','None','1','1','10.0.1.0/24','wayne','2017-12-31 15:07:51','1');
insert into location(lName,lDesc,lStorageGroupID,lStorageNodeID,lCidr,lCreatedBy,lCreatedTime,lTftpEnabled) VALUES ('Floor1','None','1','1','10.0.2.0/24','wayne','2017-12-31 15:07:51','1');

And viola, I can create multiple locations for a single storage node as long as I give each location a different CIDR value:

MariaDB [fog]> select * from location;
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
| lID | lName  | lDesc | lStorageGroupID | lStorageNodeID | lCidr       | lCreatedBy | lCreatedTime        | lTftpEnabled |
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
|   3 | Floor2 | None  |               1 |              1 | 10.0.1.0/24 | wayne      | 2017-12-31 15:07:51 | 1            |
|   4 | Floor1 | None  |               1 |              1 | 10.0.2.0/24 | wayne      | 2017-12-31 15:07:51 | 1            |
+-----+--------+-------+-----------------+----------------+-------------+------------+---------------------+--------------+
2 rows in set (0.00 sec)

The above method I think would involve the least amount of work. It’s not normalized (but the entire fog database is not normalized already). The longer harder way would be to create a table just for CIDRs, and then create a Cidr-location-association table - which would require another screen for adding & associating them and would be more work. Not worth it to go that harder route IMO.