FOG Node setup issues
-
1.5.0-RC9 had some issues with storage nodes. I would update to 1.5.0-RC10 as it was just release yesterday and many improvements from RC9. Most of those issues were resolved in working branch and hence RC10 should resolve your issues. I had the same problem and those issues were resolved now.
-
ah thank you for that.
updated now and my main fog sees the node
but it still gives this message under the storage node disk usage drop down menu: “A valid database connection could not be made”@@general"
It must be a bug when reading for the kernal info. But i’m able to see the node’s disk useage correctly.http://fognodeIP/fog still shows error 500 but that might be by designed. in 1.2.0 it showed a small text message.
other than that. it’s replicating! thank you. solved!
-
I also had the valid database connection error which turned out to be a limit that I was hitting with mysql. Could be related and you could go into mysql and check to see if you are hitting that provided your credentials for your nodes are correct. It sounds like they are because replication is working.
Discussion about valid database connection
If you go into mysql, you could check by running the following command:
mysql> show variables like 'max_connections';that max value if it’s being hit will show in the following command:
mysql> show status like '%onn%';If the output of that is higher than the max connections then there is your problem. Read through the discussion and see if it can help what your dealing with.
-
Just realized your node is on 1.2 and your FOG server is on 1.5 RC10. I would update your storage node first if that’s an option. Many changes since 1.2
-
max connection is 151, show status has a current connetion of 37, max used connection of 1 and threads connected of 1. everything else is 0.
will read the other thread. both node and main server are 1.5.0-rc10.
thank you, you’ve been a big help.
-
@JGallo
(
image url)check this out. see that error under kernel? well it looks like the entire info is on the wrong row.
storage node name is right, the IP is right, the “a valid database…” message shouldn’t be there, so now the Kernal 3.13…" message is pushed down a row. uptime is on the wrong row. So i think it’s an bug in the php code somewhere. the node works and connects and replicates fine. I’ve checked the settings you mention and dont see an issue. -
Possibly could be a bug. Wouldn’t be the first time LOL. Curiously what browser are you on and what size screen are you on? If you try to narrow the window on super wide screen I have seen the dashboard get all weird so I usually keep the window expanded.
-
I would expect this to be resolved once the storage nodes version matches the fog server’s version, just as @JGallo suggested.
-
@nrg Please report back when you have all servers running the same FOG version.
-
@Wayne-Workman My main server was 1.5.0 RC9 and my node was 1.5.0 RC10 which is why it didn’t work. I did update my main server after Jgallo mentioned it and has resolved most of the issues.
I think the “(“A valid database connection could not be made” 1.5.0-RC-10)” might be a bug. I’ve found two other threads that mention the same thing but their solution didn’t work on my end. As long as the server is replicating, i’m all good.
please marked as solved thanks.
-
@nrg Marking this as solved then. For the database connection issue, open up another thread please.
