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

    Service Settings revert to "all unchecked"

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    5
    540
    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.
    • T
      Taspharel
      last edited by

      Hei.

      Yesterday I updated our Ubuntu 16.04 Server to FOG 1.5.2 - no errors during update.

      Since then, one of the computers that was imaged about a month ago keeps loosing the checked boxes in the “Service Settings” area of the hosts menu. As a consequence the log file on the client shows: The response module is disabled on the host - and the fog client doesn’t do its deeds.

      Curiously, one of the checked boxes stays checked, but which one keeps changing, I wasn’t able to find a pattern yet.

      The service settings are all set as required in the FOG Settings Menu, so those shouldnt overwrite anything.

      Tried repairing the FOG client, it is up to date - tried uninstalling and reinstalling - no change.

      For all the other computer in use, I haven’t found one so far that shows the same error - but I am afraid it might come back and bite me when I don’t expect it 🙂

      Anybody has an idea what could be wrong?

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • T
        Taspharel
        last edited by

        Solved by Tom Elliot as per this thread: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/7

        1 Reply Last reply Reply Quote 0
        • Wayne WorkmanW
          Wayne Workman @Taspharel
          last edited by

          @taspharel 1.5.2 has some problems with saving settings, there’s a few threads open about this. All I can say is sit tight for now.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott
            last edited by

            Is this on a host, or group? Can you give me a detailed, as much as possible, of how I can reproduce? If I can reproduce it reliably, I can usually fix it pretty quickly.

            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 0
            • T
              Taspharel
              last edited by

              Oh, I had a look around but somehow seemingly didnt use the right querys to find the other threads. Sorry.

              It is on a host, the host was registered long before 1.5.2 and the last imaging was done before 1.5.2 as well.

              Reproductability is the problem atm, no other host shows this behaviour. I was thinking about just re-imaging and hoping it would go away.

              Things we did do:

              • Delete Macs that werent from the main Network card.
              • Reset Encryption Data
              • Saved the settings without any boxes checked and then tried saving with boxes checked.

              But regarding what you wrote it seems its not in the communication part between fog and the fog-client right?

              Sorry, not much more I can give. Will hang tight, thanks for your great work.

              1 Reply Last reply Reply Quote 0
              • T
                Taspharel
                last edited by

                Solved by Tom Elliot as per this thread: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/7

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post

                263

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project