APC AP9212 User's Guide Page 84
- Page / 147
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
84
10.3 Failure and fault analysis
As the complexity of any system grows, so does the likelihood of a individual components failure.
The consequences of this failure are unique to every system. This highlights the need to analyse
the system and identify faults that can occur and how these faults will propagate through the
system, on both a hardware and a software level. The following questions should be considered
when designing a control system:
• What potential faults can occur and how serious are they?
• How can software accurately become aware of these faults ?
• What action can be taken to recover ?
• How will this fault propagate to other devices in the System ?
• Can additional hardware be added to the system to more effectively diagnose these
faults ?
This information would encourage the development of a more reliable software system capable
of detecting and recovering from failures.
10.4 Logging analysis
10.4.1 Overview
In virtually every complex software system, various log files are used for monitoring and
debugging the software. This characteristic is shared by both the APT and the Spectrum Scanner
software through the use of the java.util.logging framework. Operating Systems are also an
example of this. Unix/Linux based operating systems log system messages to
/var/adm/messages
i
whereas WindowsNT messages can viewed with the Event Viewer.
In any software failure, analysis of these log files is generally the standard procedure for
identifying the cause of the problem. Particularly when the system is controlled remotely. This
analysis can often be very time consuming due to the verbosity and sheer size of log information.
Command line tools such as grep, tail, more, and less are often used in this kind of
analysis. These are inadequate, particularly for Java based systems, for several reasons:
• Log messages can be on more than one line (eg Java stack traces).
• Some log messages are longer than 80 characters.
• Log messages cannot be filtered according to their severity.
• Searches are limited to plain text as opposed to log record types and attributes.
Given these shortcomings of the current log analysis tools, a specification for an ideal tool can
be defined.
10.4.2 Analysis tool specification
The aim is to provide a graphical based tool to analyse log file data using searching, filtering and
masking techniques. The power of this tool is drawn from the fact that LogRecord data types
can be searched, rather than just plain text.
i
The path of the messages log file varies between differnts distrubutions
- Oliver Mather 1
- Abstract 3
- Acknowledgements 5
- Contents 7
- List of Figures 9
- 1 Introduction 11
- 2 APT hardware 13
- 2.3 Mistral 14
- 2.4 Telescope 14
- 2.5 CCD 16
- 2.6 Telescope movement 16
- 2.6.1 Anti backlash motor 17
- 2.6.2 Limit switches 18
- 2.6.3 Tilt sensor 19
- 2.6.4 Macrostation 19
- 2.7 Masterswitch 20
- 2.8 Web cameras 21
- 2.10 Roof 22
- 2.11 ROTSE 23
- ParralelRS232RS232 24
- 3 APT software 25
- 3.3 Command line tools 26
- 3.4.1 Introduction 27
- 3.4.2 Architecture 27
- 3.5 APT server 28
- 4.1 Introduction 31
- 4.3 Code 32
- 4.3.2 Configuration 33
- 4.3.3 SNMP messages 33
- 4.4 JAS integration 34
- 4.4.1 Commands 35
- 4.4.2 Messages 36
- 4.5 Screenshots 37
- 4.6 Conclusion 38
- 5.1 Introduction 39
- 5.2 Architecture 40
- 5.3 Process manager 40
- 5.4 Roof 41
- 5.5 Chat system 43
- Figure 5-8 APT chat system 44
- 5.6 Look and Feel 45
- 5.6.2 Problems 46
- 5.6.3 Screenshots 46
- 5.7 Conclusion 47
- 6 APT software deployment 49
- 6.3.1 Versioning 50
- 6.3.2 Security 51
- 6.4 Compilation 52
- 6.5 Version synchronisation 55
- 6.6 Uploading 56
- 6.7 Conclusion 57
- 7.1 Introduction 59
- 7.2 Hardware 59
- 7.3 Software 59
- 7.3.2 Maintenance 60
- 7.3.3 Client SP server 60
- 7.3.4 Client error control 60
- 7.4 Conclusion 62
- 8 SkinnedTextField 63
- 8.4 TextSkin 64
- 8.5 SkinnedTextFieldDemo 65
- 9 CSIRO SEARFE project 69
- 9.3 Requirements 70
- 9.4 Hardware 71
- 9.5 Architecture 71
- 9.5.1 Data files 72
- 9.6 User interface 73
- 9.6.2 Data visualisation 76
- 9.7.1 Visualisations 80
- 9.8 Conclusion 81
- 10 Conclusion 83
- 10.4 Logging analysis 84
- Bibliography 87
- A. Glossary 89
- B.1. Introduction 91
- B.2. JAS message sender 91
- B.4. Creating JAS commands 91
- B.4.1. JASCommand object 92
- B.4.2. Installing commands 92
- B.5. JAS channel monitoring 93
- C. Software tools 95
- C.1.3. Checkout the code 96
- C.1.4. CVS user interfaces 96
- D. SNMP overview 97
- Response 98
- RequestRequest 98
- E. Astronomy primer 99
- E.1.3. Coordinate epochs 100
- E.2. Astronomical times 101
- E.3. Gamma ray bursts 102
- E.4. Astronomical filters 102
- E.5. Flat fielding 103
- E.6. Cosmic rays 103
- F. Selected code listings 105
- F.1.6. SnmpTrapDaemon.java 121
- F.2. APT deployment system 132
- F.2.3. apt build.xml 134
- F.2.4. lib build.xml 141
- F.3. CSIRO / SEARFE 144
- F.4. TextSkin 145
Related products and manuals for Network switches APC AP9212
Network switches APC AP9217 User Manual
(10 pages)
(10 pages)
Network switches APC AP5202 Specifications
(20 pages)
(20 pages)
Network switches APC EP Zero ARF User Manual
(16 pages)
(16 pages)
Network switches APC AP9225 User's Guide
(67 pages)
(67 pages)
Network switches APC UTS6BI User Manual
(15 pages)
(15 pages)
Network switches APC UTS6H Specifications
(68 pages)
(68 pages)
Network switches APC AP9258 User Manual
(4 pages)
(4 pages)
© 2020, manymanuals.com. All rights reserved. | 1.607 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals