Search results

Jump to: navigation, search
  • ...ng filer migration. No dates yet but it will affect ARGUS, all CEs and all batch worker nodes (glExec) running GridJobs. The downtime is foreseen to last 1h * Lydia's document - Setup a system to do data archiving using FTS3
    41 KB (5,000 words) - 04:11, 1 September 2015
  • ...ng filer migration. No dates yet but it will affect ARGUS, all CEs and all batch worker nodes (glExec) running GridJobs. The downtime is foreseen to last 1h * Lydia's document - Setup a system to do data archiving using FTS3
    43 KB (5,351 words) - 16:49, 6 September 2015
  • ...ng filer migration. No dates yet but it will affect ARGUS, all CEs and all batch worker nodes (glExec) running GridJobs. The downtime is foreseen to last 1h * Lydia's document - Setup a system to do data archiving using FTS3
    44 KB (5,604 words) - 10:22, 15 September 2015
  • ...ng filer migration. No dates yet but it will affect ARGUS, all CEs and all batch worker nodes (glExec) running GridJobs. The downtime is foreseen to last 1h * Lydia's document - Setup a system to do data archiving using FTS3
    44 KB (5,552 words) - 22:25, 19 September 2015
  • ..., following the application of the updated FTS3 software to the production system last week a memory leak was introduced which also caused a set of problems * Updating the first batch of the remaining Castor disk servers (those in tape-backed service classes)
    14 KB (1,604 words) - 12:01, 23 September 2015
  • * Lydia's document - Setup a system to do data archiving using FTS3 ...mblyness with the CEs. However, I understand much of this is caused by the batch farm being busy. There are low-availability tickets 'on hold' for Liverpool
    45 KB (5,699 words) - 08:31, 28 September 2015
  • * Lydia's document - Setup a system to do data archiving using FTS3 ...mblyness with the CEs. However, I understand much of this is caused by the batch farm being busy. There are low-availability tickets 'on hold' for Liverpool
    46 KB (5,818 words) - 10:21, 19 October 2015
  • * Lydia's document - Setup a system to do data archiving using FTS3 ...mblyness with the CEs. However, I understand much of this is caused by the batch farm being busy. There are low-availability tickets 'on hold' for Liverpool
    52 KB (6,786 words) - 16:22, 12 October 2015
  • * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail * Lydia's document - Setup a system to do data archiving using FTS3
    47 KB (6,004 words) - 20:08, 25 October 2015
  • * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail * Lydia's document - Setup a system to do data archiving using FTS3
    48 KB (6,098 words) - 09:45, 2 November 2015
  • * We have been investigating the behaviour of some batch jobs as there is a low level of failures that are not understood. * gdss664 (AtlasTape - D0T1) was removed from service on the 28th Oct. The system was having some problems running some network commands which were resolved
    12 KB (1,234 words) - 14:05, 11 November 2015
  • ...ng a disk replacement and updating the firmware in the disk controller the system was re-run through the acceptance testing for 5 days before being returned ...d battery replacement and updating the firmware in the disk controller the system was re-run through the acceptance testing for 5 days before being returned
    12 KB (1,253 words) - 10:56, 4 November 2015
  • * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail * Lydia's document - Setup a system to do data archiving using FTS3
    54 KB (7,032 words) - 12:38, 8 November 2015
  • * LHCb batch jobs failing to copy results into castor - changes made seems to have impro ...e that it is just not possible to simulate the behaviour on pre-production system. ACTIONS: RA to ensure the procedure for dealing with any recurrence of thi
    5 KB (850 words) - 11:33, 27 November 2015
  • * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail * Lydia's document - Setup a system to do data archiving using FTS3
    48 KB (6,095 words) - 12:37, 16 November 2015
  • * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail * Lydia's document - Setup a system to do data archiving using FTS3
    48 KB (6,163 words) - 16:24, 29 November 2015
  • ...- also a possible improvement in configuration, frequent write of a Oracle system log is slow and can be improved by writing to a dedicated area with a diffe * LHCb batch jobs failing to copy results into castor - changes made seems to have impro
    6 KB (1,018 words) - 12:25, 4 December 2015
  • ...repository/Technical_Documents/WLCGFutureISUseCases_1.3.pdf An Information System future use cases document has been produced]. * We are investigating why LHCB batch jobs sometimes fail to write results back to Castor (and the sometimes fail
    47 KB (5,899 words) - 20:49, 6 December 2015
  • * Approach for configuring batch systems (e.g. setting up mem limits). ...nical_Documents/WLCGFutureISUseCases_1.6.pdf PDF]). Looking at information system owned by WLCG (an interesting idea). Starting to prepare a Roadmap to GLUE
    47 KB (5,834 words) - 10:11, 11 January 2016
  • ...- also a possible improvement in configuration, frequent write of a Oracle system log is slow and can be improved by writing to a dedicated area with a diffe * LHCb batch jobs failing to copy results into castor - changes made seems to have impro
    7 KB (1,141 words) - 15:00, 11 December 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)