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

Unable to register and inventory new Dell PCs

Scheduled Pinned Locked Moved Solved
FOG Problems
6
45
18.2k
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.
  • W
    Wayne Workman @Sebastian Roth
    last edited by Feb 23, 2016, 10:42 PM

    @Sebastian-Roth So do the new inits work?

    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
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth Feb 23, 2016, 5:24 PM Feb 23, 2016, 11:23 PM

      @Wayne-Workman Absolutely. We just couldn’t make them work on the old 1.2.0 server. So he installed a new machine with FOG trunk and WHOOOSH the Latitude 3470 went through registering like a charm… Only sad that it took me so long to see that he’s using 1.2.0 as it is noted in the OP.

      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 1
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth Aug 6, 2023, 3:28 PM Feb 24, 2016, 10:53 AM

        Adding some more information for later references. Output of lspci -nn | grep Ethernet shows (notice PCI ID and revision):

        02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
        

        Looking at dmesg | grep r81 I first thought the NIC is not working because we didn’t have the correct firmware binaries included. BUT it turned out that the NIC was working even without the correct firmware loaded. Possibly not fully functional/speed - I don’t know. Tom added the firmware binary to the current kernel anyway - error disappeared. Here is the dmesg output:

        r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
        r8169 0000:02:00.0 eth0: RTL8168g/8111g at 0xffffc90000062000, 20:47:47:47:bd:76, XID 0c000800 IRQ 273
        r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
        r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
        r8169 0000:02:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)

        To get all these outputs and doing all the testing we booted the ISO file I created some weeks ago (see here or search the forums for ‘grub-mkrescue’). Worked on the first try and was really helpful in this case. I guess we might want to look into adding this to the wiki as well as George’s great posts on creating the USB FOG OS Live (FOSL)?!?

        Edit: Ok, I think here would be a good start: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FOG
        Should we add Troubleshoot_Boot (which would include iPXE, kernel and init boot)?? I do find scattered information (@Wayne-Workman reminds me on the scattered info on ISC-DHCP settings) on booting process, PXE, iPXE and there is probably a lot more. For example: https://wiki.fogproject.org/wiki/index.php?title=Knowledge_Base#Troubleshooting
        But I couldn’t find anything on how to debug the whole booting process. Maybe this is just too complex and every situation is different. So it’s better to handle in the forums?? Comments?

        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 W 2 Replies Last reply Feb 24, 2016, 11:57 AM Reply Quote 0
        • T
          Tom Elliott @Sebastian Roth
          last edited by Feb 24, 2016, 11:57 AM

          @Sebastian-Roth I think a wiki article on what to do for troubleshooting may be useful.

          I’m also looking at the kernel source. While, for a period of time, the native firmware directory seemed to be missing the firmware files for some nic’s, it appears they are now there (and I don’t know for how long they have been there.

          I’m going to attempt building a kernel without the linux-firmware directory I’ve been using for so long in hopes that it may fix the loading issue (maybe it wasn’t ever really needed)?

          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

          S 1 Reply Last reply Feb 24, 2016, 12:02 PM Reply Quote 1
          • S
            Sebastian Roth Moderator @Tom Elliott
            last edited by Sebastian Roth Feb 24, 2016, 6:04 AM Feb 24, 2016, 12:02 PM

            @Tom-Elliott said:

            I’m going to attempt building a kernel without the linux-firmware directory I’ve been using for so long in hopes that it may fix the loading issue (maybe it wasn’t ever really needed)?

            I really don’t think you should remove all the firmware from the kernel you build!! Which loading issue you mean? The error I posted below? That error went away as soon as I added that particular firmware file to CONFIG_EXTRA_FIRMWARE! I am pretty sure there are some NICs which just won’t work without the firmware binaries. Please think twice before removing them.

            I edited my last post to make clear that the error went away when adding the correct firmware to the kernel.

            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
            • W
              Wayne Workman @Sebastian Roth
              last edited by Wayne Workman Feb 24, 2016, 9:31 AM Feb 24, 2016, 3:31 PM

              @Sebastian-Roth said:

              I do find scattered information (@Wayne-Workman reminds me on the scattered info on ISC-DHCP settings) on booting process, PXE, iPXE and there is probably a lot more. For example: https://wiki.fogproject.org

              We have a lot of articles that are scattered. I’ll try to at least get the DHCP stuff linked together right now and list all these other articles on the main troubleshooting page.

              My main problem with all these other articles is that I’m not sure if they are sound or not. They were created back when the wiki was open to all - so the quality may be questionable.

              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/

              S 1 Reply Last reply Feb 24, 2016, 5:39 PM Reply Quote 0
              • S
                Sebastian Roth Moderator @Wayne Workman
                last edited by Feb 24, 2016, 5:39 PM

                @Wayne-Workman said:

                main problem with all these other articles is that I’m not sure if they are sound or not.

                Good point! As well there is a lot of pre 1.2.0 stuff in some of the articles which I suspect is more confusing than helping anyone (people who still run 0.32 either know what they do or just don’t care anyway). The best thing to do would be to get together two or three people and do some kind of review. Do you think we could get together with @Tom-Elliott on a chat and start sorting through the wiki?

                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

                W M 2 Replies Last reply Feb 24, 2016, 6:23 PM Reply Quote 0
                • W
                  Wayne Workman @Sebastian Roth
                  last edited by Feb 24, 2016, 6:23 PM

                  @Sebastian-Roth said:

                  The best thing to do would be to get together two or three people and do some kind of review. Do you think we could get together with @Tom-Elliott on a chat and start sorting through the wiki?

                  We need to. It needs to be organized like a book - everything in the contents. The search engine is the index.

                  Old stuff needs to be labeled “OLD” or even removed. I started a list in our secret area already.

                  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
                  • M
                    mattyb @Sebastian Roth
                    last edited by Feb 25, 2016, 4:31 PM

                    @Sebastian-Roth I would like to thank Sebastian for his time in helping me diagnose this issue. We spent a substantial amount of time working through the issue and I learned a lot through the process! We are working through uploading images for these two machines as I type and all appears to be going well now that I’m on the Trunk version.

                    M 1 Reply Last reply Feb 25, 2016, 5:21 PM Reply Quote 1
                    • M
                      mattyb @mattyb
                      last edited by Feb 25, 2016, 5:21 PM

                      I’m getting the Trunk-specific database error when uploading an image (same as referenced in the WIKI here. I’ve checked all four locations for the correct username/password combination and it’s correct. I’ve checked the filesystem of the new FOG server that Sebastian walked me through, and it’s the correct EXT4. Username ‘Root’ has seems to have the proper system access to the image directory that it needs based on the result of the ls -laR /images command.

                      W 1 Reply Last reply Feb 25, 2016, 5:43 PM Reply Quote 0
                      • W
                        Wayne Workman @mattyb
                        last edited by Wayne Workman Feb 25, 2016, 11:43 AM Feb 25, 2016, 5:43 PM

                        @mattyb said:

                        Username ‘Root’ has seems to have the proper system access to the image directory that it needs based on the result of the ls -laR /images command.

                        The username that is used in all of the credentials you checked must have system access to the image directory.

                        Can you try to log into the server via FTP using the credentials you confirmed? There are examples of how to do this towards the top of that article. Do it from a remote computer - not from the fog 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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        M 1 Reply Last reply Feb 25, 2016, 6:02 PM Reply Quote 0
                        • M
                          mattyb @Wayne Workman
                          last edited by Feb 25, 2016, 6:02 PM

                          @Wayne-Workman Logging in to ftp://<IP> works fine, I can read and write. Do I need to test at the specific image directory?

                          W 1 Reply Last reply Feb 25, 2016, 6:06 PM Reply Quote 0
                          • W
                            Wayne Workman @mattyb
                            last edited by Feb 25, 2016, 6:06 PM

                            @mattyb It wouldn’t hurt.

                            Anything in the apache error logs? FOG Configuration -> Log Viewer -> Apache Error Log

                            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/

                            M 1 Reply Last reply Feb 25, 2016, 6:12 PM Reply Quote 0
                            • M
                              mattyb @Wayne Workman
                              last edited by Feb 25, 2016, 6:12 PM

                              @Wayne-Workman Interesting. Navigating to fog Configuration / Log Viewer straight away says there’s an error with the Fog “ftp_login(): Login incorrect.”

                              In my Fog Configuration / TFTP Server, the username and password are correct, as are the fog config files on the server.

                              W 1 Reply Last reply Feb 25, 2016, 6:36 PM Reply Quote 0
                              • W
                                Wayne Workman @mattyb
                                last edited by Feb 25, 2016, 6:36 PM

                                @mattyb The error should show you what it tried for the username and password. navigate back to the log viewer and pay attention to the error.

                                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/

                                M 1 Reply Last reply Feb 25, 2016, 7:31 PM Reply Quote 0
                                • M
                                  mattyb @Wayne Workman
                                  last edited by Feb 25, 2016, 7:31 PM

                                  @Wayne-Workman There’s nothing to expand. Below the pause button it says ‘invalid folder’ and nothing else.

                                  M 1 Reply Last reply Feb 25, 2016, 7:49 PM Reply Quote 0
                                  • M
                                    mattyb @mattyb
                                    last edited by Feb 25, 2016, 7:49 PM

                                    I think my issue is in Storage Node / DefaultMember / Management Password. I updated that to match all other configs and now I get actual log choices. Trying to upload now.

                                    M 1 Reply Last reply Feb 25, 2016, 7:53 PM Reply Quote 0
                                    • M
                                      mattyb @mattyb
                                      last edited by Feb 25, 2016, 7:53 PM

                                      That was it. Same headache as this OP: Point #3. Registering and uploading!

                                      W 1 Reply Last reply Feb 25, 2016, 8:10 PM Reply Quote 1
                                      • W
                                        Wayne Workman @mattyb
                                        last edited by Wayne Workman Feb 25, 2016, 2:10 PM Feb 25, 2016, 8:10 PM

                                        @mattyb said:

                                        That was it. Same headache as this OP: Point #3. Registering and uploading!

                                        Just going to point out that those steps from that post are also in the Wiki article you said you went through 😉 Glad you got it working.

                                        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/

                                        M 1 Reply Last reply Feb 25, 2016, 8:32 PM Reply Quote 0
                                        • M
                                          mattyb @Wayne Workman
                                          last edited by Feb 25, 2016, 8:32 PM

                                          @Wayne-Workman Agreed, but what’s not clear is that the default password in this field is not actually my password, encrypted. The management password needs to be in this field in clear text. The same applies to other config sections on the management web interface. I should have just tried it earlier.

                                          W 1 Reply Last reply Feb 25, 2016, 8:50 PM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 2 / 3
                                          2 / 3
                                          • First post
                                            27/45
                                            Last post

                                          288

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project