Project

General

Profile

Actions

Task #11522

closed

Provide a cronjob for removing old access.log files

Added by Roberto Cirillo about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Urgent
Category:
System Application
Target version:
Start date:
Mar 26, 2018
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Pre-Production, Production

Description

As done for

gcube@node66.p.d4science.research-infrastructures.eu

we should also add the same cronjob to

gcube3@node1.p.d4science.research-infrastructures.eu

Related issues

Related to D4Science Infrastructure - Task #10954: There is no limit to the access log file numberClosedTommaso PiccioliJan 17, 2018

Actions
Related to D4Science Infrastructure - Task #13043: Provide a cronjob for removing old access.log files on IS-Registry instancesClosedRoberto CirilloDec 14, 2018

Actions
Actions #1

Updated by Roberto Cirillo about 7 years ago

  • Related to Task #10954: There is no limit to the access log file number added
Actions #2

Updated by Andrea Dell'Amico about 7 years ago

Was the change on node66 done manually or by ansible?

Actions #3

Updated by Roberto Cirillo about 7 years ago

I guess it was done manually by @tommaso.piccioli@isti.cnr.it

Actions #4

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from New to In Progress
Actions #5

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

In installed the cron jobs for the users gcube and gcube3.

Actions #6

Updated by Andrea Dell'Amico about 7 years ago

  • Status changed from Feedback to Closed
Actions #7

Updated by Tommaso Piccioli over 6 years ago

  • Status changed from Closed to In Progress

There are still problems with the "rotate and delete log", at least on these hosts:

collector-d4research.d4science.org
collector-pre.d4science.org

Actions #8

Updated by Tommaso Piccioli over 6 years ago

  • Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo
Actions #9

Updated by Roberto Cirillo over 6 years ago

  • Assignee changed from Roberto Cirillo to Tommaso Piccioli
  • Infrastructure Pre-Production added

The same cronjob should be added to all the collector instances.
Please could you add it to the following production/preproduction instances?

collector-d4research.d4science.org
gcube2@node24.p.d4science.research-infrastructures.eu
collector-d4os.d4science.org
collector-pre.d4science.org
collector-sbd.d4science.org
collector-parthenosvo.d4science.org
collector-openaire.d4science.org
Actions #10

Updated by Roberto Cirillo over 6 years ago

  • Priority changed from Normal to High

Right now, I've removed manually the access log from node24.p.d4science and collector-d4research.d4science.org

Please could you plan this activity?

Actions #11

Updated by Roberto Cirillo over 6 years ago

  • % Done changed from 100 to 0
Actions #12

Updated by Roberto Cirillo over 6 years ago

  • Assignee changed from Tommaso Piccioli to _InfraScience Systems Engineer
  • Priority changed from High to Urgent

Again the same problem on collector-d4research and collector-openaire. This time I'm not going to remove the logs manually.
Please could you add the cronjob on all the collectors?

Actions #13

Updated by Andrea Dell'Amico over 6 years ago

  • Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo
  • % Done changed from 0 to 40

See https://support.d4science.org/projects/aginfraplut/wiki/GCore_based_services for the documentation on how to configure the nodes before provisioning them with a cron job that removes the old logs.
In the VMs were a cron job was manually installed, the old cron job must be manually removed or it will run twice (not a big deal).

You can run the playbook with the following command:

./run.sh ghn-node.yml -i inventory/hosts.pre -l <host_name|host_group> -t gcore_cron

You can also use the more fine grained tag gcore_logs if you don't want to manage the cron job that restarts the services. I'll not run that job, the ghn inventory is a bit of a mess and you know the hosts better than me.

Actions #14

Updated by Roberto Cirillo over 6 years ago

Ok. I'm going to run it, in order to test it, in preproduction environment, on collector-pre.d4science.org host.

Actions #15

Updated by Roberto Cirillo over 6 years ago

The cronjob have been properly installed on collector-pre. I'm going to install it on the other hosts.

Actions #16

Updated by Roberto Cirillo over 6 years ago

Added to:

collector-d4research.d4science.org
node24.p.d4science.research-infrastructures.eu
collector-sbd.d4science.org
Actions #17

Updated by Roberto Cirillo over 6 years ago

  • % Done changed from 40 to 90

Added to the following hosts:

collector-d4os.d4science.org
collector-parthenosvo.d4science.org
collector-openaire.d4science.org

Actions #18

Updated by Roberto Cirillo over 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

Added also on root-vo collector. I'm going to set to feedback this ticket in order to check tomorrow if the job works as expected

Actions #19

Updated by Roberto Cirillo over 6 years ago

  • Status changed from Closed to In Progress
Actions #20

Updated by Roberto Cirillo over 6 years ago

  • Status changed from In Progress to Feedback
Actions #21

Updated by Roberto Cirillo over 6 years ago

  • Status changed from Feedback to Closed

The job works properly

Actions #22

Updated by Roberto Cirillo over 6 years ago

  • Related to Task #13043: Provide a cronjob for removing old access.log files on IS-Registry instances added
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)