Skip to main content

ArcGIS log files blow up when set to verbose in ArcGIS 10.4.1 (way more so then in 10.2.2)

Permanently deleted user
We recently upgraded to ArcGIS Server 10.4.1 (from 10.2.2). We have our log file collection set to verbose, as required by Analytics. The amount of log data produced with 10.2.2 was managable, but since the upgrade it has become unmanagable. We are creating around 2 GB of log files/day, and that is just for a single ArcGIS server! Has anyone else experienced this? Any suggestions as to what we can do? I really want to turn off verbose collection, but without it Analytics will not work. Thank you in advance for any guidance you might be able to provide!
0

Comments

5 comments

Date Votes
  • Permanently deleted user
    Tara,

     

    which log files are you seeing get this large?  I just posted a question about resetting log files because of the size they got to (not just ArcGIS log).We do have multiple AGS servers being monitored in our dev/test environment but only one of them is 10.4.1 so I'm not sure if this is the same issue you are having.  Did you ever find a solution?

     

     
    0
  • Permanently deleted user
    Hi Tara and Peter,  

     

    While we currently do require that your ArcGIS server be set to verbose logging, we are looking into a way to collect the data we need without this requirement.  The tracking number for this improvement is GID-502.  

     

    Thanks!

     

    Danny
    0
  • Permanently deleted user
    Hi Peter - These are our actual ArcGIS Server logs that get extremely large with verbose logging (drive\arcgisserver\logs\site). Additionally, we are starting to think that verbose logging is having a significant impact on the virtual memory being used by our services. It is standard that the amount of virtual memory used by a service is 2-3x greater than the physical memory, but we are seeing a full order of magnitude increase. This is obviously having a pretty significant impact on the performance of our ArcGIS Server.

     

    Danny - Thank you for providing the tracking number. I will definitely continue to follow this, and I do hope they are able to find a fix.
    0
  • Permanently deleted user
    Tara,

     

    How are you determining the amount of virtual memory being used - is it per service or in total?  I'm very interested in this because we are in the process of migrating from 10.2.2 to 10.5(.1) and if verbose logging has that much of an impact, we'll need to do some quick changes to our RAM allocations on the servers.

     

    We have decided not to use Analytics due to it's current shortcomings and will stick with Optimizer.  It will still require us to have Verbose logging enabled in AGS, though.  Depending on what information you want to collect, you might be able to get away with Fine level (it still lists start/end times and extent but no time breakdowns).

     

    Peter

     

    Peter.
    0
  • Permanently deleted user
    Peter - We ended up contracting with Esri to try and help us develop a game plan to improve the stability and performance of our systems. As part of that, we have been using some of their monitoring tools (System Log Parser, System Monitor, etc). The virtual memory came from a fairly basic script we ran in a command line. I'm afraid I'm not able to find a copy of it right now but will let you know if I do.We are working to tune our services (both on the mxd as well as within Manager) to try and help in the time being. Also, I did try reducing the logging to Fine, but I'm afraid Analytics stops working altogether when that happens.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post