Storage ID 0 is not valid / A valid database connection could not be made

[Tom Elliott]

It’s seems it’s connecting to the db now, but we can’t seem to connect to the other nodes.

This might be due to two things.

I modified a function to help ensure the nodes are available before getting data. The () on the nodes tells me the main server is unable to request the other nodes’ urls. This might simply be because the isAvailable is using a connection timeout of 500 ms. Maybe this is just too short to see those servers? It worked fine in my testing, but my nodes are admittedly within the same network I am. To test this theory, please open up the file:

/var/www/fog/lib/fog/fogurlrequests.class.php.

At lines: 271 and 327.

Please make them read as:
$options[CURLOPT_CONNECTTIMEOUT_MS] = 2000;

I think maybe then you’ll start seeing data filling in these areas?

[Tom Elliott]

and I think that will fix for the unable to create the task issue for you too. (The changing the timeout to 2000 miliseconds).

[entr0py]

That might be the problem considering I don’t even have that file…

root@FOG-Virtual-Machine:/var/www/fog/lib/fog# ls -lsa quests
ls: cannot access quests: No such file or directory

Those are supposed to be asterisks for anything quests anything. I only have one file in the whole lib/fog directory with a newer date than August 13 2014…

[entr0py]

@Tom-Elliott

Nevermind… how about /var/www/html/fog/lib/fog

My bad.

[entr0py]

@Tom-Elliott

Upgraded to 6007 on both host and node, made the change you suggested and still nothing. Same routine.

I created another node with all the same settings, placed it in the same storage group, disabled the old node and enabled the new one and still nothing. If I select that storage group on the dashboard it shows 0/0/0 with and the node doesn’t show in the list either.

[Tom Elliott]

@entr0py your issue brought another partial issue for what I would call doubles. At one point the server only used /var/www/fog for ubuntu (this is usually set as a link now).

Please try running:
rm -rf /var/www/fog; ln -s /var/www/{html/,}fog

This should allow the server to see the files regardless of how you’re accessing the data (why you didn’t see fogurlrequests).

[Tom Elliott]

Remoted in and found that the server was in fairly funky state.

It is ubuntu 12.04, and while we typically recommend to update, this particular issue was simply due to ondrej attempting to install php 7, but the packages variable on fogsettings was pre-labelled as php 5. Removed the packages variable and php/apache on the node, updated the php version stored in the fogsettings, reinstalled ondrej, and re-ran installer .