1 2 Previous Next 17 Replies Latest reply on Feb 7, 2014 2:04 PM by John O'Toole

    "Software not licensed" error when run BL job

    Jason Culver

      Experiencing an "software not licensed" error on multiple target servers when running bl job called "MSXX_ETC_PRD-ufe
      " from BladeLogic Server Automation 7.4.3 app server.  I have tried many methods to
      relicensed the nodes as noted below:  What is also strange is the bl job has been running for quite some time against the 5-6 target servers with no issues.

       

      -deactivate license from bmc portal then relicense from appserver using autolic
      -decommissing server object and readding from bl gui console
      -deploy bl "update server properties job" to all servers
      -relicense the agent using getlic and putlic commands
      -checked permissions from /usr/lib/rsc/exports
      -confirmed i can live browse the server object from bl console
      -able to cd //host from bl mgr app server successfully

       

      Also, checked the rscd logs on the tagets to shed further light, but couldn't find any error messages to go off from... has anybody come across an issue like this before?  Looking to other places or ideas to check for a resolve.

        • 1. Re: "Software not licensed" error when run BL job
          John O'Toole

          Hi Jason,

           

          This could be an issue with the agent property not reflecting that the agent is licensed correctly.

          Could you check the AGENT_STATUS property in the BSA UI for this server? If it is set to "not licensed" could you either run a USP job against it and make sure it updates afterwards or right click and do a "verify".

           

          Thanks,

           

          John

           


          • 2. Re: "Software not licensed" error when run BL job
            Jason Culver

            Hi John,

             

            Agent Status shows “agent is alive” and agent shows licensed, but job still fails with “software not licensed”

             

            Error      Feb 4, 2014 7:31:36 AM  cd: software not licensed: //all-vams-p041.gxsonline.net/

             

             

            lit-vablm-p001# cd //all-vams-p026.gxsonline.net

             

            all-vams-p026# agentinfo all-vams-p041

            all-vams-p041:

              Agent Release   : 8.1.0.295

              Hostname        : all-vams-p041

              Operating System: Linux 2.6.18-194.32.1.el5

              User Permissions: 0/0 (root/root)

              Security        : Protocol=5, Encryption=TLS1

              Host ID         : 69962EC1

               

            1. of Processors : 8

              License Status  : Licensed for NSH/CM

            • 3. Re: "Software not licensed" error when run BL job
              John O'Toole

              Hi Jason. From looking at the rscd.log you attached, I see there are nsh commands there which call out to another agent - ohiomgr6. Could you check that one to see if that is the agent which is perhaps unlicensed here?

              • 4. Re: "Software not licensed" error when run BL job
                Jason Culver

                Hi John,

                 

                I checked the licensing portal from BMC and I see ohiomgr6 as licensed:

                 

                Date Generated

                 

                Generated By

                 

                Licensed Product

                 

                Host

                 

                Unique ID

                 

                CPUs

                 

                License Count

                 

                Select for Deactivation

                 

                04/25/2013

                 

                culverj

                 

                Operations Manager

                 

                ohiomgr6.ohctr.gxs.com

                 

                97C652BA

                 

                4

                 

                1

                 

                 

                 

                lit-vablm-p001# agentinfo ohiomgr6.ohctr.gxs.com

                ohiomgr6.ohctr.gxs.com:

                  Agent Release   : 7.4.3.713

                  Hostname        : ohiomgr6.ohctr.gxs.com

                  Operating System: Linux 2.6.9-89.ELsmp

                  User Permissions: 0/0 (root/root)

                  Security        : Protocol=5, Encryption=TLS1

                  Host ID         : 97C652BA

                   

                1. of Processors : 4

                  License Status  : Licensed for NSH/CM

                • 5. Re: "Software not licensed" error when run BL job
                  John O'Toole

                  Hi Jason,

                   

                  Could you include the job run log from the job? Seeing the context of where the error appears within the log might help.

                   

                  Also, what user:role are you running this job as? I'll use that to look through the rscd.log again. Just to rule out permissions, which sometimes appear as license issues as you mentioned, could you run it as BLAdmins:BLAdmin and see if you get the same error?

                   

                  Can you run a very simple deploy job to some of these problem servers? Do those work or do they also hit the license issue?

                   

                  Do you have any servers which this same job works ok and does not throw the error? The job run log will tell me that also.

                   

                  Thanks,

                   

                  John

                  • 6. Re: "Software not licensed" error when run BL job
                    Bill Robinson

                    is the target a VM?  if so the cpu count may be changing.  you can try licensing it for a high cpu count like:

                     

                    autolic -c 200 user pass server

                    • 7. Re: "Software not licensed" error when run BL job
                      Jason Culver

                      Thanks Bill, that was the resolve to the issue.  I was able to run the job without getting the software not license error now.  The sys admin must have added more CPUs to the VM.  Again, appreciate the help from you and John.

                      • 8. Re: "Software not licensed" error when run BL job
                        Jason Culver

                        I spoke too earlier, one the app engineer ran the job this morning those 5 servers I licensed came back with the “software not license” error.  Seems something is deactivating the license after a short period of time.  I too tried again myself with BLadmin:Bladmin and it failed with “software not license” too.

                        • 9. Re: "Software not licensed" error when run BL job
                          John O'Toole

                          I was wondering why the agentinfo was working if the problem was the CPUs but I was going to check that with Bill.

                           

                          Can you send in the job run log for one of this mornings runs along with the rscd.log and rscdsvc.log from a couple of the servers? I would like to compare the events on both sides.

                          Also, now that it has hit the issue this morning, does agentinfo still report it as licensed ok? i.e. is there a difference in what the job log is saying and what the agentinfo is saying?

                           

                          To confirm Bill's earlier question - these are all Windows VMs?

                           

                          Thanks,

                           

                          john

                          • 10. Re: "Software not licensed" error when run BL job
                            Jason Culver

                            Some more background info on BL job.  I attached the rscd logs for a target that was successful and a target that failed due to “license error”.  The job was deployed by bladmin:bladmin, the original owner and creator of the script for the job is in the role group called application:hawkinss.

                             

                             

                            • 11. Re: "Software not licensed" error when run BL job
                              Jason Culver

                              When the original owner ran the job this morning and reported that it failed, I checked the licensing status and it showed unlicensed this morning.

                               

                              all-vams-p041.gxsonline.net:

                                Agent Release : 8.1.0.295

                                Hostname : all-vams-p041

                                Operating System: Linux 2.6.18-194.32.1.el5

                                User Permissions: 0/0 (root/root)

                                Security : Protocol=5, Encryption=TLS1

                                Host ID : 699645C1

                                 

                              1. of Processors : 8

                                License Status : Not Licensed

                               

                              I went back in and relicense the failing targets with the command Bill provided:

                               

                              autolic -c 200 user pass server

                               

                              then ran the job again as application role, but failed:

                               

                               

                              • 12. Re: "Software not licensed" error when run BL job
                                Jason Culver

                                These are Redhat 5.5 virtual machines, could you tell me the path for the rscdsvc.log files are?  Would these logs be on the target hosts or bl app server?  BladeLogic app server is also running redhat 5.5 too with bl8.1 version.

                                • 14. Re: "Software not licensed" error when run BL job
                                  John O'Toole

                                  Hi Jason,

                                   

                                  I think I see the problem. Compare the agentinfo output for this server from Tuesday and today. The hostid has changed:

                                   

                                  Feb 4th:

                                  all-vams-p041:
                                    Agent Release   : 8.1.0.295
                                    Hostname        : all-vams-p041
                                    Operating System: Linux 2.6.18-194.32.1.el5
                                    User Permissions: 0/0 (root/root)
                                    Security        : Protocol=5, Encryption=TLS1
                                    Host ID         : 69962EC1


                                  Feb 6th:

                                  all-vams-p041.gxsonline.net:
                                    Agent Release : 8.1.0.295
                                    Hostname : all-vams-p041
                                    Operating System: Linux 2.6.18-194.32.1.el5
                                    User Permissions: 0/0 (root/root)
                                    Security : Protocol=5, Encryption=TLS1
                                    Host ID : 699645C1

                                   

                                  Could the IP Addresses of these linux servers be changing? See following KA:

                                   

                                  https://kb.bmc.com/infocenter/index?page=content&id=KA305341

                                   

                                   

                                  Now that you have relicensed it, double check the AGENT_STATUS property again. If it became unlicensed and then a USP job ran, its status would be unlicensed even if you then went and licensed it again - until you rerun the USP or do a Verify.

                                  1 2 Previous Next