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

Fog Client 0.9.11 - Cert?

Scheduled Pinned Locked Moved
FOG Problems
4
13
2.3k
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.
  • I
    ITCC
    last edited by Apr 14, 2016, 1:30 PM

    Getting the current error in FOG client

    0_1460640622077_upload-78636c11-8723-41b6-b6c9-705d5c45e268

    1 Reply Last reply Reply Quote 0
    • I
      ITSolutions Testers
      last edited by Apr 14, 2016, 1:36 PM

      Are you getting this on all machines or just this one?
      What version of FOG are you using(the number in the cloud)?

      1 Reply Last reply Reply Quote 0
      • I
        ITSolutions Testers
        last edited by Apr 14, 2016, 1:42 PM

        You could try running
        sudo ./installfog.sh --recreate-CA --recreate-keys

        Also forgot to ask is this a new install of FOG? Also is it a new image, I see it is on a VM?

        1 Reply Last reply Reply Quote 0
        • I
          ITCC
          last edited by Apr 14, 2016, 1:54 PM

          7166

          just looking into one machine at the moment due to new image, not a lot using new fog server.

          I 1 Reply Last reply Apr 14, 2016, 1:58 PM Reply Quote 0
          • I
            ITSolutions Testers @ITCC
            last edited by Apr 14, 2016, 1:58 PM

            @ITCC So this is your first image with the FOG client for testing? I would try the command I mentioned earlier and see if that helps. You can also try uninstalling and reinstalling the client to see if something went wrong in the install.

            1 Reply Last reply Reply Quote 0
            • I
              ITCC
              last edited by Apr 14, 2016, 2:07 PM

              it has been OK, not played for a week or so. come back and not working. using FOG server to deploy other machines (old images with new agent)

              Have completed the certs and it’s still an issue

              1 Reply Last reply Reply Quote 0
              • I
                ITCC
                last edited by Apr 14, 2016, 2:08 PM

                0_1460642909104_upload-0d4bdf38-4534-4963-bac0-cc49c07f91eb

                1 Reply Last reply Reply Quote 0
                • I
                  ITCC
                  last edited by Apr 14, 2016, 2:20 PM

                  reinstalled client in middle of deployment seemed to work. Will replace on image and try again.
                  also got the next ver so would need to complete anyway.

                  Thanks

                  1 Reply Last reply Reply Quote 0
                  • J
                    Joe Schmitt Senior Developer
                    last edited by Apr 14, 2016, 3:07 PM

                    @ITCC

                    The FOG client “locks” into the FOG server that is running when you install it. From the sounds of it, you are setting up a new FOG server and trying to making the clients use this new server, but they are still locked in to your old one. You can setup your new server so that is has the same identity as your old one; allowing the clients to seamlessly switch between the two. To do this, you would need to copy over your CA certs from your old server to the new one, and then use the --recreate-keys parameter (DO NOT USE --recreate-CA, this resets the identity of a server).

                    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.

                    1 Reply Last reply Reply Quote 2
                    • W
                      Wayne Workman
                      last edited by Wayne Workman Apr 14, 2016, 9:21 AM Apr 14, 2016, 3:21 PM

                      What @Jbob said has been outlined here for a few months: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_of_hosts_when_building_new_server

                      That’s probably one of our more important wiki articles.

                      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 1
                      • I
                        ITCC
                        last edited by Apr 14, 2016, 5:51 PM

                        this doesn’t get affected when upgrading FOG via SVN does it?

                        i have rolled back to before. on clients that have not been changed since new fog server i get this…


                        --------------------------------Authentication--------------------------------

                        14/04/2016 18:48 Client-Info Version: 0.9.12
                        14/04/2016 18:48 Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
                        14/04/2016 18:48 Data::RSA FOG Server CA cert found
                        14/04/2016 18:48 Middleware::Authentication Cert OK
                        14/04/2016 18:48 Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
                        14/04/2016 18:48 Middleware::Communication Response: Invalid security token
                        14/04/2016 18:48 Service Sleeping for 120 seconds

                        any advice?

                        1 Reply Last reply Reply Quote 0
                        • I
                          ITCC
                          last edited by Apr 14, 2016, 6:05 PM

                          I did some research and found the " reset encryption data" button in the host record. Click and fix. thanks guys !

                          1 Reply Last reply Reply Quote 0
                          • J
                            Joe Schmitt Senior Developer
                            last edited by Apr 14, 2016, 7:29 PM

                            @ITCC upgrading FOG will maintain its identity, so long as you don’t use --recreate-CA

                            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.

                            1 Reply Last reply Reply Quote 1
                            • 1 / 1
                            1 / 1
                            • First post
                              3/13
                              Last post

                            206

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project