" define what and how should be launched.
usage: nagrun.sh -v <vo> -d <dest> [-b <broker_uri>]
[-n <broker_network>] [-t <timeout>] [-w <fw_verb>]
[-z <metric_verb>] [-f <fqan>] [-i <host:port,..>] -B -R -N -h -m
-v and -d (if not -m) are mandatory paramters. Defaults:
<broker_network> - PROD
<timeout> - 600 sec
<metrics_verb> - 0
<fw_verb> - 1 (2 - messages, 3 - Nagios config/stats/debug)
-f <fqan> - VOMS FQAN
-B - don't do broker discovery
-R - take MB randomly; by default sort by min response time
-N - don't run WN tests
-m - don't use mta service to transfer messages
In most cases the parameters is the translation of corresponding ones given to emi.cream.CREAMCE-JobState metric.
emi.cream.CREAMCE-JobState |
nagrun.sh |
--mb-network <net> Brokers network for broker discovery on WN. |
-n <broker_network> |
--mb-uri <URI> Message Broker URI. |
-b <broker_uri> |
--mb-destination <dest> queue/topic on MB to publish to. |
-d <dest> |
--mb-no-discovery Do not do broker discovery on WN. |
-B |
--mb-choice <best or random> How to choose MB on WN. |
-R |
--vo <name> Virtual Organization. |
-v <vo> |
--vo-fqan <name> VOMS primary attribute as FQAN. |
-f <fqan> |
--wn-verb <0-3> Metrics verbosity level on WN. |
-z <metric_verb> |
--wn-verb-fw <0-3> Framework verbosity level on WN. |
-w <fw_verb> |
--timeout-wnjob-global <sec> Global timeout for a job on WN. |
-t <timeout> |
--no-mb |
-m |
emi.wms.CREAMCE-JobMonit
Monitors status of all submitted jobs (as defined in activejob.map
files) and updates states of emi.cream.CREAMCE-JobState and emi.wms.CREAMCE-JobMonit metrics. Acts as a babysitter for all grid jobs submitted by emi.cream.CREAMCE-JobState. emi.cream.CREAMCE-JobState and emi.cream.CREAMCE-JobMonit are updated (as passive checks) either via Nagios command file or NSCA. It accepts these parameters:
--timeout-job-global <sec> Global timeout for jobs. Job will be cancelled and dropped
if it is not in terminal state by that time. (Default: 3300)
--timeout-job-waiting <sec> Time allowed for a job to stay in Waiting with 'no compatible
resources'. (Default: 2700)
--timeout-job-discard <sec> Discard job after the timeout. (Default: 21600)
--timeout-job-schedrun <sec> Scheduled/Running states timeout. (Default: 19800)
--hosts <h1,h2,..> Comma-separated list of CE hostnames to run the monitor on.
WN Probes
Using the default wntag directory emi.wn
these probes are performed on the worker node using the wrapper samtest-run
:
- WN-csh
- WN-softver
- WN-brokerinfo
WN-csh
Checking if CSH works running the command: /bin/csh -c "env|sort" > env-csh.txt
and then cheking if the variable PATH
is defined. Accept only the parameter: debug
.
Example of a message sent as output:
serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-Csh
summaryData: OK
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:36Z
nagiosName: emi.wn.WN-Csh-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if CSH works\nTest: OK.\n
WN-softver
Detects the version of software which is really installed on the WN. To detect the version lcg-version
, glite-version
commands and the cat of the /etc/emi-version
file are tried and if the commands are not available the script exits with an error.
Example of a message sent as output:
serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-SoftVer
summaryData: OK: EMI 1.2.0-1
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:37Z
nagiosName: emi.wn.WN-SoftVer-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Installed software version\n+ type=unknow\n+ mwver=error\n+ type -f glite-version\n/home/dteam009/home_cre30_262167654/CREAM262167654/nagios/probes/emi.wn/sam/WN-softver: line 31: type: glite-version: not found\n+ '[' -f /etc/emi-version ']'\n+ type=EMI\n++ cat /etc/emi-version\n+ mwver=1.2.0-1\n+ set +x\nVersion pattern: ^2\\.[456789]OR^3\\.OR^1\\.\nDeducted middleware version: EMI 1.2.0-1\n
WN-brokerinfo
Check if BrokerInfo works. The procedure is the following:
- Firstly check if BrokerInfo file is defined in
$GLITE_WMS_RB_BROKERINFO
, $GLITE_WL_RB_BROKERINFO
or $EDG_WL_RB_BROKERINFO
variables
- Then try to get CE host name using
edg-brokerinfo getCE
or glite-brokerinfo getCE
command respectively. If previous command result value is different from 0 test is failed.
Example of a message sent as output:
serviceURI: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: FAKE-SITE
metricStatus: OK
metricName: emi.wn.WN-Bi
summaryData: OK: getCE: cream-30.pd.infn.it:8443/cream-pbs-creamtest2
gatheredAt: cream-wn-030.pn.pd.infn.it
timestamp: 2011-09-22T15:25:35Z
nagiosName: emi.wn.WN-Bi-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if BrokerInfo works\nBrokerInfo file: /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n+ ls -l /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n-rw-r--r-- 1 dteam009 dteam 367 Sep 22 17:25 /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\n+ set +x\nCheck if we can get the name of CE using glite-brokerinfo command\n+ glite-brokerinfo -v getCE\nBrokerInfo::getBIFileName(): /home/dteam009/home_cre30_262167654/CREAM262167654/.BrokerInfo\nBrokerInfo::getCE(): \n -> cream-30.pd.infn.it:8443/cream-pbs-creamtest2\n -> BI_SUCCESS\n+ result=0\n+ set +x\n
Test
To test the probe you have to create a valid proxy.
State + Monit + Cancel
First you have to "submit" a jdl:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobState --wms <WMS hostname> --no-mb
[ale@cream-48 ~]$ /usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo dteam -x /tmp/x509up_u501 -H cream-19.pd.infn.it -m emi.cream.CREAMCE-JobState --wms cream-45.pd.infn.it --no-mb
OK: [Submitted]
OK: [Submitted]
Connecting to the service https://cream-45.pd.infn.it:7443/glite_wms_wmproxy_server
====================== glite-wms-job-submit Success ======================
The job has been successfully submitted to the WMProxy
Your job identifier is:
https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
The job identifier has been saved in the following file:
/var/lib/gridprobes/dteam/emi.cream/CREAMCE/cream-19.pd.infn.it/jobID
==========================================================================
You can "monitor" the job:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobMonit --pass-check-dest active
[ale@cream-48 ~]$ /usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo dteam -x /tmp/x509up_u501 -H cream-19.pd.infn.it -m emi.cream.CREAMCE-JobMonit --pass-check-dest active
metric results >>> <cream-19.pd.infn.it,emi.cream.CREAMCE-JobState-dteam>
OK: [Scheduled] https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
OK: [Scheduled] https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
Testing from: cream-48.pd.infn.it
DN: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Alessio Gianelle/CN=proxy
VOMS FQANs: /dteam/Role=NULL/Capability=NULL, /dteam/NGI_IT/Role=NULL/Capability=NULL
glite-wms-job-status https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:
Status info for the Job : https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
Current Status: Scheduled
Status Reason: unavailable
Destination: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
Submitted: Wed Nov 9 16:43:31 2011 CET
==========================================================================
OK: Jobs processed - 1
OK: Jobs processed - 1
[Scheduled] : 1|jobs_processed=1;; DONE=0;; RUNNING=0;; SCHEDULED=1;; SUBMITTED=0;; READY=0;; WAITING=0;; WAITING-CANCELLED=0;; WAITING-CANCEL=0;; ABORTED=0;; CANCELLED=0;; CLEARED=0;; MISSED=0;; UNDETERMINED=0;; unknown=0;1;2
Before it finishes you can "cancel" it:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobCancel
[ale@cream-48 ~]$ /usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo dteam -x /tmp/x509up_u501 -H cream-19.pd.infn.it -m emi.cream.CREAMCE-JobCancel
OK: job cancelled
OK: job cancelled
Testing from: cream-48.pd.infn.it
DN: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Alessio Gianelle/CN=proxy
VOMS FQANs: /dteam/Role=NULL/Capability=NULL, /dteam/NGI_IT/Role=NULL/Capability=NULL
Job cancellation request sent:
glite-wms-job-cancel --noint -i /var/lib/gridprobes/dteam/emi.cream/CREAMCE/cream-19.pd.infn.it/jobID
Job bookkeeping files deleted.
You can verify that it works correctly checking the status of the job.
[ale@cream-48 ~]$ glite-wms-job-status https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:
Status info for the Job : https://cream-45.pd.infn.it:9000/fvNWcPJ6nVXAQJqhuU29-g
Current Status: Cancelled
Destination: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
Submitted: Wed Nov 9 16:43:31 2011 CET
==========================================================================
State + Monit without notification
As before submit a job disabling the messages transfer (option --no-mb):
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobState --wms <WMS hostname> --no-mb
Then you can monitor the job until it ends:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobMonit --pass-check-dest active
At the end when job finished the execution of the emi.cream.CREAMCE-JobMonit metrics should trigger also a get_output
[ale@cream-48 ~]$ /usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo dteam -x /tmp/x509up_u501 -H cream-19.pd.infn.it -m emi.cream.CREAMCE-JobMonit --pass-check-dest active
metric results >>> <cream-19.pd.infn.it,emi.cream.CREAMCE-JobSubmit-dteam>
OK: success.
OK: success.
Testing from: cream-48.pd.infn.it
DN: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Alessio Gianelle/CN=proxy
VOMS FQANs: /dteam/Role=NULL/Capability=NULL, /dteam/NGI_IT/Role=NULL/Capability=NULL
glite-wms-job-status https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:
Status info for the Job : https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
Current Status: Done (Success)
Exit code: 0
Status Reason: Job Terminated Successfully
Destination: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
Submitted: Wed Nov 9 18:11:03 2011 CET
==========================================================================
Getting job output: OK.
metric results >>> <cream-19.pd.infn.it,emi.cream.CREAMCE-JobState-dteam>
OK: success.
OK: success.
Testing from: cream-48.pd.infn.it
DN: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Alessio Gianelle/CN=proxy
VOMS FQANs: /dteam/Role=NULL/Capability=NULL, /dteam/NGI_IT/Role=NULL/Capability=NULL
glite-wms-job-status https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:
Status info for the Job : https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
Current Status: Done (Success)
Exit code: 0
Status Reason: Job Terminated Successfully
Destination: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
Submitted: Wed Nov 9 18:11:03 2011 CET
==========================================================================
Getting job output: OK.
OK: Jobs processed - 1
OK: Jobs processed - 1
Done : 1|jobs_processed=1;; DONE=1;; RUNNING=0;; SCHEDULED=0;; SUBMITTED=0;; READY=0;; WAITING=0;; WAITING-CANCELLED=0;; WAITING-CANCEL=0;; ABORTED=0;; CANCELLED=0;; CLEARED=0;; MISSED=0;; UNDETERMINED=0;; unknown=0;1;2
You can verify that it works correctly checking the status of the job.
[ale@cream-48 ~]$ glite-wms-job-status https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
======================= glite-wms-job-status Success =====================
BOOKKEEPING INFORMATION:
Status info for the Job : https://cream-45.pd.infn.it:9000/qAAznOmFalzWi5eTYrjAlQ
Current Status: Cleared
Status Reason: user retrieved output sandbox
Destination: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
Submitted: Wed Nov 9 18:11:03 2011 CET
==========================================================================
To check that metrics on the worker node run correctly you can edit the output files in /var/lib/gridprobes/<VO or FQAN>/emi.cream/CREAMCE/<hostname>/jobOutput
[ale@cream-48 ~]$ ls /var/lib/gridprobes/dteam/emi.cream/CREAMCE/cream-19.pd.infn.it/jobOutput/ale_qAAznOmFalzWi5eTYrjAlQ/
gridjob.out wnlogs.tgz
In gridjob.out you should found job's output; if all goes well at the end of the file there should be some lines like these:
>>>>>>>>>>>>>>>>>> Wed Nov 9 18:11:35 CET 2011
T |S |c |U |O |W |C |A |P |
3 |3 |3 |0 |3 |0 |0 |3 |0 |
Services Total 3 Checked: 3
All services were checked. Killing Nagios.
These lines are returned by nagiostats with this meaning:
T |
NUMSERVICES |
total number of services. |
S |
NUMSVCSCHEDULED |
number of services that are currently scheduled to be checked. |
c |
NUMSVCCHECKED |
number of services that have been checked since start. |
U |
NUMSVCUNKN |
number of services UNKNOWN. |
O |
NUMSVCOK |
number of services OK. |
W |
NUMSVCWARN |
number of services WARNING. |
C |
NUMSVCCRIT |
number of services CRITICAL. |
A |
NUMACTSVCCHECKS1M |
number of total active service checks occuring in last minute. |
P |
NUMPSVSVCCHECKS1M |
number of passive host checks occuring in last minute. |
wnlogs.tgz contains also the output mail-messages from the singles worker node metrics:
[ale@cream-48 ~]$ tar ztvf /var/lib/gridprobes/dteam/emi.cream/CREAMCE/cream-19.pd.infn.it/jobOutput/ale_qAAznOmFalzWi5eTYrjAlQ/wnlogs.tgz
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:35 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:02 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/archives/
-rw-r--r-- dteam017/dteam 5804 2011-11-09 18:11:26 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/objects.cache
-rw-r--r-- dteam017/dteam 69232 2011-11-09 18:11:35 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/nagios.debug
-rw-r--r-- dteam017/dteam 920 2011-11-09 18:11:35 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/nagios.log
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:02 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/rw/
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:02 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/spool/
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:32 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/var/spool/checkresults/
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:02 home/dteam017/home_cre19_460125504/CREAM460125504/nagios/tmp/
drwxr-xr-x dteam017/dteam 0 2011-11-09 18:11:30 tmp/sam.26154.23590/msg-outgoing/
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:32 tmp/sam.26154.23590/msg-outgoing/temporary/
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:32 tmp/sam.26154.23590/msg-outgoing/00000000/
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:30 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab442089af6/
-rw-rw-r-- dteam017/dteam 1019 2011-11-09 18:11:30 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab442089af6/text_body
-rw-rw-r-- dteam017/dteam 83 2011-11-09 18:11:30 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab442089af6/header
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:32 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44404d0fc/
-rw-rw-r-- dteam017/dteam 659 2011-11-09 18:11:32 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44404d0fc/text_body
-rw-rw-r-- dteam017/dteam 83 2011-11-09 18:11:32 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44404d0fc/header
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:31 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44306bbab/
-rw-rw-r-- dteam017/dteam 397 2011-11-09 18:11:31 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44306bbab/text_body
-rw-rw-r-- dteam017/dteam 83 2011-11-09 18:11:31 tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44306bbab/header
drwxrwxr-x dteam017/dteam 0 2011-11-09 18:11:30 tmp/sam.26154.23590/msg-outgoing/obsolete/
Looking inside them you should found the output of the emi.wn.WN-Csh metrics:
[ale@cream-48 tmp]$ cat tmp/sam.26154.23590/msg-outgoing/00000000/4ebab44306bbab/text_body
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-Csh
summaryData: OK
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-09T17:11:31Z
nagiosName: emi.wn.WN-Csh-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if CSH works\nTest: OK.\n
EOT
Of the emi.wn.WN-SoftVer metrics:
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-SoftVer
summaryData: OK: gLite 3.1.0
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-09T17:11:32Z
nagiosName: emi.wn.WN-SoftVer-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Installed software version\n+ type=unknow\n+ mwver=error\n+ type -f glite-version\nglite-version is /opt/glite/bin/glite-version\n+ type=gLite\n++ glite-version\n+ mwver=3.1.0\n+ set +x\nVersion pattern: ^2\\.[456789]OR^3\\.OR^1\\.\nDeducted middleware version: gLite 3.1.0\n
EOT
Of the emi.wn.WN-Bi metrics:
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-Bi
summaryData: OK: getCE: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-09T17:11:30Z
nagiosName: emi.wn.WN-Bi-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if BrokerInfo works\nBrokerInfo file: /home/dteam017/home_cre19_460125504/CREAM460125504/.BrokerInfo\n+ ls -l /home/dteam017/home_cre19_460125504/CREAM460125504/.BrokerInfo\n-rw-r--r-- 1 dteam017 dteam 367 Nov 9 18:11 /home/dteam017/home_cre19_460125504/CREAM460125504/.BrokerInfo\n+ set +x\nCheck if we can get the name of CE using glite-brokerinfo command\n+ glite-brokerinfo -v getCE\nBrokerInfo::getBIFileName(): /home/dteam017/home_cre19_460125504/CREAM460125504/.BrokerInfo\nBrokerInfo::getCE(): \n -> cream-19.pd.infn.it:8443/cream-lsf-creamcert2\n -> BI_SUCCESS\n+ result=0\n+ set +x\n
EOT
State + Monit with notification
To test also the mechanism of messages transfer you need to install a Message Broker.
Then you can "submit" a job using this command:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobState --wms <WMS hostname> --mb-uri <Message Broker URI> --mb-destination <Message Broker destination>
[ale@cream-48 ~]$ /usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo dteam -x /tmp/x509up_u501 -H cream-19.pd.infn.it -m emi.cream.CREAMCE-JobState --wms cream-45.pd.infn.it --mb-uri stomp://cream-12.pd.infn.it:61613 --mb-destination /tmp/msg
OK: [Submitted]
OK: [Submitted]
Connecting to the service https://cream-45.pd.infn.it:7443/glite_wms_wmproxy_server
====================== glite-wms-job-submit Success ======================
The job has been successfully submitted to the WMProxy
Your job identifier is:
https://cream-45.pd.infn.it:9000/3sqXvSstpobzaQhTzWNH4Q
The job identifier has been saved in the following file:
/var/lib/gridprobes/dteam/emi.cream/CREAMCE/cream-19.pd.infn.it/jobID
==========================================================================
Again you can, as usual, monitor the job until it terminates:
/usr/libexec/grid-monitoring/probes/emi.cream/CREAMCE-probe --vo <vo> -x <path of the proxy> -H <CREAM-ce hostname> -m emi.cream.CREAMCE-JobMonit --pass-check-dest active
At the end you can do the same checks as in the previous test, but also you can check the log of the Message Broker Server to see if it receives the messages, as in this example:
2011-11-10 11:17:36,856 [Thread-2] coilmq.server.socketserver.StompRequestHandler - DEBUG - Processing frame: SEND
content-length:1020
ROC:UNDEFINED
sitename:INFN-EMITESTBED
destination:/tmp/msg
persistent:true
nagios_host:localhost.localdomain
role:site
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-Bi
summaryData: OK: getCE: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-10T10:17:36Z
nagiosName: emi.wn.WN-Bi-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if BrokerInfo works\nBrokerInfo file: /home/dteam017/home_cre19_378000412/CREAM378000412/.BrokerInfo\n+ ls -l /home/dteam017/home_cre19_378000412/CREAM378000412/.BrokerInfo\n-rw-r--r-- 1 dteam017 dteam 2282 Nov 10 11:17 /home/dteam017/home_cre19_378000412/CREAM378000412/.BrokerInfo\n+ set +x\nCheck if we can get the name of CE using glite-brokerinfo command\n+ glite-brokerinfo -v getCE\nBrokerInfo::getBIFileName(): /home/dteam017/home_cre19_378000412/CREAM378000412/.BrokerInfo\nBrokerInfo::getCE(): \n -> cream-19.pd.infn.it:8443/cream-lsf-creamcert2\n -> BI_SUCCESS\n+ result=0\n+ set +x\n
EOT
2011-11-10 11:17:37,854 [Thread-2] coilmq.server.socketserver.StompRequestHandler - DEBUG - Processing frame: SEND
content-length:397
ROC:UNDEFINED
sitename:INFN-EMITESTBED
destination:/tmp/msg
persistent:true
nagios_host:localhost.localdomain
role:site
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-Csh
summaryData: OK
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-10T10:17:37Z
nagiosName: emi.wn.WN-Csh-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Checking if CSH works\nTest: OK.\n
EOT
2011-11-10 11:17:38,854 [Thread-2] coilmq.server.socketserver.StompRequestHandler - DEBUG - Processing frame: SEND
content-length:659
ROC:UNDEFINED
sitename:INFN-EMITESTBED
destination:/tmp/msg
persistent:true
nagios_host:localhost.localdomain
role:site
serviceURI: cream-19.pd.infn.it:8443/cream-lsf-creamcert2
hostName: localhost.localdomain
serviceFlavour: CE
siteName: INFN-EMITESTBED
metricStatus: OK
metricName: emi.wn.WN-SoftVer
summaryData: OK: gLite 3.1.0
gatheredAt: cream-wn-007.pn.pd.infn.it
timestamp: 2011-11-10T10:17:38Z
nagiosName: emi.wn.WN-SoftVer-dteam
role: site
voName: dteam
serviceType: emi.wn.WN
detailsData: Installed software version\n+ type=unknow\n+ mwver=error\n+ type -f glite-version\nglite-version is /opt/glite/bin/glite-version\n+ type=gLite\n++ glite-version\n+ mwver=3.1.0\n+ set +x\nVersion pattern: ^2\\.[456789]OR^3\\.OR^1\\.\nDeducted middleware version: gLite 3.1.0\n
EOT