| Panel | |
|---|---|
Table of Contents
|
...
IRMIS Overview
"IRMIS is a collaborative effort between several EPICS sites to build a common Relational DataBase schema and a set of tools to populate and search an RDB that contains information about the operational EPICS IOCs installed at that site." IRMIS (the schema, crawler programs and UI) was developed by Don Dohan and Claude Saunders at APS. For general information and distributions see the IRMIS home page.
...
description | cvs root | production directory tree root | details |
|---|---|---|---|
IRMIS software | SLAC code has diverged from the original collaboration version, and LCLS IRMIS code has diverged from the main SLAC code (i.e. we have 2 different version of the IRMIS PV crawler.) | CD: |
|
CD scripts | For ease and clarity, the CD scripts are also in the LCLS CVS repository under | /afs/slac/g/cd/tools/irmis |
|
LCLS scripts | /afs/slac/g/lcls/cvs | /usr/local/lcls/tools/irmis |
|
FACET scripts | These scripts share the LCLS repository (different names so they don’t collide with LCLS scripts) | /usr/local/facet/tools/irmis | |
|
...
You can also see a complete listing of data_validation_audit entries in reverse chron order by using AIDA (but you will have to pick out the IRMISDB lines):
- Launch AIDA web https://mccas1.slac.stanford.edu/aidaweb
- In the query line, enter LCLS//DBValidationStatus
** Please focus only on entries where schema_nm is IRMISDB. This report shows entries for ALL of our database operations; sometimes entries from different systems are interleaved.*
...
- step launched but didn’t finish: check the status of processes launched by the cron job using ps –ef --ef | grep. An example: when perl dbi was hanging due to the 199-day-Linux-server-uptime bug. Several LCLS PV crawler jobs had launched, but had hung in the db_connect statement, and had to be killed from the Linux command line.
- step launched and finished, but the completed step was never written: the getPwd problems cause this symptom. See entries starting 9/23 9 pm for an illustration.
- step never launched: is the script available? Is the server up? Is crontab/trscrontab configured correctly? Are there permission problems? etc.
- other mysteries: figure out where the job in question stopped, using ps –ef--ef, logfiles, etc…
- Logfile messages sent in e-mail:
- Duplicate PV report (lcls only near the top of the message)
Forward these to the relevant IOC Engineer. - List of IOCs with PV counts that changed during the current crawl (lcls only near the top of the message) – helpful for figuring out a big PV count drop
- IOCS not found in IRMIS, added to IOC table (lcls only) – nice to know which new IOCs were just added.
If an IOC directory in $IOC is not in the IRMIS IOC database table yet, IRMIS will automatically add it, and produce a message which you'll see here. - PV Crawler log messages
Don't worry about "expecting 3 arguments to nfsMount"!
Quickly check "Could not locate" - usually an IOC dir that isn't quite in production yet.
You can send a message to the IOC engineer if you see " unreachable" - it could be a typo, or it could be intentional.
A "Could not locate" an st.cmd file will create "Parse error: 2" messages, which can be ignored if the IOC isn't in production.
- Duplicate PV report (lcls only near the top of the message)
...