Storage Nodes not showing in GUI
-
Server
- FOG Version: 1.3.1-RC-6
- OS: Ubuntu
Client
- Service Version:
- OS:
Description
We have recently just updated from 1.3.0-RC-15 to 1.3.0 and when checking our storage nodes in the GUI it is showing that none exist. When we try to create our node it tells us that the node already exists. We have attempted to delete all nodes and recreate, create a new group with the same nodes. None of which has worked, when we create the new nodes and move into to storage nodes on the GUI nothing is present and nothing is showing in the group tab either. When we look in the MySQL database we see the existence of the node. In an attempt to solve we updated to 1.3.1-RC-6 still to no avail, any help would be greatly appreciated.
-
Remoted in today.
Found this is actually an unknown bug until now.
@SbrewerBAV uses a jailed FTP system and the ftppath was adjusted to use
/In the storage node, when a path was being received/set to the storage node, I was using the php command
rtrimto remove the right side trailing/if they were present, so I could present the path in a nicer method. This was removing the/as it was the only one present. As the imagepath and ftppath are required fields, it was returning the nodes as if they were invalid.I’ve updated @SbrewerBAV code base with a quick patch to fix this and have addressed this potential issue for the working-1.3.3 branch.
-
Something must be wrong in the DB. Get into MySQL via the CLI interface and run these queries, post the output here, use the code wrapping tool, it looks like this:
</>Change the passwords in the output before you post it here, to something like PASSWORD.select * from nfsGroups; select * from nfsGroupMembers; -
+------+--------------+------------------------------+ | ngID | ngName | ngDesc | +------+--------------+------------------------------+ | 1 | default | Auto generated fog nfs group | | 2 | troubleshoot | | +------+--------------+------------------------------+ 2 rows in set (0.01 sec) +-------+---------------+----------------------+-----------------+------------+---------------------+----------------------+------------+---------------+------------------+--------------+---------------+---------------+-------------------+---------+---------+--------+--------------+-----------------+------------+ | ngmID | ngmMemberName | ngmMemberDescription | ngmIsMasterNode | ngmGroupID | ngmRootPath | ngmSSLPath | ngmFTPPath | ngmMaxBitrate | ngmSnapinPath | ngmIsEnabled | ngmHostname | ngmMaxClients | ngmBandwidthLimit | ngmUser | ngmPass | ngmKey | ngmInterface | ngmGraphEnabled | ngmWebroot | +-------+---------------+----------------------+-----------------+------------+---------------------+----------------------+------------+---------------+------------------+--------------+---------------+---------------+-------------------+---------+---------+--------+--------------+-----------------+------------+ | 3 | media | | 1 | 1 | /mnt/pool/it/images | /opt/fog/snapins/ssl | | | /opt/fog/snapins | 1 | 10.228.255.10 | 100 | 0 | fog | * | eth0 | | /fog | | 4 | troubleshot | | 1 | 2 | /mnt/pool/it/images | /opt/fog/snapins/ssl | | | /opt/fog/snapins | 1 | 10.228.255.10 | 100 | 0 | fog | ****** | | eth0 | | /fog | +-------+---------------+----------------------+-----------------+------------+---------------------+----------------------+------------+---------------+------------------+--------------+---------------+---------------+-------------------+---------+---------+--------+--------------+-----------------+------------+ 2 rows in set (0.00 sec)Mod edited to use code box.
-
Are all your nodes updated to the same version? What do you mean not showing in the GUI? Under the dashboard page?
-
We were not aware that we would also have to update storage nodes, how would we go about fixing that issue?
-
@SbrewerBAV Would you select this page again, and then review the tail of the apache error log to see if there is anything of help there?
I’ve seen FOG do this if there is an error on the page or information coming from the database.
-
@SbrewerBAV said in Storage Nodes not showing in GUI:
We were not aware that we would also have to update storage nodes, how would we go about fixing that issue?
You update the storage nodes exactly the same way you updated the main server - with the latest fog installer. It’s the same steps.
-
@george1421 There are no errors that pop up when moving to the storage node space, im told when they went to change a setting on the storage node and they clicked save that was when it disappeared.(were updating the FTP path)
-
I’d really appreciate if you’re still around hitting me up in chat.
I can’t see WHY this would be happening and think remote session (if possible) or at least real time feedback would be really good.
-
Remoted in today.
Found this is actually an unknown bug until now.
@SbrewerBAV uses a jailed FTP system and the ftppath was adjusted to use
/In the storage node, when a path was being received/set to the storage node, I was using the php command
rtrimto remove the right side trailing/if they were present, so I could present the path in a nicer method. This was removing the/as it was the only one present. As the imagepath and ftppath are required fields, it was returning the nodes as if they were invalid.I’ve updated @SbrewerBAV code base with a quick patch to fix this and have addressed this potential issue for the working-1.3.3 branch.
-
@sbrewerbav said in Storage Nodes not showing in GUI:
@george1421 There are no errors that pop up when moving to the storage node space, im told when they went to change a setting on the storage node and they clicked save that was when it disappeared.(were updating the FTP path)
Same case here. I just update and the node disappear.
-
@doubleailes [Moderator note] Please start your own thread because this thread is over 8 months old and I’m sure your computing environment is not the same as the OP of this thread. In your thread, please include what version of FOG you are using on both the master node and storage node as well as what OS is used on the master node and storage node(s)
