Entries in Tomcat's localhost_access_log.2017-06-13.txt file

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Jon, Steve, Ian, Dave

hovikav
Ebase User
Posts: 5
Joined: Tue May 23, 2017 2:47 pm

Entries in Tomcat's localhost_access_log.2017-06-13.txt file

#1

Postby hovikav » Wed Jun 21, 2017 9:23 am

Daily log files are being filled by entries such as these - upto 20 per second.

10.32.65.141 - - [13/Jun/2017:00:00:00 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:01 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036
10.32.65.141 - - [13/Jun/2017:00:00:02 +0100] "GET /ufs/appstatus/appstatus.jsp HTTP/1.0" 404 1036

We're trying to understand what's trying to invoke the jsp.

A few facts
  • 10.32.65.141 is the web server where IIS is installed - we presume this is therefore the requestor?

    The missing appstatus.jsp has been deliberately renamed as it was causing other errors and is no longer needed to run.

    There are no Ebase scheduled jobs invoking this

    We can't see any windows scheduled jobs invoking this (not 100% sure of this)

    The entries are only in log files of the Internal production Tomcat system
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#2

Postby Jon » Wed Jun 21, 2017 1:12 pm

These are genuine URL requests hitting the server. The access log can provide you with more information about the caller - this is configured in the server.xml file in tomcat/conf. I thought that by default it would provide you with the caller's IP address but I could be wrong. Then you can try and figure out where these requests are coming from.
0 x


Who is online

Users browsing this forum: No registered users and 4 guests