@wayne-workman, @george1421 it is possible if the uuid for these hosts are the same. Which rc 10 should fix.
Best posts made by Tom Elliott
-
RE: FOG thinks all servers are a single host.
-
RE: Windows 10 Drivers Not Copying
@uwpviolator I’m going to guess. The fact that you state it works for windows 7 kind of proves this is outside of something fog is actually doing. Not that we don’t want to help (I think you’re aware of this already), but we can’t fix other people’s “mishaps”. All we can do is provide, hopeful, workarounds.
-
RE: AD configs not applied
@eliaspereira please open the storage node in the GUI. It looks like the path you have for images is /mint/images. Is this correct? By default fog sets up in /images.
-
RE: Fog Replication Not working
@wayne-workman already known about and there’s a workaround fix for it somewhere around the forums. It has to do with replacing the plugin.class.php file
-
RE: Can't chainload past Fog menu (Boot hard drive) - HP zbook laptop
@wayne-workman three finger salute = CTRL+ALT+DELETE usually. Or at least in olden days.
-
RE: Error message when attempting to access fog
I’d also recommend following the information here.
Which should help you remove the extra kernels.
With the information you’ve given us however, it appears your total disk space is about 150GB?
Did you have a mount for /images? Your disk space is completely used up currently. This means mysql can’t write the lock files to actually initiate itself, and cannot perform and updates to the database. This is why you’re seeing the message.
I’d also take a look in your /images folder and remove any images you do not need anymore to help you out a little bit.
-
RE: FOG Client: Athentication Error: Unable to get token
@joe-schmitt This is indeed a server side error.
Basically it’s saying it cannot find your FOG Server’s private key, which is how it knows how to decrypt the information passed by the client.
Please re-run the FOG installer using the argument(s):
./installfog.sh -KY
You MUST NOT recreate the CA at this point as the client is already aware of it. The -K will simply recreate the missing private key using the current CA, and all should start working immediately.
-
RE: Database Install blank page
@trex please try the steps as outlined here.
https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy
-
RE: FOG is very slow to server kernel and init image
What version of fog are you running?
What BOOT file are you using? This sounds like you’re using pxelinux.0 still as that limited the network transfer to 10mbps (which would also cause high latency).
-
RE: FOG is very slow to server kernel and init image
@pberberian Are you connected to a switch, or a hub? This difference is significant.
-
RE: Pxe Input/output error
@sourceminer Please follow the information in this post:
https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy -
RE: FOG Service - Error Communicating with Client
I don’t think sharing a users’ database is necessary, and should not be done except in the most extreme of cases.
This particular issue is so miniscule, and finding the offending mac’s is so simple that sharing an entire database is not required.
At the most, if sharing any part of a DB IS required, should only get a copy of the hostMAC Table so you can find the current host requesting, and figure out the mac’s are being sent.
But even that’s not needed. The list of mac addresses being send is already visible:
00:09:0f:aa:00:01 98:e7:f4:f4:0a:5e e4:a7:a0:b6:55:26 00:09:0f:fe:00:01
The rest of the mac addresses are “invalid” and not counted towards the registered macs.
I’m fairly sure one of these 4 mac addresses has the “duplicate” host associated to it.
The SQL QUERY to use to see which hosts have which mac’s:
SELECT `hmHostID`,`hostID`,`hostName`,`hmMAC` FROM `hostMAC` LEFT OUTER JOIN `hosts` ON `hostMAC`.`hmHostID` = `hosts`.`hostID` WHERE `hmMAC` IN ('00:09:0f:aa:00:01','98:e7:f4:f4:0a:5e','e4:a7:a0:b6:55:26','00:09:0f:fe:00:01')\G
-
RE: FOG Service - Error Communicating with Client
Once you find the mac address that’s registered to a host other than the one requesting, you can blacklist the mac address by part or whole.
You would goto FOG Configuration Page->FOG Settings->Quick Reg, and something like Pending Mac Filters (I can’t see right now as what we’re working on is not able to view the fog settings currently.) I’ll update with the direct link as soon as I can.
-
RE: Upgraded an Existing Server to 1.4.4 and Now Interface is Very Slow and Chromium Images are not working
@rstockham23 To me it sounds like the image doesn’t exist on the nodes at /images/2018CloudReady.
Can you verify that the storage nodes you require to have this image actually have it?
-
RE: Deleting Image doesn't free up HDD space
@tesparza So the filesize on dashboard is displaying correctly?
-
RE: First time FOG Client installation - can't authenticate with server
@george1421 He’s referring to the autologout module, but you’re definitely not wrong.
@blkeller, duly noted. Updating the time restraints means updating the entry in SQL, not hard, and I can have that done fairly easily. Even not allowing the setting to hold on to anything less than 5 minutes isn’t too hard, though do I set it to 0 if it’s below 5? Just thoughts on how best to approach. I don’t think it should warrant an “error” to update the host because that field isn’t really necessary for normal imaging functions.
-
RE: Cant access management portal
@coxm The
/var/www/fog/lib/fog/config.class.php
DATABASE_PASSWORD line should look like:define('DATABASE_PASSWORD', '<whateveryourfogguipasswordishere>');
You may also need to edit the
/opt/fog/.fogsettings
line withsnmysqlpass=''
to:snmysqlpass='<whateveryourfogguipasswordishere>'
-
RE: FOG (RC12) Settings Exit Types (legacy, efi) will not be saved after change
Please try this SQL statement:
UPDATE `globalSettings` SET `settingCategory`='FOG Boot Settings' WHERE `settingKey` IN ('FOG_ADVANCED_MENU_LOGIN','FOG_EFI_BOOT_EXIT_TYPE','FOG_PXE_MENU_TIMEOUT','FOG_PXE_MENU_HIDDEN','FOG_PXE_ADVANCED','FOG_KEY_SEQUENCE','FOG_NO_MENU','FOG_BOOT_EXIT_TYPE','FOG_PXE_HIDDENMENU_TIMEOUT','FOG_IPXE_MAIN_COLOURS','FOG_IPXE_MAIN_CPAIRS','FOG_IPXE_MAIN_FALLBACK_CPAIRS','FOG_IPXE_VALID_HOST_COLOURS','FOG_IPXE_INVALID_HOST_COLOURS','FOG_IPXE_HOST_CPAIRS','FOG_IPXE_BG_FILE');
This should reset all those items to use the proper setting category. The problem with the ajax and the place you’re currently updating is because those fields are appearing outside of the “<form>” element. So when you click update, nothing is actually being sent to be updated. This should address those issues.
-
RE: Bandwidth Graph on Fog 1.4.4 for Ubuntu Server 16.04.3 doesn't seem to function
@n406c is it literally saying bandwitch.php or bandwidth.php?