#!db
-
I am seeing this also FYI
-
@Raymond-Bell Glad to know I’m not the only one.
-
@Wayne-Workman Is the node connecting to the main server? What’s in the config.class.php?
-
@Tom-Elliott I’ve looked at the config.class.php, it looks all correct.
What do you mean by connecting? FTP is working fine, it’s replicating.
Also as a side note, I’m sort of in disbelief that I didn’t include Apache errors nor MySQL errors… I’ll get those tomorrow morning.
-
@Wayne-Workman I think the exact connection you’re using in the config.class.php and that node connecting remotly to the main db using those connections.
Did this occur after a specific number of hosts? Meaning @Raymond-Bell have you checked all the same as well? What OS are you using @Raymond-Bell (I know @Wayne-Workman you’re using Fedora or Centos.)?
-
@Tom-Elliott For this setup, it’s all CentOS 7.
We have a little over 400 hosts at the moment (I ended up not doing that import earlier).
However, this is our 12th and 13th nodes, both installed today, both with this issue. Could it be the number of nodes breaking it?
-
@Wayne-Workman Unlikely, but I really don’t know. That’s why i ask to double verify the connection as it’s being used by the config.class.php and that same node. Maybe SELINUX? Maybe Firewall? I don’t know.
-
@Tom-Elliott I have firewall configured the same on all the nodes. SELinux is set as Permissive across the board.
-
@Tom-Elliott if this isn’t figured out by tomorrow morning, I’m going to pull whatever SVN is 8157 and see if that works tomorrow morning, which I am sure will work, and then I’'ll slowly iterate up through the revisions until I find where it breaks.
-
I’m unable to replicate this issue at home.
-
Tom figured out the problem was due to mis-matching storage node versions and main server version of fog. the main server is behind a little from the recent node installations. Tom was able to create a patch that solved the issue without me having to update the main server, it is working good.