1.5.0-RC-10 - Storage Nodes Displaying Incorrectly - "A valid database connection could not be made"

[Steveo]

This issue is encountered on the main screen under storage nodes

When entering the node - all details are offset.

I have blanked out the IP on the above screenshot. This replicated on 2 fresh installations. Am I missing something and this is a legitimate database issue or is this an interface issue?

[Wayne Workman]

@steveo said in 1.5.0-RC-10 - Storage Nodes Displaying Incorrectly - “A valid database connection could not be made”:

Am I missing something and this is a legitimate database issue or is this an interface issue?

It’s a legitimate issue, and plain enough. The storage nodes are unable to connect to the main fog database. This article has everything you need in it to get this fixed:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

From the storage nodes, try the remote tests under the “Manually Testing MySQL” section. The fogstorage password can be found in the web gui at: web gui -> fog configuration -> fog settings -> FOG Storage Nodes -> STORAGENODE MYSQLUSER and STORAGENODE MYSQLPASS respectively.

Using that information, and while on a storage node, you’d run a command. Say the storage user is fogstorage and the storagenode password is Password1 and the main fog server’s ip is 1.2.3.4 the command would look like this:
mysql -u fogstorage -pPassword1 -h 1.2.3.4 -D fog
Note that there is no space between the -p and the Password1, that is on purpose.

We don’t know what’s exactly wrong until you run the test though. Based on if that succeeds or fails determines what we look at next.

[Steveo]

@wayne-workman , Thank you for clarifying. After some confusion I finally managed to resolve this on my test hosts. I will now replicate the change on my original environment. (My database knowledge is to blame).

Maybe if I ask nicely, we could request that this error be made a little more intuitive within the interface? (The error statement itself caused a slight offset within the interface, which is corrected after fixing the error)

(Again, I blanked out the IP)

[Wayne Workman]

@steveo Cool, let us know if you need more help.

[Tom Elliott]

Marking solved as this was not a bug, it really was a valid db connection not being able to be made. (this means the storage nodes it was asking for could not communicate to the main server).