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

    1.5.7 Does not capture correctly

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    11
    643
    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
      Tywyn
      last edited by Tywyn

      Hi,

      after having installed 1.5.7 with dnsmasq on a fresh system I registered a host and tried to capture it.

      Filesystem resize took a while but then the capture process started and next time I looked at the client it started to boot Windows. So I thought, everything is fine.

      Looking in the fog-gui unter “Tasks” it shows, that the task is marked as “in progress”.
      In “Images” the resprective image has a given “image size on client” of 17,91GB (which should be correct) and it says “Captured: invalid date”.

      In /images I cannot see the subfolder for that image. I just see the temporary-image-files for that host.

      total 9084220
      drwxrwxrwx 2 root       root       4096 Feb 11 09:14 .
      drwxrwxrwx 4 fogproject root       4096 Feb 11 08:54 ..
      -rwxrwxrwx 1 root       root          5 Feb 11 08:59 d1.fixed_size_partitions
      -rwxrwxrwx 1 root       root    1048576 Feb 11 09:06 d1.mbr
      -rwxrwxrwx 1 root       root        190 Feb 11 09:06 d1.minimum.partitions
      -rwxrwxrwx 1 root       root         15 Feb 11 08:59 d1.original.fstypes
      -rwxrwxrwx 1 root       root          0 Feb 11 08:59 d1.original.swapuuids
      -rwxrwxrwx 1 root       root        190 Feb 11 08:59 d1.partitions
      -rwxrwxrwx 1 root       root  456246853 Feb 11 09:06 d1p1.img
      -rwxrwxrwx 1 root       root 8844911814 Feb 11 09:14 d1p2.img
      

      Not sure, whether this is related to the problem. Just found in the apache errorlog:

      [Tue Feb 11 08:45:24.344438 2020] [core:notice] [pid 27814] AH00094: Command line: '/usr/sbin/apache2'
      [Tue Feb 11 08:53:07.049920 2020] [proxy_fcgi:error] [pid 27846] [client 10.203.128.10:32854] AH01071: Got error 'PHP message: PHP Warning:  Illegal offset type in /var/www/fog/lib/fog/fogmanagercontroller.class.php on line 296\n', referer: http://10.203.128.9/fog/management/index.php?node=host&sub=edit&id=1
      [Tue Feb 11 09:14:28.792096 2020] [proxy_fcgi:error] [pid 30994] [client 10.203.129.60:40948] AH01071: Got error 'PHP message: PHP Warning:  ftp_login(): Please specify the password. in /var/www/fog/lib/fog/fogftp.class.php on line 464\n'
      [Tue Feb 11 09:14:29.770421 2020] [proxy_fcgi:error] [pid 27844] [client 10.203.129.60:40950] AH01071: Got error 'PHP message: PHP Warning:  ftp_login(): Please specify the password. in /var/www/fog/lib/fog/fogftp.class.php on line 464\n'
      [Tue Feb 11 09:14:30.678660 2020] [proxy_fcgi:error] [pid 27821] [client 10.203.129.60:40952] AH01071: Got error 'PHP message: PHP Warning:  ftp_login(): Please specify the password. in /var/www/fog/lib/fog/fogftp.class.php on line 464\n'
      
      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        Will you look in /images/dev for a directory that matches the MAC address of the target computer you just captured? If its there then it appears that the linux service account fogproject is out of sync with the values stored in the web ui.

        Here is a tutorial that you should run through to resync all of the locations where that service account is defined to ensure the passwords are all correct.
        https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

        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!

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

          Worked through your instructions and in fact in the default storage part the fogproject password did not match.

          Maybe useful for debugging:
          Some parts of the password were the same, but 2 characters appeared to be Unicode characters. Unfortunately I did not take a screenshot to show what the password looked like.

          Four letters of the correct password are: \^S;
          I think, that in the incorrect password in the storage node, they were replaced by those unicode characters.

          Please let me know if you understand, what I mean.

          The capture-task worked in the end.

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @Tywyn
            last edited by george1421

            @Tywyn Thank you for the feedback. What is the native language (codepage) defined on the FOG server. I assume it isn’t us-english. This sounds like a flaw in the fog installer script we should probably have the developers look at. Its pretty late in the game to get it into the 1.5.8 release, but surely if its fixable will make it into the next release.

            It would be handy to know what it was set to vs what it should have been and what locations were incorrect. Was it just in the storage node configuration?

            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!

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

              @george1421 said in 1.5.7 Does not capture correctly:

              @Tywyn Thank you for the feedback. What is the native language (codepage) defined on the FOG server. I assume it isn’t us-english. This sounds like a flaw in the fog installer script we should probably have the developers look at. Its pretty late in the game to get it into the 1.5.8 release, but surely if its fixable will make it into the next release.

              It would be handy to know what it was set to vs what it should have been and what locations were incorrect. Was it just in the storage node configuration?

              LANG=de_DE.UTF-8

              Yes, just in the storage node config. In the tftp-server part it was correctly mapped.

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Tywyn
                last edited by

                @Tywyn said in 1.5.7 Does not capture correctly:

                LANG=de_DE.UTF-8
                Yes, just in the storage node config. In the tftp-server part it was correctly mapped.

                @Developers ??

                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!

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by

                  @Tywyn It would be really helpful if you’d remember some more detailed infos on this. What did the unicode characters look like?

                  @george1421 Without more details I am not even sure this is still an issue in latest dev-branch. You know that we have changed the random password generator since 1.5.7. Might be fixed already but I can’t be sure without more details.

                  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 Reply Quote 1
                  • T
                    Tywyn
                    last edited by

                    Maybe I have a snapshot before I went through the list to resync the credentials. Will check tomorrow, when I am back in the office.

                    1 Reply Last reply Reply Quote 1
                    • T
                      Tywyn @Sebastian Roth
                      last edited by

                      @Sebastian-Roth said in 1.5.7 Does not capture correctly:

                      @Tywyn It would be really helpful if you’d remember some more detailed infos on this. What did the unicode characters look like?

                      @george1421 Without more details I am not even sure this is still an issue in latest dev-branch. You know that we have changed the random password generator since 1.5.7. Might be fixed already but I can’t be sure without more details.

                      Bild Text

                      @Sebastian-Roth : Will send you the cleartext-password in a PN, if it helps to debug. Please let me know, if you need it.

                      In my previous posting I was wrong. The password in the storage section differed completely from the correct password.

                      BTW: Was not able to upload the png to the forum here, so I used an external Server: Message was: Fehler: Beim auswerten der Serverantwort ist etwas schiefgegangen. which may translate into Error: Something went wrong while evaluating the server answer.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @Tywyn Can’t make any sense of this so far. Maybe when you send me the password. But you said it was really different?!

                        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
                        • S
                          Sebastian Roth Moderator
                          last edited by

                          Thanks to @Tywyn who provided the initial password I was able to figure out why this happened. The installer uses the password to update the storage node setting in a way that is prone to a URL encoding issue. I have to admit I didn’t know base64 encoding can actually produce strings that can cause such a problem:

                          $ echo -n 'as~ja$j2niau83j2' | base64
                          YXN+amEkajJuaWF1ODNqMg==
                          

                          The + character is then miss-interpreted by the PHP code as space character and therefore breaking the base64 decoding of that string.

                          I just pushed a fix to dev-branch in hope if this fixing all cases that special characters could cause in that part of the code.

                          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
                          • First post
                            Last post

                          298

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project