There are several ways to monitor the Vo Frontend:
You can either monitor the frontend as a whole, or just a single entry point.
The frontend monitoring is located at a URL like the one below
Moreover, each frontend group has its own history on the Web.
Assuming you have a main group, it can be monitored at
You can get the equivalent of the Web page snaphot by using
./wmsXMLView.py -pool gfactory1.my.org
The vo frontend writes two log files per entry point frontend_info.YYYYMMDD.log and frontend_err.YYYYMMDD.log.
Assuming you have a main group, the log files are in
All errors are reported in the frontend_err.YYYYMMDD.log. file, while frontend_info.YYYYMMDD.log contains entries about what the VO frontend is doing.
The VO frontned also advertises summary information in the WMS collector.
condor_status -pool gfrontend1.my.org -any
and look for glideclient ads.
The glideinWMS also provides pseudo interactive monitoring functionalities; a user can run short lived commands alongide any already running job in the queue.
To run a pseudo interactive command, move into
./glidein_interactive.py jobid cmdline
There are also a set of useful often used commands that you may want to use:
- glidein_ls.py jobid [subdir]
- glidein_cat.py jobid fname
- glidein_top.py jobid
- glidein_ps.py jobid [opts]