Hi, this is the code that adds that field: https://github.com/DSpace/DSpace/blob/dspace-1_8_x/dspace-stats/src/main/java/org/dspace/statistics/SolrLogger.java#L212
If you look a few lines above, you'll see that if the request contains the "X-Forwarded-For" header (which is usually added by a proxy). If this header wouldn't be present, the real IP of the request would be used, which is the localhost IP. I have two possible explanations for this. Either you at some point changed nginx configuration to use or to stop using X-Forwarded-For and thus you ended up with both "real" IPs and "localhost". This could be proven by checking again after some time and seeing whether only one of them grows (either "localhost" or the "real" IPs) or both. Or, my other hypothesis would be, that some other program on the same machine is triggering usage requests and therefore those requests really are coming from localhost. In any case, I'm sure adding the X-Forwarded-For header can be configured in nginx. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
