1 2 Previous Next 21 Replies Latest reply on Jun 30, 2009 9:20 AM by Regis

    8.8 SP3 - Issues?

    Rookie

      I am considering upgrading to SP3 but as it was only released a few weeks ago I wondered if anyone had upgraded to SP3 and if so has anyone had any issues?

        • 1. Re: 8.8 SP3 - Issues?
          Employee

          I've seen nothing but good results once the upgrade is complete.  I've seen a few people have problems during the upgrade process, but that's usually fairly straightforward to troubleshoot.

           

          I would just make sure that the regular precautions are done (backup the database, get a copy of the keys folder, etc.) and then be pretty confident in doing it.

           

          Personally I've upgraded three core servers with no problems at all.

          • 2. Re: 8.8 SP3 - Issues?
            Specialist

            I've upgraded my core server to SP3 with no issues.  Have deployed to about 200 of my 1800 clients with no known issues.  Will be deploying to the remaining machines sometime next week.

            • 3. Re: 8.8 SP3 - Issues?
              Rookie

              What were some of the problems you've seen during upgrades.  We've got an upgrade that's been running for about 4 hours now (from SP2 - SP3).

              • 4. Re: 8.8 SP3 - Issues?
                Employee

                What does it say is running?  Coredbutil /upgradedb or something like that?

                 

                The only problems I've seen are certain databases in a bad state that cause some task to fail.

                 

                If the upgrade does fail in the middle it picks up where it left off, so it's not too bad, you fix what wasn't working, then run again and off you go.

                • 5. Re: 8.8 SP3 - Issues?
                  Rookie

                  That's exactly what it's running right now but we haven't seen any errors.  Just really slow.  CPU is chugging along at about 79%.

                  • 6. Re: 8.8 SP3 - Issues?
                    Employee

                    If you have a large database it can take a long time.  A very long time.  In my test lab (about 12 managed devices, not many tasks, pretty bare-bones) it took somewhere between 90 minutes and 2 hours for that step alone.  Not as long as yours, but yours is also a much larger database, I would guess.

                    • 7. Re: 8.8 SP3 - Issues?
                      Specialist

                      Mach6 wrote:

                       

                      If you have a large database it can take a long time.  A very long time.  In my test lab (about 12 managed devices, not many tasks, pretty bare-bones) it took somewhere between 90 minutes and 2 hours for that step alone.  Not as long as yours, but yours is also a much larger database, I would guess.

                       

                      Wow... Then I wonder if something is up with mine.  I have 1800+ devices, 1 core, the SQL instance is on a seperate SQL Server, and it took less than 20 minutes. 

                      • 8. Re: 8.8 SP3 - Issues?
                        Employee

                        Chris,

                         

                        Do you patch through LANDesk?  Patching tables are among the largest we have, and can make CoreDBUtil take a lot longer.

                        • 9. Re: 8.8 SP3 - Issues?
                          Specialist

                          Mach6 wrote:

                           

                          Chris,

                           

                          Do you patch through LANDesk?  Patching tables are among the largest we have, and can make CoreDBUtil take a lot longer.

                          Just for clarification, the SP3 update to the core took about ~20 minutes.

                           

                          When I push the update (via LANDesk) to clients it takes between 5 and 10 minutes (each), and I have done about 200 of those.

                           

                          I use LANDesk pretty regularly, but I am SURE that I don't use it to the potential as some of the other users do, so maybe that was it?

                           

                          Chris

                          • 10. Re: 8.8 SP3 - Issues?
                            Rookie

                            I work with DCaldwell - we do have a pretty large deployment (approx 7000 clients, extensive use of policies).

                             

                            Our database is around 2gb - We've tried the update twice (revert back to the old config using VMWare and a database restore).  Right now the Coredbutil update is going on 7hours - the SQL server isn't getting hammered, but the core server is still cranking over 50% steady CPU.

                             

                            Attached is the last part of the Coredbutil log file.  Looking in the \logs directory, there are a slew of scheduledtaskhandler logs that seem to be processes kicked off by the update.  I'll attach a couple of examples of that as well.

                             

                            Any thoughts?  Do we need to just allow this to run to completion even if it starts to get to 24hrs?  Should we cancel all policies before launching the update?

                             

                            Thanks!

                            • 11. Re: 8.8 SP3 - Issues?
                              WiseGuy Apprentice

                              We saw the same situation with many scheduledtaskhandler logs when we upgraded to SP2.  To the point where we rolled back to the previous version as we were running at 4+ hours for the install.  I called tech support and they indicated that if you have a lot of scheduled tasks it can take a while to convert them as the update has to run a process on each one.  We then went through a cleanup process of our scheduled tasks and got the numbers of tasks remaining down to under a hundred.  After the cleanup the install on the Core then went fast (less than 90 minutes if I remember correctly).

                              • 12. Re: 8.8 SP3 - Issues?
                                Rookie

                                Thanks for your reply Ernie.  We actually resolved the issue with this: http://community.landesk.com/support/docs/DOC-5891

                                We're a school system.  We have several hundred policies which allow a teacher to go the portal and install a printer.  For whatever reason one of the printer policies had become corrupted.  When we ran the command manually and monitored it' progress in the log we could see exactly where it was stopping. We're running our core servers virtually.  So we restored the snapshot we took before we got started, fired up the console, found the policy causing the pain and deleted it.  Then we restarted the procedure again which is no more than a command line.  It ran for about an hour. Than the regular SP3 setup was run and about 3.5 - 4 hours later were up and running.  We haven't had any issues since.  Everything looks good.  Thanks for responding.

                                • 13. Re: 8.8 SP3 - Issues?
                                  zman Master

                                  So as indicated in the doc schedpkgupdate.exe is doing all the heavy lifting here. In older upgrades this animal had a 6 hour timer on it (it would kill itself after 6 hours).Also the last SP if schedpkgupdate.exe died after 6 hours there running it again (with appropriate switches) would not update the packages. This caused issues with the portal since if the new xlm files were not created and running the portal would die looking for them. Simply saving the distribution packages would upgrade them.

                                   

                                  So with shops with a lot of packages (3 to 4 digits) it can take an enormous amount of time. I hope LANDesk has lifted the 6 hour rule, and will test this shortly . Just something to be aware of.  You can tail schedpkgupdate.exe.log and see how it takes for an average policy and calculate how long this process takes.

                                  • 14. Re: 8.8 SP3 - Issues?
                                    Rookie

                                    Nice learning process for me.  It ran for about 14 hours before we hit the switch the first time.  Then we got the document and an email from LANDesk saying you may want to take a look at this.  Thanks for the tip.

                                    1 2 Previous Next