1.5.9-RC2
bzImage Version: 4.19.123
bzImage32 Version: 4.19.123
is the result. the storage node is located at a different site than the master node. with a private connection between the sites. the funny thing is we rebuilt our server after we had a problem with our previous fog server. prior to its problem on the old server the node’s graph and kernel version was listed in the web ui. nothing in the network has been changed. there is no proxy server in the network
@Sebastian-Roth this is the response for the storage node.
@@general
4.18.0-193.14.2.el8_2.x86_64
GTIGFogServer.gtioh.com
Up: 5 days 0 hrs 22 mins Load: 0.00, 0.00, 0.00
GenuineIntel
4
Intel
Xeon CPU E5-2670 v3 @ 2.30GHz
2297.339
30720 KB
7.63 GiB
0.43 GiB
0.23 GiB
@@fs
703.79 GiB
303.69 GiB
400.11 GiB
@@nic
lo$$14448$$14448$$0$$0
ens192$$212545560632$$5067789639$$0$$2945
@@end
the storage node is working as we can capture and deploy from it. It’s just not showing in the web UI.
Hello
We recently setup a new fog master node and storage node. when I add the storage node to the management I get the following error
We can connect to the fog database from the storage node to the master node using the fogstorage user and password found in the /opt/fog/.fogsettings.
Both nodes are running 1.5.9-RC2 which is what the default fogproject.git pulled down. They are running Centos 8.
