• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Unable to use log viewer from interface

Scheduled Pinned Locked Moved Solved
FOG Problems
5
33
10.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    Sebastian Roth Moderator
    last edited by Sebastian Roth Oct 21, 2015, 3:54 AM Oct 21, 2015, 7:57 AM

    @Hanz said:

    ERROR 2003 (HY000): Can’t connect to MySQL server on ‘10.7.3.50’ (113 “No route to host”)

    Maybe this is just a typo but the IP address is quiet different to all the others you mentioned here in this thread so far (10.7. instead of 10.72.). This could explain the “No route to host” error.

    ERROR 1045 (28000): Access denied for user ‘fogstorage’@‘10.72.208.55’ (using password: NO)

    Are you sure about using an empty or no password here? Make sure the login credentials are correct in /var/www/html/fog/lib/fog/Config.class.php

    They two nodes not working correctly are also missing the connection type= “MYSQL_ASYNC” line in /opt/fog/.fogsettings and line can’t be manually added, installer overwrites somehow.

    This file is only used/written by the installer script. FOG itself uses the above mentioned Config.class.php when connecting to the database. The MYSQLI_ASYNC setting missing on those two nodes might mean that the version checked out is older?? Edit: According to what Tom said the ASYNC stuff might be missing in a newer version. Please check to see if you are running different versions (it’s not a real problem I think - but it would explain the missing setting):

    cd /path/to/fog/trunk
    svn info
    ...
    Revision: xxxx
    ....
    

    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

    T H 2 Replies Last reply Oct 21, 2015, 9:33 AM Reply Quote 0
    • T
      Tom Elliott @Sebastian Roth
      last edited by Oct 21, 2015, 9:33 AM

      @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.

      1. 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.

      2. 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.

      3. 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.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 1
      • H
        Hanz @Sebastian Roth
        last edited by Oct 21, 2015, 12:32 PM

        @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.

        H 1 Reply Last reply Oct 21, 2015, 12:34 PM Reply Quote 0
        • H
          Hanz @Hanz
          last edited by Oct 21, 2015, 12:34 PM

          They are different versions, because I updated the two nodes when the error started presenting itself.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Oct 21, 2015, 5:42 PM

            But 10.7.3.50 or should it be 10.72.3.50 ???

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            H 1 Reply Last reply Oct 21, 2015, 5:56 PM Reply Quote 0
            • H
              Hanz @Sebastian Roth
              last edited by Oct 21, 2015, 5:56 PM

              @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)

              1 Reply Last reply Reply Quote 0
              • T
                Tom Elliott
                last edited by Oct 21, 2015, 8:11 PM

                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.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                H 1 Reply Last reply Oct 21, 2015, 9:09 PM Reply Quote 1
                • T
                  Tom Elliott @Hanz
                  last edited by Oct 21, 2015, 8:45 PM

                  @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

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  H 1 Reply Last reply Oct 21, 2015, 9:45 PM Reply Quote 0
                  • H
                    Hanz @Tom Elliott
                    last edited by Oct 21, 2015, 9:09 PM

                    @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)’

                    H 1 Reply Last reply Oct 21, 2015, 9:15 PM Reply Quote 0
                    • H
                      Hanz @Hanz
                      last edited by Oct 21, 2015, 9:15 PM

                      @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)

                      H 1 Reply Last reply Oct 21, 2015, 9:17 PM Reply Quote 0
                      • H
                        Hanz @Hanz
                        last edited by Oct 21, 2015, 9:17 PM

                        @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 ON fog.
                        TO ‘fogstorage’@’%’ |
                        ±----------------------------------------------------------------------------------------------------------+
                        2 rows in set (0.00 sec)

                        I know the password is encrypted, but it is certainly correct via the WebUI

                        1 Reply Last reply Reply Quote 0
                        • H
                          Hanz @Tom Elliott
                          last edited by Oct 21, 2015, 9:45 PM

                          @Tom-Elliott What should I get when I enter it correctly :mysql -u fogstorage -p’fs*********’ -h 10.72.3.50 fog

                          1 Reply Last reply Reply Quote 0
                          • H
                            Hanz
                            last edited by Oct 21, 2015, 10:45 PM

                            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.

                            1 Reply Last reply Reply Quote 0
                            • T
                              Tom Elliott
                              last edited by Oct 22, 2015, 3:15 AM

                              This should now be fixed. Sorry it took so long.

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                              H 1 Reply Last reply Oct 22, 2015, 4:04 AM Reply Quote 0
                              • H
                                Hanz @Tom Elliott
                                last edited by Oct 22, 2015, 4:04 AM

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • 1
                                • 2
                                • 2 / 2
                                2 / 2
                                • First post
                                  28/33
                                  Last post

                                161

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project