In my IIS logs the page /umbraco/ping.aspx is accessed a lot from a certain ip address. Also from my own ip address. Is this with a reason and likes Umbraco to know if your site is up or is someone investigating me? With the first I've got no problem but the second I don't like. Maybe you could explain also what the ping page is all about?
Is umbracoStats something default in an Umbracoinstallation? I never installed the package. I like to know how I can see these logs within Umbraco. I don't like to remove this :-)
/umbraco/ping.aspx
Hi,
In my IIS logs the page /umbraco/ping.aspx is accessed a lot from a certain ip address. Also from my own ip address. Is this with a reason and likes Umbraco to know if your site is up or is someone investigating me? With the first I've got no problem but the second I don't like. Maybe you could explain also what the ping page is all about?
Regards,
Roel
Hi Roel,
Looks like it is caused by umbracoStats. See this post
http://forum.umbraco.org/yaf_postst6511_Fixed-stats-database-table-flooded-with-entries-for-umbracopingaspx.aspx
Neil
Is umbracoStats something default in an Umbracoinstallation? I never installed the package. I like to know how I can see these logs within Umbraco. I don't like to remove this :-)
What version of umbraco are you using?
Hi Neil,
The version is 4.6.
Regards,
Roel
I have a fresh 4.6.1 & 4.7.0 installed, running fiddler there are no requests being made to umbraco/ping.aspx
Have you checked the umbracolog table to see if anything is being logged for these requests?
What packages do you have installed?
Is Distributed publishing enabled it uses the ping.aspx see - http://our.umbraco.org/forum/developers/api-questions/10267-The-file-%27umbracopingaspx%27-does-not-exist-In-a-distributed-setup
There are no requests in the loggintable.
See here a part of my log of today:
2011-04-11 02:22:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 6
2011-04-11 02:27:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 7
2011-04-11 02:32:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 4
2011-04-11 02:37:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 5
2011-04-11 02:42:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 5
2011-04-11 02:47:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 6
2011-04-11 02:52:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 5
2011-04-11 02:57:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 202 84 39
2011-04-11 03:02:40 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 1149
2011-04-11 03:07:40 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 1111
2011-04-11 03:12:40 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 970
2011-04-11 03:17:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 646
2011-04-11 03:22:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 824
2011-04-11 03:27:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 2
2011-04-11 03:32:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 814
2011-04-11 03:32:52 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 64.27.54.34 - 200 0 0 231 81 394
2011-04-11 03:37:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 3
2011-04-11 03:37:52 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 64.27.54.34 - 200 0 0 231 81 326
2011-04-11 03:42:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 22
2011-04-11 03:42:52 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 64.27.54.34 - 200 0 0 231 81 325
2011-04-11 03:47:39 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 85.17.255.98 - 200 0 0 231 84 2
2011-04-11 03:47:52 W3SVC5 85.17.255.98 GET /umbraco/ping.aspx - 80 - 64.27.54.34 - 200 0 0 231 81 332
is working on a reply...