8 Replies Latest reply on Feb 13, 2012 7:57 AM by greatscott

    Issue with system updating and sitestat.xml

    greatscott

      Anyone ever have an issue with their sitestat.xml file not updating? Its reading this: CatalogVersion="20120201200033" Because of this our systems aren't updating. Its showing an older catalog version than is currently available in the Master Repository. The catalog.z is also out of date.

       

      Thanks!

        • 1. Re: Issue with system updating and sitestat.xml
          tao

          I have before and usually a force un/re-install of the Agent corrects the issue.  

          • 2. Re: Issue with system updating and sitestat.xml
            JoeBidgood

            Possibly a stupid question but have you performed a replication to this repository? These files are controlled and updated by the replication process...

             

            HTH -

             

            Joe

            • 3. Re: Issue with system updating and sitestat.xml
              greatscott

              Joe,

               

              What happens is when we perform a repository update, the old "CatalogVersion" is left when we do a repository update at 1am.  If on February 7th the CatalogVersion was "20120207XXXXXX", we do the repository replication at 1am on the 8th, it should be changed to "CatalogVersion= 20120208XXXXX".

               

              Instead, what we are finding, is that it is still at "CatalogVersion=20120207XXXXXX", essentially a day behind. To remedy this, we have been forced to issue the system a reboot. Sometimes it takes several reboots to get the SiteStat.xml to properly update.

               

              Essentially the systems see the catalog version as being old, and skips over the repository, assuming it has no updates to issue. All the meanwhile, the master repository DOES have the correct DAT version,etc.

               

              (But to answer your original question, yes, we have been performing regular updates to this repository for quite some time)

               

              Tao,

               

              I would agree with you normally, but this seems to be purely server related IMO.

               

              Message was edited by: greatscott on 2/8/12 12:42:57 PM CST
              • 4. Re: Issue with system updating and sitestat.xml
                JoeBidgood
                If on February 7th the CatalogVersion was "20120207XXXXXX", we do the repository replication at 1am on the 8th, it should be changed to "CatalogVersion= 20120208XXXXX".

                 

                 

                Strictly speaking, when you do a replication, the catalog version is changed to whatever it is on the master repo - the catalog version known to the server - so the sitestat on the distributed repo should only change to 20120208XXXXX  if that's what the version of the master is. (I guess you knew that but it needs stating for clarity )

                 

                I assume the replication tasks to the DR are succeeding? There are no errors listed in epoapsrv.log?

                If so - check the sitestat in the root of the master repo: does the catalog version match the last time the master repo was modified (for example by a pull task)?

                Do you have any client machines that update from the master repo itself? If so, do any of them show the same "not up-to-date repository" error?

                 

                Thanks -

                 

                Joe

                • 5. Re: Issue with system updating and sitestat.xml
                  greatscott

                  Joe,

                   

                  Our DRs seem to be updating properly. Basically we have our McAfee Agent Policy set so that each machine has to try 2 SADR's before it can use the ePO server. Our SADRs are somewhat sporadic, so yes, systems get their updates from the master repository frequently.

                   

                  No notable errors in the epoapsrv.log file. Here is the interesting part: We run our Master Repository Pull at 1am. It says in the Server Task Log that the task ran for 53mins. If you go into the server into the mcafee\epolicyorchestrator\DB\Software folder, it says that the Sitestat.xml, Replica.txt, catalog.z, Previous Folder, Current Folder were all last modified at 1:53am. The kicker is that we had to reboot the server this morning at 6am to get the SiteStat.xml file to update to the proper date of CatalogVersion=20120209XXXXXX, as it was stuck on the one from the 8th.

                  • 6. Re: Issue with system updating and sitestat.xml
                    JoeBidgood

                    we had to reboot the server this morning at 6am to get the SiteStat.xml file to update to the proper date of CatalogVersion=20120209XXXXXX, as it was stuck on the one from the 8th.

                     

                    Which sitestat file are we talking about here? Can you let me know which folder it lives in?

                     

                    Thanks -

                     

                    Joe

                    • 7. Re: Issue with system updating and sitestat.xml
                      greatscott

                      %installed drive%\Program Files\mcafee\epolicyorchestrator\DB\Software\SiteStat.xml

                       

                      When you go to the server via http://{insert server name here}/Software/SiteStat.xml should pull up in the browser. It will show the incorrect date too when we don't perform a reboot after we do our 1am repository pull.

                       

                      Message was edited by: greatscott on 2/9/12 10:29:00 AM CST

                       

                      Message was edited by: greatscott on 2/9/12 10:29:33 AM CST
                      • 8. Re: Issue with system updating and sitestat.xml
                        greatscott

                        Has anyone ever seen this?