Hi All, having used fog in the past I had tools like “mem check” “fogwipe”, “hardisk check” and lots of others. I thought these were in snapins. Having taken over another Fog install I cant find any of the tools, is there something I should download? somewhere else i should look?
Posts made by Trev-lchs
-
Snapins are empty
-
RE: Cannot get iPXE to connect to FOG Server
@rav I was assuming you were setting this up on a windows network, with an Microsoft windows domain. So is your DHCP server a linux box then?
-
RE: Cannot get iPXE to connect to FOG Server
@rav Sorry Rav my experience is with windows servers Maybe @george1421 will be better equipped to help you with this one.
-
RE: Cannot get iPXE to connect to FOG Server
@rav https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence Hi Rav, follow this, but please add the fog server IP to option 66. Also if you have subnets to need to complete this on each subnet scope on the dhcp server, also if you have 2 DHCP servers you must do it on each one and on each subnet
-
RE: Cannot install a CA Certificate
@sebastian-roth OK I am just very stupid, My apologies everyone. However. this might be a great opportunity to help others. Please when installing the client, in the box that says Fog Server, make sure you clear the box (the word FogServer) and enter the IP of your Fog Server then click next. The easy thing to do is just click next on the install, that’s when you get the CA error as it has no idea where the fog server is.
-
RE: Cannot install a CA Certificate
@trev-lchs Sorry Sebastian, same issue with the latest one.
-
RE: Cannot install a CA Certificate
@sebastian-roth Thanks Sebastian I will give it a go.
-
RE: Cannot install a CA Certificate
@trev-lchs what I have done for now is kept using the old client (0.11.16) on the image i had in fog, this works perfectly. But if anyone knows what the fix is for the “Cannot install a CA Cert” that i have with client ver 0.12.0, that would be really very useful.
-
RE: Cannot get iPXE to connect to FOG Server
@rav Can I just please add, if you are setting it up for UEFI, you must when adding the DHCP option to the new policy, you must put the Fog IP address in Option 66. You might think you don’t need to, as you already have it in for the BIOS booting. But if you are adding a policy for UFEI you must add the fog server address into option 66 for tftp server, otherwise the UFEI client does not know where to get the IPXE.EFI file (or whichever file you specify in option 67) from.
This is not in the WIKI and is a step that is often missed. Especially by me.
-
RE: Fog shrinks partition to data size
@trev-lchs it appears this was a one off and subsequent installs have not had this issue. So this one can be written off as solved. Seems the resize NTFS partition failed to work one time.
-
Cannot install a CA Certificate
Hi All having upgraded fog to Ver 1.5.9 from version 1.5.4, trying install the smart installer for client Version 0.12.0 over client Version 0.11.16, it uninstalled the old client but then failed to install the new one with the error unable to install CA certificate. Thing is, the previous version of the client was working fine on 1.5.9, communication was all good… I should of stayed to my mantra of “if it isn’t broke don’t fix it”. Any help gratefully received.
-
RE: Upgrading fog 1.5.4 to 1.5.9 stable version using github
@george1421 Thanks George, i will leave well alone, I am a great believer in “if it isn’t broke don’t fix it”. Thanks for all your help with this.
-
RE: Upgrading fog 1.5.4 to 1.5.9 stable version using github
@george1421 HI George, yep that got me pasted that issue, still wanted to create a new password for Fogstorage because it had a blank password. It stated that this is common on versions prior to 1.5.8, but it liked the one it created and carried on with the install.
-
RE: Upgrading fog 1.5.4 to 1.5.9 stable version using github
@george1421 HI George I keep getting this error when running the install, it asked me at the start if i wanted to upgrade the following
*** Detected a potential need to reinstall apache and php files.
*** This will remove the /etc/php* and /etc/apache2* directories
*** and remove/purge the apache and php files from this system.
*** If you’re okay with this please type Y, anything else will
*** continue the installation, but may mean you will need to
*** remove the files later and make proper changes as
*** necessary. (Y/N):
ySo i agreed to this, then further down it asks for a new password for the database which i entered but it was not secure enough i guess and it gave me one it decided to use, once i took a note and pressed ok, I got this error below any advice? I have restored the server back to before i started the install so its all still working.
!!!
!! The installer was not able to run all the way to the end as !!
!! something has caused it to fail. The following few lines are !!
!! from the error log file which might help us figure out what’s !!
!! wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log !!
!! in /root/fogproject/bin/error_logs/fog_error_1.5.9.log !!
!!!Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
Failed to stop php7.1-fpm.service: Unit php7.1-fpm.service not loaded.
root@fog2:/root/fogproject/bin#I have just reposted this as i was replying to myself last time, which probably wont register on your notification?
-
Fog shrinks partition to data size
Weirdly, having imaged a system, the partition has been shrunk to just fit the data, we can extend the partition to fill the space, but what has caused this, is there a setting i don’t know about?
-
RE: Upgrading fog 1.5.4 to 1.5.9 stable version using github
@george1421 HI George I keep getting this error when running the install, it asked me at the start if i wanted to upgrade the following
*** Detected a potential need to reinstall apache and php files.
*** This will remove the /etc/php* and /etc/apache2* directories
*** and remove/purge the apache and php files from this system.
*** If you’re okay with this please type Y, anything else will
*** continue the installation, but may mean you will need to
*** remove the files later and make proper changes as
*** necessary. (Y/N):
ySo i agreed to this, then further down it asks for a new password for the database which i entered but it was not secure enough i guess and it gave me one it decided to use, once i took a note and pressed ok, I got this error below any advice? I have restored the server back to before i started the install so its all still working.
!!!
!! The installer was not able to run all the way to the end as !!
!! something has caused it to fail. The following few lines are !!
!! from the error log file which might help us figure out what’s !!
!! wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log !!
!! in /root/fogproject/bin/error_logs/fog_error_1.5.9.log !!
!!!Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
Failed to stop php7.1-fpm.service: Unit php7.1-fpm.service not loaded.
root@fog2:/root/fogproject/bin# -
RE: Upgrading fog 1.5.4 to 1.5.9 stable version using github
@george1421 Thanks again George, I will get right onto it.
-
Upgrading fog 1.5.4 to 1.5.9 stable version using github
I know this is probably a very simple thing if you are Linux Guru, unfortunately although I love fog, I am no Linux Guru, how do you do the above? we are also using ubuntu 16.04 which is probably older than time now. So can it be done and if so how?
-
RE: Network Boot Error
@trev-lchs that was the Ticket George, I just thought the config would go across to the fail over DHCP Server, live and learn eh. Thanks very much for your help