Search results
Jump to navigation
Jump to search
- '''Actions/nagios issues''': see RT queue [https://rt.egi.eu/rt/Search/Results.html?Query=Que *ARC expert team - NGI_CH, NGI_FI, NGI_UA, EMI (Petter Urkedal)2 KB (330 words) - 13:53, 19 June 2015
- == 2.2 New Nagios Probes == === 2.2.1 CREAM & WN restructured probes ===4 KB (503 words) - 15:17, 10 March 2014
- * Probes: https://poem.egi.eu/poem/admin/poem/public_probe/ | nordugrid-arc-nagios-plugins17 KB (2,286 words) - 16:53, 10 October 2019
- *'''31-08-2015''': dCache 2.6.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Dashboard ...rvice end-points according to the version information available from BDII. Probes detecting unsupported service end-points, will generate alarms that can be15 KB (2,164 words) - 19:57, 7 May 2015
- * emi-cluster v. 2.0.1 ( 7 months) == 2.2 New Nagios Probes ==5 KB (660 words) - 13:22, 2 May 2014
- = SAM Nagios probes re-factoring TF = * [[SAM Nagios probes refactoring TF]]7 KB (1,025 words) - 12:15, 13 July 2016
- ...robes are successfully integrated. At the end of the quarter following SAM/Nagios instances were in production: Detailed list of SAM/Nagios instances can be found on the following page: [[SAM Instances]].5 KB (830 words) - 18:53, 6 January 2015
- ...sion was approved by the OMB in order to enable probe developers to update probes more frequently and independently from SAM releases. ...gridmon) and its dependencies. SAM Update-23 supports only SAM Nagios (sam-nagios). In the future version SAM GridMon will be replaced with the ARGO engine.7 KB (963 words) - 10:18, 17 December 2014
- === EMI GFAL does not work with multiple BDIIs === lcg-util 1.11.18 released with EMI 1.0.0 don't support4 KB (676 words) - 19:26, 9 January 2015
- ...within the EMI and EGI projects the monitoring framework will be based on NAGIOS. This has also the advantage to ease the integration of the FedCloud monito |Peter requested enabling alternative AuthN in probes. Need to clarify in which cases is this required and optimal mechanism of d9 KB (1,323 words) - 10:26, 23 September 2015
- * Follow up of a problem with StoRM frontend which may prevent the upgrade to EMI-2 ...ion of start of campaign on 04 March. Development of probes for the entire EMI 1 stack in time for the start of the campaign was impossible due to a numbe5 KB (747 words) - 18:17, 6 January 2015
- * status assessment of EMI 1 probes * discussion of distribution and testing of EMI WN tarball3 KB (474 words) - 18:20, 6 January 2015
- ==== 1.1. Update on the status of EMI updates ==== ** EMI-1 (28.03.2013) [http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-24-28-03-2013-v-4 KB (634 words) - 13:49, 3 April 2013
- === 1.1 EMI-1 release status (Cristina) === ...h a proxy fetched from a myproxy server fails. This is the case of the SAM/Nagios tests.4 KB (595 words) - 17:15, 29 November 2012
- ** [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-19-07-08-2014- ** [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-19-07-08-2014-10 KB (1,448 words) - 17:30, 23 October 2014
- |Nagios Probes Task Force Meeting (2nd EMI All Hands Meeting) |Presentation and planning of probe handover to EMI product teams.4 KB (585 words) - 18:59, 6 January 2015
- ...Croatian NGI participates in staged rollout of APEL and in some cases SAM/Nagios. At the beginning of project software release procedure was not defined and ...table, but first year saw a lot of releases and changes in components. SAM/Nagios is released through official release process so major bugs are spotted befo5 KB (784 words) - 18:37, 19 December 2012
- |Arc probes revisited update |glite EMI probe review6 KB (876 words) - 19:11, 6 January 2015
- COD is involved in the process of retirement the EMI-1 middleware. In near future the EMI-1 dCache service withdrawal, that has extended6 KB (889 words) - 19:12, 6 January 2015
- ...that broke in the previous release, but there is also an extension to the emi-es schema to make it useable for ATLAS. ** [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-18-07-07-2014-10 KB (1,404 words) - 17:30, 23 October 2014
- (e.g. scripts, SAM probes), or relevant parts of the infrastructure are <![endif]-->'''<span lang="EN-GB">SAM MPI probes</span>'''596 KB (64,758 words) - 11:10, 8 February 2013
- *[http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-22-10-11-2014- * EMI-UI/WN9 KB (1,348 words) - 16:03, 18 November 2014
- * EGI/EMI meeting on MEDIA collaboration and URT activities in preparation to CF13 an * preparation of EMI 1/2 DPM decommissioning campaign6 KB (815 words) - 18:16, 6 January 2015
- * emi-cluster v. 2.0.1 ( 7 months) ** The nagios probe '''eu.egi.sec.DPM-GLUE2-EMI-1''' should be modified because it tries to detect some information that th7 KB (1,085 words) - 14:04, 5 May 2014
- ==== 1.1. Update on the status of EMI-1 release (Cristina) ==== EAs that did not yet send feedback, please do so. Plans to move to EMI components or not.<br>4 KB (626 words) - 12:24, 15 October 2012
- * kickoff meeting of working group responsible of assessing the new EMI 2/3 probes before integration into SAM * Preparation of the EMI WN-tarball, by colecting all the interested sites to serve as Early adopter4 KB (595 words) - 18:20, 6 January 2015
- * emi-cluster v. 2.0.1 ** ngi-de-nagios.gridka.de - [https://ggus.eu/index.php?mode=ticket_info&ticket_id=105128 NG7 KB (1,097 words) - 17:30, 23 October 2014
- ** EMI apel v. 2.2.0 ** EMI glexec v. 1.2.13 KB (407 words) - 18:14, 6 January 2015
- == Notifications from ARGO about the nagios probes failures == == Decommissioning EMI WMS ==9 KB (1,427 words) - 14:25, 8 October 2018
- * EMI-UI/WN * emi-wn v. 3.1.0 ('''new''')8 KB (1,131 words) - 17:31, 23 October 2014
- == Notifications from ARGO about the nagios probes failures == == Decommissioning EMI WMS ==11 KB (1,646 words) - 13:56, 10 September 2018
- ...s metapackage contains all the procedures to install and configure the EMI probes. We should assess the impact.2 KB (227 words) - 11:30, 6 January 2015
- ...that broke in the previous release, but there is also an extension to the emi-es schema to make it useable for ATLAS. * emi-cluster v. 2.0.19 KB (1,323 words) - 17:31, 23 October 2014
- ...s metapackage contains all the procedures to install and configure the EMI probes. We should assess the impact. * 7 clients now publishing using SSM 2.0/EMI 3 APEL Client;2 KB (291 words) - 11:31, 6 January 2015
- * organization of EMI WN tarball staged rollout ...G: 1 advisory issued for 'High' risk issue, which was past TD and fixed by EMI but not in UMD - issued as 'Amber'5 KB (714 words) - 18:20, 6 January 2015
- ...aining sites were moved to ROC_LA. At the end of the quarter following SAM/Nagios instances were in production: Detailed list of SAM/Nagios instances can be found on the following page: [[SAM Instances]].5 KB (773 words) - 18:53, 6 January 2015
- == Notifications from ARGO about the nagios probes failures == == Decommissioning EMI WMS ==10 KB (1,492 words) - 14:11, 12 November 2018
- * EMI repository will be shut down on June 15th, broadcast sent on May 31st https * ARC-CE probes are updated in order to mitigate the issue with missing jobs (https://ggus.10 KB (1,533 words) - 15:26, 25 October 2017
- ...nts</span>'''<span lang="EN-US"> have had their code checked</span> within EMI activities. Probes: it’s up to EMI, we should investigate with them.20 KB (2,280 words) - 17:18, 17 February 2021
- == Notifications from ARGO about the nagios probes failures == == Decommissioning EMI WMS ==10 KB (1,520 words) - 15:02, 14 January 2019
- ...s of gLite decommissioning and of preparation of EMI 1 probes to start the EMI 1 decommissioning campaign ...valuation in preparation to SAM Update 22 which will include the new EMI 2 probes6 KB (884 words) - 18:20, 6 January 2015
- ...I_IE (Ireland) and the new NGI_UK. At the end of the quarter following SAM/Nagios instances were in production: Detailed list of SAM/Nagios instances can be found on the following page: [[SAM Instances]].7 KB (1,076 words) - 19:09, 6 January 2015
- * assessment of progress of EMI-1 campaign * definition of new EMI-1 StoRM support calendar with PT5 KB (705 words) - 18:25, 6 January 2015
- * SAM: Integration of EMI probes ...uires full reinstallation of SAM instance because upgrade from gLite UI to EMI-2 is not supported. Several SAM tests were renamed which required special5 KB (707 words) - 19:58, 24 December 2014
- * EMI repository shut down on June 15th, see broadcast sent on May 31st https://o * arc-nagios-probes 1.9.13 KB (337 words) - 15:37, 24 July 2017
- ...bmission of requirement and assessment of progress of readiness for SHA-2 (EMI) *Follow up with an issue with SAM WN probes5 KB (807 words) - 17:45, 6 January 2015
- == Notifications from ARGO about the nagios probes failures == == Decommissioning EMI WMS ==12 KB (1,802 words) - 14:10, 3 July 2018
- ...www.egi.eu/indico/conferenceDisplay.py?confId=823 17/02/2012 MPI VT nagios probes meeting] # Nagios probes: New monitoring probes for the EGI Service Availability Monitor (SAM) has been defined. These wil18 KB (2,818 words) - 09:04, 18 February 2014
- == Notifications from ARGO about the nagios probes failures == ...guelcg2 https://ggus.eu/index.php?mode=ticket_info&ticket_id=134931 arc-ce probes return UNKNOWN status14 KB (2,212 words) - 12:04, 14 May 2018
- ***INFN-ROMA1-CMS: still underperforming, but the bug in the nagios probes for the CREAM (ticket GGUS 128151) is then disappeared, == Decommissioning EMI WMS ==9 KB (1,378 words) - 15:25, 25 October 2017