FIN113 - eTime cronjob
From: SIDAWAY Martyn Sent: 06 July 2016 08:07 To: MATHISON Anne <Anne.Mathison@ed.ac.uk> Subject: etime and jams reboots
Hi Anne
Just to let you know servers all rebooted this morning and all seems to be running ok , dev , test and Live.
Thanks
Martyn
----
Sent: 04 July 2016 12:29 To: FINNAN Anne <Anne.Finnan@ed.ac.uk>; MATHISON Anne <Anne.Mathison@ed.ac.uk>; PEREZ LOPEZ Emilio <Emilio.Perez@ed.ac.uk>; PINEDA Julieta <julieta.pineda@ed.ac.uk> Subject: RE: FIN113 - etime cronjob
Actually the logs dates are from the last rsync jobs run on Fenton regardless of etime . The previous email I had sent were log dates for Test environment only back in December , and again not related to etime . Sorry for any confusion caused by that , upshot was no rsync jobs run for a very , very long time for etime or any others in Live .
Thanks
Martyn
---
Sent: 04 July 2016 12:23
From: FINNAN Anne
To: SIDAWAY Martyn <Martyn.Sidaway@ed.ac.uk>; MATHISON Anne <Anne.Mathison@ed.ac.uk>; PEREZ LOPEZ Emilio <Emilio.Perez@ed.ac.uk>; PINEDA Julieta <julieta.pineda@ed.ac.uk>
Subject: RE: FIN113 - etime cronjob
I thought it stopped running in December?
The listing below relates to hr, in fact I don’t think eTime existed in 2009??
---
Anne,
Now that we got the answers we were missing, I'm happy to sign off this project.
Julieta. - 4-Jul 10:59
----
On 04/07/2016 10:14, SIDAWAY Martyn wrote:
Just an update from this email I had sent out last week the actual date this cronjob was last run was way back in September 2009 :-
Logs on Fenton
-rw-r--r-- 1 hr11i hr11i 0 Sep 22 2009 rsync-hailes-2009-09-22.log
-rw-r--r-- 1 hr11i hr11i 312 Sep 22 2009 rsync-hailes-2009-09-22.err
-rw-r--r-- 1 hr11i hr11i 354 Sep 22 2009 rsync-2009-09-22.messages
-rw-r--r-- 1 hr11i hr11i 0 Sep 23 2009 rsync-hailes-2009-09-23.log
-rw-r--r-- 1 hr11i hr11i 956 Sep 23 2009 rsync-hailes-2009-09-23.err
-rw-r--r-- 1 hr11i hr11i 790 Sep 23 2009 rsync-2009-09-23.messages
The old job used to copy contents of etime application to hailes only unidirectional.
I would conclude from the dates above this is definitely not required for a long time now . and also the purpose it seems to be purely to keep the application files the same on both servers. The new TAD ( and technical build document ) details that the same code is deployed to both servers so negates any need for this cronjob , and any subsequent deployments should be performed in the same manner .
Thanks
Martyn
As discussed yesterday (28-Jun) , this particular cron job was switched off back in December 2015 and not been used since , on the existing servers or new , The rsync job was copying essentially the 'war' files from one server to the other , presumably to keep the application code the same on both servers in each environment . But in our case with the migration we have used exactly the same war file to deploy to both servers . Further deployments are covered in the TAD under common procedures( so exact copy of WAR file is deployed to both servers rather than using rsync to make them the same ) .
Thanks
Martyn
-
From: PINEDA Julieta
Sent: 29 June 2016 13:43
To: MATHISON Anne
To keep you up to date, the only outstanding thing is to confirm whether an rsync cron job which used to run in the old infrastructure is still needed (and I think it is, but it hasn't been configured yet).
TADs and everything else are OK. I went through your completion report, I don't have anything to add.
Julieta.