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

Storage Nodes Not Showing Up

Scheduled Pinned Locked Moved Solved
Bug Reports
3
8
721
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.
  • J
    Joe Gill
    last edited by Jun 10, 2019, 9:30 PM

    FOG Ver. – 1.5.6.4
    OS – CentOS Linux release 7.6.1810 (Core)

    I just migrated over from Debian 9.9 on a new FOG server build to CentOS. Everything is up and running except for multicasting. I was getting an error stating “Fog Server not Master Node”. I went through all of the config changes and updated all instances of username and password found in /opt/fog/.fogsettings file. When doing so, I noticed that the Fog Storage Node would not let me change the IP Address or username. It would say it updated but when I refreshed things it was not updating. I tried a different browser and the problem persisted. So I decided to delete the FOG storage node and re-add it. When I re-added it, the storage node never appeared in the list. I have rebooted the server and restarted all services with no luck in getting my storage node back.

    I don’t know if this is the appropriate place to post this or not. Please move this if it is not.

    Thanks!

    Cheers,

    Joe

    G 1 Reply Last reply Jun 10, 2019, 11:07 PM Reply Quote 0
    • G
      george1421 Moderator @Joe Gill
      last edited by Jun 10, 2019, 11:07 PM

      @Joe-Gill I don’t know if I have an answer for you on this one. I can tell you that only a full normal mode fog server in a storage group can be a multicaster. If you are running a mix mode where an other device other than a real fog server (with the dabase) is marked as a master node in a storage group, multicasting will not work. Also that ethernet adapter logical name must be defined for that master storage node.

      I’m not sure about what password you are changing or IP addresses. But as a test on one of these storage nodes rename the .fogsettings file to something else then rerun the installer. The installer will forget everything about the last install and ask you the questions over again, just reset that storage node as a new storage node pointing to your newly migrated master FOG server. That should be easier then messing with user ids and password on each storage node.

      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!

      J 1 Reply Last reply Jun 10, 2019, 11:19 PM Reply Quote 1
      • J
        Joe Gill @george1421
        last edited by Jun 10, 2019, 11:19 PM

        @george1421

        Thanks George! I’ll give that try and re-post results. I know it has to be something simple. I just can’t wrap my head around it.

        J 1 Reply Last reply Jun 11, 2019, 2:23 PM Reply Quote 0
        • J
          Joe Gill @Joe Gill
          last edited by Jun 11, 2019, 2:23 PM

          @george1421
          @Tom-Elliott

          Well I removed .fogsettings file and re-ran the installer. This made no difference on the FOG settings. I removed FOG entirely (minus my images). Re-ran the installer and re-migrated my DB over to the new install and my storage node came back. As a test, I tried adding a new storage node (not as a master) and it still would not allow me to add any new storage nodes or make changes to my existing storage node.

          Any suggestions is greatly appreciated!

          Thanks!

          J 1 Reply Last reply Jun 11, 2019, 7:29 PM Reply Quote 0
          • J
            Joe Gill @Joe Gill
            last edited by Jun 11, 2019, 7:29 PM

            @Developers

            Any ideas here?

            Thanks!

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Jun 11, 2019, 10:25 PM

              @Joe-Gill In the other topic I suggested you run the database maintenance stuff. Did you do that yet?

              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

              J 1 Reply Last reply Jun 11, 2019, 10:26 PM Reply Quote 0
              • J
                Joe Gill @Sebastian Roth
                last edited by Jun 11, 2019, 10:26 PM

                @Sebastian-Roth

                Yes I did. It didn’t help any.

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by Jun 11, 2019, 11:22 PM

                  In a remote session we figured out that the database schema version was kind of oddly set. Still not sure why that was. Fixed that and applied the last couple of schema changes. That fixed a couple of odd issues including the Storage Node setting changes that can be done now again.

                  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
                  • 1 / 1
                  1 / 1
                  • First post
                    2/8
                    Last post

                  203

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project