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

Imaging Jobs Freezing

Scheduled Pinned Locked Moved Unsolved
FOG Problems
5
57
19.1k
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.
  • A
    atarone @Sebastian Roth
    last edited by Jun 15, 2017, 8:05 PM

    @Sebastian-Roth The deployments started freezing again with the new init.xz and the old one.

    Below are the screen captures you requested:

    ls -al Vertix
    total 9526116
    drwxrwxrwx 2 fog root 4096 Jun 15 11:07 .
    drwxrwxrwx 11 fog root 4096 Jun 15 11:07 …
    -rwxrwxrwx 1 root root 1 Jun 15 10:21 d1.fixed_size_partitions
    -rwxrwxrwx 1 root root 512 Jun 15 10:21 d1.mbr
    -rwxrwxrwx 1 root root 132 Jun 15 10:21 d1.minimum.partitions
    -rwxrwxrwx 1 root root 15 Jun 15 10:21 d1.original.fstypes
    -rwxrwxrwx 1 root root 0 Jun 15 10:21 d1.original.swapuuids
    -rwxrwxrwx 1 root root 9754708186 Jun 15 11:07 d1p1.img
    -rwxrwxrwx 1 root root 132 Jun 15 10:21 d1.partitions

    cat /images/Vertix/d1.partitions
    label: dos
    label-id: 0x708be90c
    device: /dev/sda
    unit: sectors

    /dev/sda1 : start= 63, size= 78134424, type=7, bootable

    cat /images/Vertix/d1.minimum.partitions
    label: dos
    label-id: 0x708be90c
    device: /dev/sda
    unit: sectors

    /dev/sda1 : start= 63, size= 24918072, type=7, bootable

    cat /images/Vertix/d1.fixed_size_partitions

    fogadmin@INC-FOG01:~$

    I think I have found part of it given this output. Please let me know.

    Thanks,

    Anthony

    S 1 Reply Last reply Jun 15, 2017, 8:20 PM Reply Quote 0
    • S
      Sebastian Roth Moderator @atarone
      last edited by Sebastian Roth Jun 15, 2017, 2:21 PM Jun 15, 2017, 8:20 PM

      @atarone said in Imaging Jobs Freezing:

      The deployments started freezing again with the new init.xz and the old one.

      Are you able to switch between virtual terminal one and two (as described earlier) when deployment freezes?

      The numbers in the outputs you posted look pretty ok to me. I can’t see where things are going wrong here yet.

      I think I have found part of it given this output. Please let me know.

      What do you mean by that?

      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

      A 1 Reply Last reply Jun 15, 2017, 8:24 PM Reply Quote 0
      • A
        atarone @Sebastian Roth
        last edited by Jun 15, 2017, 8:24 PM

        @Sebastian-Roth “I think I have found part of it given this output. Please let me know.” I though that last output capture being blank may have been a problem, but you said all looks good to you. I am unable to switch between the VTYs.

        Thanks,

        Anthony

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Jun 15, 2017, 8:31 PM

          @atarone said in Imaging Jobs Freezing:

          I am unable to switch between the VTYs.

          So the client really seems to fully freeze. What if you hit caps lock by the way. Does the LED on the keyboard change state when it hangs? Just want to make sure…

          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 Sebastian Roth Jun 15, 2017, 2:57 PM Jun 15, 2017, 8:57 PM

            As well, could you please try this: Boot the client into deploy task using the new init.xz as normal. As FOG starts to prepare the disk for imaging (before the blue partclone screen) switch to VT2 (Ctrl+Alt+F2) and run this command: tail -f /var/log/messages. Just let it sit there. You should see all (kernel) messages coming in. Maybe this will give us a hint on what’s causing the hang. Please take a picture and upload here.

            Unfortunately you can’t see when it freezes while you are in VT2 but you can run a ping from another machine to check if the client is still alive…

            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

            A 1 Reply Last reply Jun 20, 2017, 6:50 PM Reply Quote 0
            • A
              atarone @Sebastian Roth
              last edited by Jun 20, 2017, 6:50 PM

              @Sebastian-Roth Do you have a VT2 version for init_32.xe? I can only use the NCR and they are 32 bit.

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Sebastian Roth Jun 20, 2017, 1:38 PM Jun 20, 2017, 7:37 PM

                @atarone Yes, no problem. Find a fresh version of both 32 bit and 64 bit in the same place.

                @Tom-Elliott What do you think about adding a virtual terminal to the official initrds? Would this use too much resources on the clients for no reason?

                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 A 2 Replies Last reply Jun 20, 2017, 7:45 PM Reply Quote 0
                • T
                  Tom Elliott @Sebastian Roth
                  last edited by Jun 20, 2017, 7:45 PM

                  @Sebastian-Roth I don’t think it would. I think it’s just the access to those terminals can be rather limited, which is all the more reason I added the openssh utils. Anybody can remote in much easier than have a device that’s having issues right next to them the whole time.

                  Using the openssh elements of it all allow us (devs and what not) to remote in and ssh in to see the machine too.

                  Pair the postinit scripts with a means to associate the root password and you don’t even, fully, need debug mode to test things (though I’ll admit you’d be strained for time to get information).

                  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
                  • S
                    Sebastian Roth Moderator
                    last edited by Jun 20, 2017, 9:30 PM

                    @Tom-Elliott You are absolutely right about SSH being the more advanced method to get access to such a client. But in this case when network connection is lost or it actually freezes it’s quite handy I suppose. On the other hand, I see that we never ever had such a case yet. So maybe just leave it.

                    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
                    • A
                      atarone @Sebastian Roth
                      last edited by Jun 22, 2017, 7:00 PM

                      @Sebastian-Roth Thanks! What is the key combination to switch VTY lines? I am unable to switch them using CTRL-ALT-Fx or any other combination of those keys.

                      Thanks!

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by Jun 22, 2017, 8:03 PM

                        @atarone You mean you aren’t able to switch even when the imaging did not freeze yet? Yeah, Ctrl+Alt+Fx is the key…

                        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

                        A 1 Reply Last reply Jun 22, 2017, 8:24 PM Reply Quote 0
                        • A
                          atarone @Sebastian Roth
                          last edited by Jun 22, 2017, 8:24 PM

                          @Sebastian-Roth Correct. I am not able to switch when using CTRL-ALT-Fx.

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by Sebastian Roth Jun 22, 2017, 4:22 PM Jun 22, 2017, 8:48 PM

                            @atarone Before or after it freezes??

                            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

                            A 1 Reply Last reply Jun 27, 2017, 2:06 PM Reply Quote 0
                            • A
                              atarone @Sebastian Roth
                              last edited by Jun 27, 2017, 2:06 PM

                              @Sebastian-Roth
                              @Tom-Elliott

                              Yes before it freezes I am not able to switch. On another interesting note, I tried updating to the latest client and i get the error message below:

                              0_1498572351557_FOG ScreenShot.jpg

                              Could this be related?

                              Thanks,

                              Anthony

                              G 1 Reply Last reply Jun 27, 2017, 2:56 PM Reply Quote 0
                              • G
                                george1421 Moderator @atarone
                                last edited by Jun 27, 2017, 2:56 PM

                                @atarone This message is typically generated during an upload if/when someone mucks about with the linux user called fog. This is a service account that is owned by the FOG backend and should not be used for general system administration. If you happened to change this password or the installer got this account out of sync you will see the above error. I’m not saying that is your case, because what you have is a bit unique.

                                But I would start by inspecting the /opt/fog/.fogsettings file for the password, then make sure in the web gui that the storage node password matches. If they all do then connect to the fog server using a windows box ftp client. Use the user ID (fog) and password found in the .fogsettings file. Confirm that you can login.

                                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!

                                A 1 Reply Last reply Jun 27, 2017, 3:12 PM Reply Quote 0
                                • A
                                  atarone @george1421
                                  last edited by Jun 27, 2017, 3:12 PM

                                  @george1421 I confirmed the passwords and they do match. I can connect via a Windows FTP client, but when I run the update I still get the error listed below.

                                  Thanks,

                                  Anthony

                                  G 1 Reply Last reply Jun 27, 2017, 3:23 PM Reply Quote 0
                                  • G
                                    george1421 Moderator @atarone
                                    last edited by george1421 Jun 27, 2017, 9:23 AM Jun 27, 2017, 3:23 PM

                                    @atarone Well my last post was way off base, you are not capturing an image but just trying to update the client settings.

                                    There is another place the fog user account info is hidden in the fog settings under tftp server. I can’t say for absolute why this is there. I’m not saying that is your issue either. Its just strange why you have your root issue. I don’t think its related to updating the client settings.

                                    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 1
                                    • T
                                      Tom Elliott
                                      last edited by Jun 27, 2017, 4:01 PM

                                      The settings under TFTP Server is from the days of PXE Boot (plain and simple). These were used to define the TFTP Server and the fog username/password were used to upload the latest pxe file when tasking a client machine. This, then, was also used for updating the kernels. I just don’t have a logical way to achieve a more dynamic means of updating these things so these “settings” are now used during updating kernels.

                                      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

                                      A 1 Reply Last reply Jun 27, 2017, 5:32 PM Reply Quote 0
                                      • A
                                        atarone @Tom Elliott
                                        last edited by Jun 27, 2017, 5:32 PM

                                        @Tom-Elliott
                                        @george1421 Thank you for clarifying. I am still getting the same error message when I try to update the client. Is there some where else this password could be messed? I did install the latest FOG update, so I am at 1.4.4. I will try a deployment and let you know if I have any success.

                                        Thanks,

                                        Anthony

                                        A 1 Reply Last reply Jun 29, 2017, 1:32 PM Reply Quote 0
                                        • A
                                          atarone @atarone
                                          last edited by Jun 29, 2017, 1:32 PM

                                          @Tom-Elliott
                                          @george1421 after updating to the latest version the deployments to the NCR still fail. I am able to image PCs and laptops so I will just use a different solution for the NCRs and leave it at that. Thanks everyone for all of your help and assistance!

                                          Thanks,

                                          Anthony

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 3 / 3
                                          3 / 3
                                          • First post
                                            47/57
                                            Last post

                                          248

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project