tomcat_mgmt/webapps/mgmt/ui/help/samples/
folder.
find /arch/tomcats -wholename '*/logs/*' -exec grep -l xception {} \;
find /arch/tomcats -wholename '*/logs/*' -exec grep -l FATAL {} \;
find /arch/tomcats -wholename '*/logs/*' -exec grep -l OutOfMemoryError {} \;
While exceptions in the retrieval and mgmt components could potentially be from user errors, any exceptions/FATAL messages in the ETL/Engine components should immediately be investigated.
getApplianceMetrics
BPL (see samples/checkConnectedPVs.py
) to monitor the number of currently disconnected PVs.
You can then send an email notification to the system administrators if this is greater than a certain percentage or absolute number.
/getPVsByDroppedEventsTypeChange
BPL (see samples/checkTypeChangedPVs.py
) to watch for any PV's that have changed type.
If a PV changes type, the EPICS archiver appliance will suspend archiving this PV until the situation is manually resolved.
/renamePV
BPL or the UI/changeTypeForPV
BPL/changeTypeForPV
alters the data that has already been archived; so you may want to make a backup first.
/getCurrentlyDisconnectedPVs
returns a list of currently disconnected PVs and some notion of when the connection to this PV was lost.
/getPausedPVsReport
) but are now alive.mysqldump
; this should be more than adequate.
mysqldump -u userid -p password archappl > /path/to/backupfile
It is also good practice to validate the backups every so often.
Most labs have some scripts that perform some basic validation of these backups. Please ask if you need more info.
mysql -u userid -p password archappl < /path/to/backupfile
Restarting the appliance after this should pick up the imported configuration.
As the JVM can cache DNS lookups, giving your replacement appliance the same IP address as the one that was lost should also help if you have a cluster of machines.
em1
between the archiver appliance and the IOC using something like so /usr/sbin/tcpdump -i em1 'host ioc_or_gateway_hostname and appliance_hostname' -w /localdisk/captured_packets
/localdisk/captured_packets
contains the packet capture and can be copied over to a dev box and inspected at leisure.tshark
like so tshark -X lua_script:ca.lua -r captured_packets 2>&1 | less
CID - Client ID
, SID - Server ID
and Subscription ID
in the PV details page.cashark
plugin to track the life cycle of the Channel Access channel.