[Glass] maintenance_gem.log expired sessions

[Trussardi Dario Romano via Glass]

> 
> 
> On Wed, Dec 9, 2015 at 8:20 AM, Trussardi Dario Romano via Glass <glass at lists.gemtalksystems.com> wrote:
> Ciao,
> 	
> 	i have a deployment glass environment system ( 3.1.0.6 )
> 
> 	where i run the Seaside maintenance VM.
> 
> 	Now the		 maintenance_gem.log 	report:
> 
> 		hourly :
> 
> 			--transcript--'Starting markForCollect.: 2015-12-06T03:35:11.58872890472412+01:00'
> 			--transcript--'Warning: markForCollection found 2569174 live objects, 4553 dead objects(occupying approx 409770 bytes)'
> 			--transcript--'...finished markForCollect.2015-12-06T03:35:19.36173295974731+01:00'
> 	
> 		every minute:
> 
> ...Expired: 0 sessions.
> ...Expired: 20 sessions.
> ...Expired: 4 sessions.
> ...Expired: 9 sessions.
> ...Expired: 3 sessions.
> ...Expired: 0 sessions.
> ...Expired: 0 sessions.
> ...Expired: 0 sessions.
> ...Expired: 0 sessions.
> 
> 
> Now my application open	only two local session  ( DTRWASession  subclass of WASession ) every day.
> 
> Where for local i intend on the local network where the Glass server run.
> 
>  I don't understand  because the maintenance report some other Expired session.
> 
> The maintenance expired session reference to WASession open  or reference- mean to some other thinks?
> 
> The system records information about the WASession open and the relative IP request  address   ?
> 
> Sessions expired can be related to intrusion attempts from internet?
> 
> 
> 
> Yes, that looks strange. If you check the object log entries (either via tODE command "ol view -r"  or from WAObjectLog) you can see the timestamp.
> So...if you are sure nobody was doing anything at all at that time then it might be intrusion attempts. Bear in mind the session timeout. 
> I wonder if you have some kind of service that would do a HTTP GET over the main URL for checking sanity of the system (kind of monit tool)?

Ciao Mariano,
	
	i have the following services ( launched by daemontools ) :

/etc/service/gs_maintenance: up (pid 11242) 2221972 seconds
/etc/service/gs_seaside-9060: up (pid 11240) 2221972 seconds

/etc/service/gs_seaside-9061: up (pid 11244) 2221972 seconds

/etc/service/gs_seaside-9062: up (pid 11245) 2221972 seconds

/etc/service/gs_seaside-9063: up (pid 11247) 2221972 seconds

/etc/service/gs_seaside-9064: up (pid 11246) 2221972 seconds

/etc/service/gs_seaside-9065: up (pid 11248) 2221972 seconds

/etc/service/gs_statmon-1: up (pid 11241) 2221972 seconds

/etc/service/gs_statmon-60: up (pid 11243) 2221972 seconds


	The		 gs_statmon-x 	services open some sessions in the server ?

	Thanks,

		Dario



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20151209/dd7a2681/attachment-0001.html>