Posts made by thebrennan47

Case solved! Thanks again to both of y’all @george1421 @Wayne-Workman

@george1421 I have made the change you suggested, however I am still missing something it seems like. I noticed that when I re-run installfog.sh on the storage node, it marks DHCP configuration as ‘skipped’. I imagine this may be the problem. Is there a way to change this to set up the storage node up as a dhcp server?

We are trying to set this up in the same way our current system is set up, which is basically going to be a fog server plus 3-4 storage nodes. Each storage node handles the local area connections for its ~15 workers

@george1421 I ran it on the fog server after updating everything and that didn’t reset it. However I ran it on the storage node as well, and that does look to have helped

Thanks for the assistance with this!

@george1421

I found the following two config options on the fog configuration settings:

FOG_TFTP_HOST
FOG_WEB_HOST

And then on the storage node I verified that it has the correct IP for itself also.

I also edited the fogsettings and default.ipxe files to verify they also have the correct IP.

(I also went through the steps here: https://wiki.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address )

I have also verified that they can successfully ping one another

I am still seeing the following issues though

In the Home Page UI
Nothing shows up in the drop down for storage node disk usage.

Also, when I click on the graph section it opens a hardware information page that gives out the following error: “Invalid Server Information!”

On the fog configuration / settings page:
FN1 FOG Version: ("A valid database connection could not be made"1.4.3)

Still digging around trying to figure out what I am missing here. Any ideas?

Server

• FOG Version: 1.4.3
• OS: Ubuntu LTS 1.6.4

Client

• Service Version:
• OS: Windows 7

Description

After updating the IP Address of our fogserver, we can no longer load the disk usage graphs for our storaqe node. I have double checked that the fogsettings are updated on both machines to contain the new IP. I have also re-run the installfog script on both machines

Any ideas what I could be missing?

We have a new class of hardware and the version we have in production right now (Fog version 0.32) is not compatible. We are creating another server setup in parallel to test before we attempt to move everything over.

The storage node is currently set to also be the master node yes. We currently only have one. Once I get this working we plan on expanding further. The fog server is not currently on the same subnet. It is in a completely different building — I didn’t realize that might make a difference. I can definitely try that if it does

We are trying to use the storage node as the dhcp server. Below is the dhcpd.conf file contents

ddns-update-style none;

option domain-name "xyz.com";
option domain-name-servers ###.###.##.#,###.###.##.#;
option subnet-mask 255.255.255.0;

default-lease-time 2400;
max-lease-time 4800;

log-facility local7;

subnet 192.168.1.0 netmask 255.255.255.0 {
        range 192.168.1.50 192.168.1.100;
        option broadcast-address 192.168.1.255;
        option routers 192.168.1.1;
        include "/etc/dhcp/worker-reservations.conf";
        filename "pxelinux.0";
}

Server

• FOG Version: 1.4.3
• OS: Ubuntu LTS 16.04

Client

• Service Version:
• OS: Windows 7

Description

We are currently testing an upgrade to a new version of fog. I feel like I am getting close to up and running but have hit a few snags.

I have added a storage node, and it successfully connects to fog. (Graphs etc are showing up in the UI).

I have also added a local switch with a single host. On the host I have verified that PXE boot is the first option.

However, when I queue an upload task and manually reboot, I am getting nothing on the PXE boot screen. The single host is showing up as green in the UI, but I cannot ping it manually when logging into the fog server.

I have also verified the storage node is ping-able.

I am sure I am just missing something simple. Any ideas?

Server

• FOG Version: 1.4.3
• OS: 16.04 Server LTS

Client

• Service Version:
• OS:

Description

I am getting syntax errors when running the latest version of the install fog script.

Command:

sudo sh installfog.sh --help

62 : Syntax error: word unexpected (expecting “in”)

The following also failed:

sudo bash installfog.sh --help

25: syntax error near unexpected token ‘$’{/r’’

I imagine this script is supposed to be able to run as is? So I am assuming I am just missing something. I wanted to double check before I start tinkering with it

@george1421

We are not using NVMe or any SSD’s for that matter — so considering that would it be possible for us to stick with our current version of fog?

We want to avoid upsetting our production environment if at all possible

Server

• FOG Version: 0.32
• OS: Ubuntu 12.04

Client

• Service Version:
• OS: Windows 7 and 10

Description

My hosts are currently freezing during the fog boot menu. I am trying to get the initial image uploaded but cannot got past the issue in the logs below. (I have added pics)

It freeze with the following log entries:

acpi_walk_namespace failed
Could not find Carillo Ranch MCM device
uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executed

The last line that it hangs afterwards is:
kernel_thread_helper+0x6/0x10

I am using Dell Optiplex 7040 as the host machine. Is this not compatible?