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

FOG installation errors

Scheduled Pinned Locked Moved Solved
FOG Problems
4
54
9.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.
  • D
    Daniel Miller @TaTa
    last edited by Nov 12, 2019, 10:54 PM

    @TaTa hmm … weird. You might try using chpasswd instead of passwd. I think that is available in RHEL … maybe by default. If it is, in functions.sh#L1262, change:

    echo -e "$password\n$password" | passwd $username >>$workingdir/error_logs/fog_error_${version}.log 2>&1
    

    to

    echo -e "$username:$password" | chpasswd >>$workingdir/error_logs/fog_error_${version}.log 2>&1
    

    Don’t have a RHEL system handy to test it with, however.

    1 Reply Last reply Reply Quote 0
    • D
      Daniel Miller @TaTa
      last edited by Nov 13, 2019, 12:06 AM

      @TaTa Actually, what is the result of getenforce?

      Was searching around a bit and apparently, SELinux can cause some strange behavior…
      https://forums.fogproject.org/topic/6926/setting-up-fog-password-fails-on-clean-new-centos-7-install

      Instructions for setting SELinux to permissive or disabled can be found at https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

      T 1 Reply Last reply Nov 13, 2019, 3:23 PM Reply Quote 0
      • T
        TaTa @Daniel Miller
        last edited by TaTa Nov 13, 2019, 9:34 AM Nov 13, 2019, 3:23 PM

        @Daniel-Miller Thank you for your replies. I already set it to permissive. Changing line 1262 toecho -e "$username:$password" | chpasswd >>$workingdir/error_logs/fog_error_${version}.log 2>&1 solved setting up passsword issue for fogproject account.

        I went to update database schema but getting Database connection unavailable. It looks like mysqld is not starting. In /etc/my.cnf files (I can’t find /etc/mysql/my.cnf), socket is pointing to /var/lib/mysql/mysql.sock. I checked mysql.sock and the file exists.

        mysql -u root and mysql -u root -p gave me ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

        Trying to restart mysql gave me this error: Redirecting to /bin/systemctl restart mysql.service Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.

        D 1 Reply Last reply Nov 13, 2019, 3:50 PM Reply Quote 0
        • D
          Daniel Miller @TaTa
          last edited by Nov 13, 2019, 3:50 PM

          @TaTa I think your server config file should be at /etc/my.cnf.d/server.cnf.
          Can you post the output of systemctl status mysqld.service and journalctl -xe?

          1 Reply Last reply Reply Quote 0
          • T
            TaTa
            last edited by TaTa Nov 13, 2019, 10:38 AM Nov 13, 2019, 4:37 PM

            /etc/my.cnf.d/ exists but it contains no files.

            systemctl status mysqld.service
            ● mysqld.service - MySQL Server
               Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
               Active: activating (start) since Wed 2019-11-13 11:34:24 EST; 3s ago
                 Docs: man:mysqld(8)
                       http://dev.mysql.com/doc/refman/en/using-systemd.html
              Process: 44776 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
              Control: 44806 (mysqld)
               CGroup: /system.slice/mysqld.service
                       ├─44806 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid --skip...
                       └─44809 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid --skip...
            
            Nov 13 11:34:24 fogprodapp01 systemd[1]: Starting MySQL Server...
            
            
            -- Unit mysqld.service has failed.
            --
            -- The result is failed.
            Nov 13 11:35:30 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
            Nov 13 11:35:30 fogprodapp01 systemd[1]: mysqld.service failed.
            Nov 13 11:35:30 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
            Nov 13 11:35:30 fogprodapp01 systemd[1]: Stopped MySQL Server.
            -- Subject: Unit mysqld.service has finished shutting down
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has finished shutting down.
            Nov 13 11:35:30 fogprodapp01 systemd[1]: Starting MySQL Server...
            -- Subject: Unit mysqld.service has begun start-up
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has begun starting up.
            Nov 13 11:35:33 fogprodapp01 nrpe[45775]: warning: /etc/hosts.deny, line 13: missing newline or
            Nov 13 11:35:34 fogprodapp01 mysqld[45781]: Unable to determine if daemon is running: No such f
            Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service: control process exited, code=exited st
            Nov 13 11:35:34 fogprodapp01 systemd[1]: Failed to start MySQL Server.
            -- Subject: Unit mysqld.service has failed
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has failed.
            --
            -- The result is failed.
            Nov 13 11:35:34 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
            Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service failed.
            Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
            Nov 13 11:35:34 fogprodapp01 systemd[1]: Stopped MySQL Server.
            -- Subject: Unit mysqld.service has finished shutting down
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has finished shutting down.
            Nov 13 11:35:34 fogprodapp01 systemd[1]: Starting MySQL Server...
            -- Subject: Unit mysqld.service has begun start-up
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has begun starting up.
            [root@fogprodapp01 my.cnf.d]#
            [root@fogprodapp01 my.cnf.d]# clear
            [root@fogprodapp01 my.cnf.d]# journalctl -xe
            -- Subject: Unit mysqld.service has failed
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has failed.
            --
            -- The result is failed.
            Nov 13 11:36:00 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
            Nov 13 11:36:00 fogprodapp01 systemd[1]: mysqld.service failed.
            Nov 13 11:36:00 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
            Nov 13 11:36:00 fogprodapp01 systemd[1]: Stopped MySQL Server.
            -- Subject: Unit mysqld.service has finished shutting down
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has finished shutting down.
            Nov 13 11:36:00 fogprodapp01 systemd[1]: Starting MySQL Server...
            -- Subject: Unit mysqld.service has begun start-up
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has begun starting up.
            Nov 13 11:36:04 fogprodapp01 mysqld[46228]: Unable to determine if daemon is running: No such f
            Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service: control process exited, code=exited st
            Nov 13 11:36:04 fogprodapp01 systemd[1]: Failed to start MySQL Server.
            -- Subject: Unit mysqld.service has failed
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has failed.
            --
            -- The result is failed.
            Nov 13 11:36:04 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
            Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service failed.
            Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
            Nov 13 11:36:04 fogprodapp01 systemd[1]: Stopped MySQL Server.
            -- Subject: Unit mysqld.service has finished shutting down
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has finished shutting down.
            Nov 13 11:36:04 fogprodapp01 systemd[1]: Starting MySQL Server...
            -- Subject: Unit mysqld.service has begun start-up
            -- Defined-By: systemd
            -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
            --
            -- Unit mysqld.service has begun starting up.
            
            
            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Nov 13, 2019, 4:50 PM

              @TaTa There should be a log file somewhere in /var/log/mysql/error.log or similar. Please take a look to see why it doesn’t seem to properly start.

              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 1 Reply Last reply Nov 14, 2019, 2:43 PM Reply Quote 0
              • T
                TaTa @Sebastian Roth
                last edited by Nov 14, 2019, 2:43 PM

                @Sebastian-Roth Thank you for pointing me to the right direction. It was mysqld.pid file that was missing. I created it and re-ran the installation and reached to the point where it asks to update database schema but getting Schema Update Fail. Unable to update schema. I put in the same password during the installation where it asked “Is the MySQL password blank?”. I’m able to mysql -u root -p and put in that same password.

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by Nov 14, 2019, 4:16 PM

                  @TaTa said in FOG installation errors:

                  Schema Update Fail. Unable to update schema

                  Any more information you get about why it fails? Error logs?

                  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 1 Reply Last reply Nov 14, 2019, 8:20 PM Reply Quote 0
                  • T
                    TaTa @Sebastian Roth
                    last edited by Nov 14, 2019, 8:20 PM

                    @Sebastian-Roth No error in mysqld log.

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sebastian Roth Moderator
                      last edited by Nov 14, 2019, 10:00 PM

                      @TaTa What about Apache und PHP logs?

                      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 0
                      • D
                        Daniel Miller
                        last edited by Nov 14, 2019, 10:09 PM

                        You may also have a fog_schema_update_error.log someplace. It looks like schemaupdaterpage.page.php drops that if it encounters an error. I’m not entirely sure where it would drop it, however.

                        T 1 Reply Last reply Nov 14, 2019, 10:12 PM Reply Quote 0
                        • T
                          TaTa @Daniel Miller
                          last edited by Nov 14, 2019, 10:12 PM

                          @Daniel-Miller fog schema update or similar name does not exist in /var/log/fog. Could it be somewhere that I’m not aware of?

                          Tom ElliottT 1 Reply Last reply Nov 14, 2019, 10:36 PM Reply Quote 0
                          • Tom ElliottT
                            Tom Elliott @TaTa
                            last edited by Nov 14, 2019, 10:36 PM

                            @TaTa under /var/www/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

                            T 1 Reply Last reply Nov 15, 2019, 3:38 AM Reply Quote 0
                            • T
                              TaTa @Tom Elliott
                              last edited by TaTa Nov 14, 2019, 9:55 PM Nov 15, 2019, 3:38 AM

                              @Tom-Elliott Thank you Tom. It looks like password for fogstorage account password does not meet password policy requirement. Where do I go to change it? I searched in the forums and it looks like there is a fix for it by disabling password validation in mysql https://forums.fogproject.org/topic/11378/fog-show-me-blank-page-on-fresh-install-ubuntu-16-04/12. It would be more ideal if I can change it to a stronger password to meet password policy.

                              Update ID: 16
                              Database Error: Failed to query: Error: SQLSTATE[HY000]: General error: 1819 Your password does not satisfy the current policy requirements Error Message: Error Code: "HY000", Error Message: ["HY000",1819,"Your password does not satisfy the current policy requirements"], Debug: SQL: [58] CREATE USER 'fogstorage'@'%' IDENTIFIED BY 'fs30609984138'
                              Params:  0
                              
                              1 Reply Last reply Reply Quote 0
                              • T
                                TaTa
                                last edited by Nov 15, 2019, 3:34 PM

                                I took are of password policy issue but getting a new error

                                “HY000”,1396,“Operation CREATE USER failed for ‘fogstorage’@‘%’”]. It doesn’t look like empty hostname as ‘%’.

                                1 Reply Last reply Reply Quote 0
                                • T
                                  TaTa
                                  last edited by Nov 15, 2019, 4:32 PM

                                  I was able to go pass that stage by changing ‘%’ to localhost. I’m not sure if it does any harm. I’m getting “Storage Node Update Warning Unable to connect using ip, user, and/or password provided!” I confirmed that fogproject account has proper access to /images folder. Any thoughts?

                                  D 1 Reply Last reply Nov 15, 2019, 4:42 PM Reply Quote 0
                                  • D
                                    Daniel Miller @TaTa
                                    last edited by Nov 15, 2019, 4:42 PM

                                    @TaTa The % in the host attribute is the mysql wildcard. This indicates that the user account is allowed to login from any machine. Changing this to localhost means you can only log in from a connection mysql / mariadb explicitly identifies as localhost. Unfortunately, localhost isn’t the only possible identifier possible for a local connection, for example it could use 127.0.0.1, so it is possible that this configuration would deny connections initiated on the same machine, which would result in that storage node warning.

                                    T 1 Reply Last reply Nov 15, 2019, 4:55 PM Reply Quote 0
                                    • T
                                      TaTa @Daniel Miller
                                      last edited by Nov 15, 2019, 4:55 PM

                                      @Daniel-Miller mysql does not allow using the wildcard. How do i get around it? This might be related to freezing screen when clicking on “Create New Image” and “No master nodes available” when listing all images?

                                      D 1 Reply Last reply Nov 15, 2019, 5:12 PM Reply Quote 0
                                      • D
                                        Daniel Miller @TaTa
                                        last edited by Nov 15, 2019, 5:12 PM

                                        @TaTa What indicates to you that the wildcard is not allowed? See MySQL’s documentation on creating accounts. It would be helpful to see both the error message encountered as well as the output of select user,host from mysql.user;

                                        T 1 Reply Last reply Nov 15, 2019, 6:00 PM Reply Quote 0
                                        • T
                                          TaTa @Daniel Miller
                                          last edited by Nov 15, 2019, 6:00 PM

                                          @Daniel-Miller You are right. I checked my other fog server and it does have a wildcard but this one is localhost.

                                          i’m getting this error when creating one using the wildcard (after dropping fogstorage user).
                                          ERROR 1396 (HY000): Operation CREATE USER failed for ‘fogstorage’@‘%’

                                          ±--------------±--------------+
                                          | user | host |
                                          ±--------------±--------------+
                                          | root | [myserverIP |
                                          | fogstorage | localhost |
                                          | mysql.session | localhost |
                                          | mysql.sys | localhost |
                                          | root | localhost |
                                          ±--------------±--------------+

                                          D 1 Reply Last reply Nov 15, 2019, 7:01 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            23/54
                                            Last post

                                          217

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project