Posts made by FlareImp

@wayne-workman After trying to re-add the node I checked the log and it was empty. So I restarted the server and that’s what was in the log.

@wayne-workman Here is the log, I blocked out the IP Address and DNS name though.

[Mon Apr 16 07:35:01.869933 2018] [mpm_prefork:notice] [pid 2845] AH00163: Apache/2.4.33 (Ubuntu) OpenSSL/1.1.0h configured – resuming normal operations
[Mon Apr 16 07:35:01.869963 2018] [core:notice] [pid 2845] AH00094: Command line: ‘/usr/sbin/apache2’
[Mon Apr 16 10:44:13.433798 2018] [mpm_prefork:notice] [pid 2845] AH00169: caught SIGTERM, shutting down
[Mon Apr 16 10:45:25.108311 2018] [mpm_prefork:notice] [pid 2815] AH00163: Apache/2.4.33 (Ubuntu) OpenSSL/1.1.0h configured – resuming normal operations
[Mon Apr 16 10:45:25.140613 2018] [core:notice] [pid 2815] AH00094: Command line: ‘/usr/sbin/apache2’
[Mon Apr 16 10:46:37.034696 2018] [php7:warn] [pid 2823] [client 10.x.x.13:49926] PHP Warning: Division by zero in /var/www/html/fog/lib/fog/storagenode.class.php on line 315, referer: http://fogserver/fog/management/index.php
[Mon Apr 16 10:46:37.497480 2018] [php7:warn] [pid 2823] [client 10.x.x.13:49926] PHP Warning: Division by zero in /var/www/html/fog/lib/fog/storagenode.class.php on line 315, referer: http://fogserver/fog/management/index.php

My storage node is no longer shown under storage in the web GUI and when I try to re-add the node it says it already exists. I upgrade both the Node and the Server from 1.4.4 to .1.5.2.

OS: Ubuntu 16.04

Changing the file in:

/var/www/html/fog/service/ipxe/refind.conf

from:
scanfor internal,hdbios

to:
scanfor internal

seems to have taken care of the issue for the UEFI systems. Will that affect the BIOS systems though? I ask because I do not currently have one close by to test.

@tom-elliott That one says “scanfor internal,hdbios”

@tom-elliott I did not.

@tom-elliott it already says “scanfor internal”

@tom-elliott My apologies, the photo was too large.

I was running Fog 1.4.4 with no issues on BIOS and UEFI systems but after upgrading to 1.5.1, all my UEFI PXE booting devices are showing this error. I’ve changed nothing other than upgrading the Fog Version.


@george1421 Thank you very much! I was able to modify the script to fit our setup. Everything is working smoothly now.

Thanks again!

Feel free to laugh as I am new to scripting in Ubuntu. Currently, I am using a script in the PostDownloadScripts folder to copy drivers to our different models of computers after imaging them with our Master Image. We have our older computers that are using BIOS and are mounted to sda2 but our newer computers we have started installing are using UEFI which is on sda4. Right now I am changing the mapping in the script between “mount.ntfs-3g /dev/sda2 /ntfs” or “mount.ntfs-3g /dev/sda4 /ntfs” depending on what type of system I am imaging. Is there a way to get the script to auto determine this so I do not have to edit the script each time I change between the different types?

Thanks for any assistance ya’ll can offer me,

Fog 1.4.4
Ubuntu 16.04

Okay, still have no idea what caused the issue but I deleted the image on the server under the GUI and recreated it. Now my server is deploying the image just fine. Any ideas as to why? I did not change anything so I am at a loss.

@Tom-Elliott here is what I see after comparing the two. The left is the nonworking server and the right is the one it works on. The only thing I noticed is the size difference. Which is do to the fact that I tried recreating the “Master” image.

@Tom-Elliott I compared it to the directory on the fog server that the image works on and everything matches up. I even tried copying the image from the remote site that the image is working at rather than my office where I build the images and it does the same thing.

Yes, the name of the image is “Win7MasterNoIEV3” under “Image Name” and Image Path" under the image management GUI and under the image directory. I just copied pasted the name once the image directory was copied over. I have even tried hand typing it out and all upper and lower case matches perfectly.

Server

• FOG Version: 1.4.0 & 1.4.2
• OS: Ubuntu 16.04

Client

• Service Version:
• OS: Windows 7 Ent 64bit

Description

I recently installed a new server at one of our sites and have run into a problem after trying to deploy our image from the new server. When choosing a host and selecting deploy after reaching the PXE screen it displays the error “Unable to locate image store (/bin/fog.download)” The process I use is I create a “Master” image on a VM at my main office then using a flash drive to copy the image to all of our fog servers at our remote sites. I know the image is good because it worked at both my office and another site running Fog 1.4.0.
I have done this process for a few years now so I am unclear as to what is causing the problem. As stated, one server that the image DID work on is running Fog 1.4.0 but the server giving me issues I have tried using Fog 1.3.5, 1.4.0 and 1.4.2. All rights to the “/images/” directory are set to 777 and ownership is fog:root of the image. I have looked through the Forums but I was unable to find anything that has helped so far. Any assistance would be welcome!

Thanks,

@falko, The postdownloadscripts folder was syncing in Fog 1.2.0 but I noticed it stop once I changed over to 1.3.x. I never had to manually sync my drivers directory once it was placed on the Fog server. It auto populated onto the nodes for that site.

Server

• FOG Version: 1.3.5
• OS: Ubuntu 16.04

Client

• Service Version: 0.11.11
• OS: Windows 7 Ent. 64bit

Description

Since I upgraded to Fog 1.3.5 I notices that the “postdownloadscripts” folder is no longer replicating between my nodes since 1.3.x. This is an issue because this was the location where i was storing the Drivers and Programs for my clients after the Image process was complete. I have been trolling through the Forums and I found where a few people suggested making a dummy image and place your drivers in there. So I gave that a shot and it was only replicating files inside of the dummy image directory one tier deep, none of the folders or subfolders and files were being copied over. This wouldn’t be a huge issue if I didn’t have to manually sync the directorys on 20+ Fog Servers and Storage Nodes every time we change something. I’m sure there is a simple solution, I am just not seeing it.

Thanks for any assisstance.

@Tom-Elliott Awesome, thank you!