Unable to use log viewer from interface
-
@Uncle-Frank I actually removed the async code as it was rather pointless to have. This is why those lines of code are removed. I’ve switched from async query to a prepare/execute/get_result.
I removed the async code for a few reasons.
-
It only ever operated on a single MySQL instance. Essentially there was absolutely no point in using async as we always had to wait for the single sql call to return data anyway.
-
Potential timing issues. Basically, it helps limit potential for a 0 id to return in that by the time the data was inserted it wouldn’t have been able to receive the id that was inserted this leaving it as 0 while in reality it just hadn’t returned by the time the insert code was referenced.
-
Prepared statements, while not currently setup properly, limit potential of sql injection attempts. While I am sanitizing input and output a great deal even without prepared statements, I think it helps better reduce the potential in case I missed something earlier in the scripts.
-
-
@Uncle-Frank yes, this ip 10.72.208.55 is one of the storage nodes and the 3.50 is my server. I was trying to connect to db on server manually, from the node.
-
They are different versions, because I updated the two nodes when the error started presenting itself.
-
But 10.7.3.50 or should it be 10.72.3.50 ???
-
@Uncle-Frank I typed it wrong, but all nodes show same error
ERROR 1045 (28000): Access denied for user ‘fogstorage’@‘XXX.XXX.XXX.XXX’ (using password: NO) -
The fogstorage user for MySQL ALWAYS requires a password. This password is randomly created by the installer and is issued when the db is instantiated. You can define this yourself of course. It is created with fogstorage@‘%’ meaning anybody can access this user regardless of the ip it’s coming from. % is MySQL is a wildcard character. The password that is created for this user is stored in fog configuration->fog settings->storage user ->password or very close to that direction.
-
@Hanz change the command so the -p is blank and enter the password when it prompts for the password. Otherwise it’s trying to connect to a database named whatever your password is. If you want the password inline do NOT put a space between the -p and wrap the password in quotes. For example
mysql -u fogstorage -p'fogstoragepassgere' -h 10.10.10.10 fog -
@Tom-Elliott Yes I’ve made sure the fogstorage password is correct on server as well as nodes. This problem didn’t arise until I updated to from version 4972…I don’t understand how any setting I have could affect this. I’ve also tried to manually assign privileges to the db on server by issuing (grant all privileges on fog.* to fogstorage@‘%’ identified by ‘(fogstorage password)’
-
@Hanz sry I didn’t c that last part…I’ve been doing it wrong apparently…will test.
mysql -u fogstorage -p’fogstorage password’ -h 10.72.3.50 fog yields
ERROR 1045 (28000): Access denied for user ‘fogstorage’@‘10.72.216.50’ (using password: YES)
-
@Hanz Server shows the following using fog database.
MariaDB [fog]> show grants FOR fogstorage;
±----------------------------------------------------------------------------------------------------------+
| Grants for fogstorage@% |
±----------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON . TO ‘fogstorage’@‘%’ IDENTIFIED BY PASSWORD ‘2690302A44883E0B71599B2B3D4687A11E9D4A6A’ |
| GRANT ALL PRIVILEGES ONfog. TO ‘fogstorage’@’%’ |
±----------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)I know the password is encrypted, but it is certainly correct via the WebUI
-
@Tom-Elliott What should I get when I enter it correctly :mysql -u fogstorage -p’fs*********’ -h 10.72.3.50 fog
-
Ok so the issue is with “MYSQL not currently running” is somehow fixed, must’'ve been resetting the fogstorage password. Not sure why SVN 4972 nodes weren’t affected.
However the issus with a page popping up with “There are no enabled storage nodes for this group” when clicking “Log Viewer” still exists. I’m currently running SVN 5036.
-
This should now be fixed. Sorry it took so long.
-
@Tom-Elliott Almost there actually…The errors mentioned are no longer present; however all nodes show options like server (ie. Multicast,Image/Snapin Replication etc.) and all present “no data to read” when chosen.
Thanks for the hard work, I’ve mentioned it before, but I feel it needs said again. I really appreciate your help.
