1 2 Previous Next 17 Replies Latest reply on May 7, 2014 12:43 PM by Jared Murrell

    BladeLogic Provisioning Stopped Working

    Jared Murrell

      We've been doing provisioning for a while and it recently stopped creating the files on the TFTP server. PXE files get created, but not TFTP. Where can I start looking? pxe.log and tftp.log don't really show me much

        • 1. Re: BladeLogic Provisioning Stopped Working
          Jared Murrell

          I'm provisioning RHEL and using Skip-Linux... the job stops at step 13/16 (Make Run Once)

          • 2. Re: BladeLogic Provisioning Stopped Working
            Jared Murrell

            Hmm.... I'm getting this error in the AppServerLauncher logs:

             

            [06 May 2014 08:18:44,571] [RMI TCP Connection(1942687)-10.10.10.10] [WARN] [::] [] received serviceTicket with invalid signature from System

            [06 May 2014 08:18:44,571] [RMI TCP Connection(1942687)-10.10.10.10] [INFO] [::] [] BlSession authentication failed. java.lang.SecurityException: Failed to establish session

             

            I'm seeing those go back a few days though, so I'm not sure if that's it or if it is something else

            • 3. Re: BladeLogic Provisioning Stopped Working
              Bill Robinson

              what do you mean by ‘pxe files’ and ‘tftp files’ ?  specifically what file or files are not being created ?

              • 4. Re: BladeLogic Provisioning Stopped Working
                Jared Murrell

                It creates a custom kickstart (since it's RHEL) file under D:\PXE called 00-11-22-33-44-55 (assuming that the MAC address is 00-11-22-33-44-55), but it is supposed to create a file under D:\tftproot\X86PC\pxelinux\pxelinux.cfg\ that is the HEX representation of the MAC (like 0AF8160B or something like that) to handle PXE instructions for the target server. The 00-11-22-33-44-55 file (custom kickstart) is being created, but the 0AF8160B (PXE instructions) is not, so when the target server receives a PXE response it can't pull the file for boot instructions

                • 5. Re: BladeLogic Provisioning Stopped Working
                  Jared Murrell

                  Here's the last entry I see in the PXE log:

                   

                  [06 May 2014 10:43:13,371] [Thread-8] [INFO] [::] [] (U)FD:2460

                  [06 May 2014 10:43:13,371] [Thread-8] [INFO] [::] [] (U)FD:2464

                  [06 May 2014 10:43:13,371] [Thread-8] [INFO] [::] [] activity fd index:1

                  [06 May 2014 10:43:13,371] [Thread-8] [INFO] [::] [] DatagramSocket received

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] RPacketProcessor Thread id= 9891765 started

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] It is a boot server request packet from /10.10.10.10:67

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] Will create light weight prov device object

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] Provision device 00-11-22-33-44-55 exists in the system

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] Provision device object active

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] IP address of the device :N/A Architecture is x64

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] Packet type is DHCP Request setting up DHCP ACK packet for reply

                  [06 May 2014 10:43:13,371] [Thread-9578111] [INFO] [::] [] makeBootMenu : type 2

                  [06 May 2014 10:43:13,387] [Thread-9578111] [INFO] [::] [] Device instructed to local boot

                  [06 May 2014 10:43:13,387] [Thread-9578111] [INFO] [::] [] Replying to /10.10.10.10:67

                  [06 May 2014 10:43:13,387] [Thread-9578111] [INFO] [::] [] RPacketProcessor Thread id= 9891765 Finished

                  • 6. Re: BladeLogic Provisioning Stopped Working
                    Jared Murrell

                    And I'm running BSA 8.3 SP3 on Winders

                    • 7. Re: BladeLogic Provisioning Stopped Working
                      Bill Robinson

                      this is probably why:

                       

                      [06 May 2014 10:43:13,387] [Thread-9578111] [INFO] [::] [] Device instructed to local boot

                       

                      is your target device in the 'imported' state ?  and the provisioning job is running?

                       

                      for this error:

                      [06 May 2014 08:18:44,571] [RMI TCP Connection(1942687)-10.10.10.10] [WARN] [::] [] received serviceTicket with invalid signature from System

                      [06 May 2014 08:18:44,571] [RMI TCP Connection(1942687)-10.10.10.10] [INFO] [::] [] BlSession authentication failed. java.lang.SecurityException: Failed to establish session

                       

                      it means that 10.10.10.10 is trying to talk to the launcher on this appserver and failing, probably because of a mismatched bladelogic.keystore.  this shouldn't be affecting anything related to the pxe issue though.

                      1 of 1 people found this helpful
                      • 8. Re: BladeLogic Provisioning Stopped Working
                        Jared Murrell

                        I saw that and have been trying to figure out why it would be set to local boot. I deleted and re-added the device, and it shows up under the smart group "Imported". I also created a new job for it and it still hangs at step 13/16 before creating the file. Previously devices would stop at step 15/16 and the OS would install, then check-in and the job would continue to 17/17 and then finish. The PM_STATE property is "Discovered"

                        • 9. Re: BladeLogic Provisioning Stopped Working
                          Bill Robinson

                          Can you query your database for the mac address in the pm_device table?

                           

                          Select * from pm_device where mac_address = ‘AA-BB-CC’;

                          1 of 1 people found this helpful
                          • 10. Re: BladeLogic Provisioning Stopped Working
                            Jared Murrell

                            Will run in a bit. Is there anything in the agent or file permissions I can check? I had an issue with this on my Linux installation and it turned out to be file permissions, but this is Windows and nothing has changed (to my knowledge) since it worked last. Another thing to note is that I added a fresh device as a test and it ended up in the same state. I'll post the SQL results as soon as I have them

                            • 11. Re: BladeLogic Provisioning Stopped Working
                              Bill Robinson

                              the tftpboot file will be written as the user the pxe service is running as, so that user will need write in the pxelinux.cfg directory.  that doesn't happen via the rscd.

                              • 12. Re: BladeLogic Provisioning Stopped Working
                                Jared Murrell
                                pm_device_idguiddescriptionlast_known_namebios_idpm_state_idbl_acl_idbl_value_idcreated_by_role_idcreated_by_user_idmodified_by_role_idmodified_by_user_idmac_addressdevice_type_idip_addressmanufacturersystem_typeno_of_cpucpu_familycpu_speedrampxe_boot_image_iddiscovery_datedate_createddate_modifiedis_64bitpre_instl_script_numis_deleted
                                5850x1E4E2C8CACEA453B94B3AD42A451C7EFserver0100-11-22-33-44-55-10200054318939561200001320000891000010200016600-11-22-33-44-550N/A0005002014-04-25 15:26:28.1802014-04-25 15:26:28.4872014-05-07 09:41:25.123110
                                • 13. Re: BladeLogic Provisioning Stopped Working
                                  Jared Murrell

                                  We have 2 PXE servers... I found the file boot file (0AF8160B) being created on the second PXE server (located in another datacenter), but the custom kickstart file (01-00-11-22-33-44-55) was being created in the right place. pxe.conf was configured with the correct IP address, so I'm not sure why that happened. After restarting both PXE servers the boot file (0AF8160B) is no longer being created on either.

                                   

                                  The user who is trying to provision says this is the first provisioning attempt for Linux after the SP3 upgrade a few weeks ago

                                  • 14. Re: BladeLogic Provisioning Stopped Working
                                    Bill Robinson

                                    The only reason the file would have been created in the other pxe server is if there was broadcast forwarding going on to that box from the target’s vlan.

                                    1 2 Previous Next