The Advanced Operational Aviation Weather Systemaoaws.caa.gov.tw/htdocs/projects/aoaws/doc/pdf/ops_manual.pdf · Replaced BigSister section with one on Opsview. Added SysView images

i

航空氣象現代化系統

The Advanced Operational Aviation Weather System (AOAWS)

操作手冊

OPERATORS MANUAL

交通部民用航空局

Civil Aeronautics Administration (CAA)

修訂日期:2013年9月

Updated: September 2013

美國國家大氣研究中心 (National Center for Atmospheric Research)

資拓宏宇國際股份有限公司 (International Integrated Systems, Inc. , IISI)

ii

文件修改紀錄（Updated Notes）

修改日期 Date 修改紀錄 Modification Records

2007 年 11 月 29 日

11/29/2007

新修訂

Original Version.

2008 年 9 月 21 日

9/21/2008

更新圖表及文字說明以反映 AOAWS 7.1.0.1 版本之修訂

。並增加硬碟裝置備份及還原重播的章節。

Updated images and text to reflect state of AOAWS 7.1.01. Added section on HD archive backup and playback restoration.

2009 年 11 月 17 日

11/17/2009

更新圖表及文字說明以反映 AOAWS 8.1.0.1 版本之修訂

。並增加 AISS FTP 伺服器資料傳送過程說明。

Updated to reflect state of AOAWS 8.1.01 version system. Added section on AISS FTP server file transfer processing.

2009 年 11 月 24 日

11/24/2009

更新圖表及文字說明以反映 AOAWS 8.1.0.1 版本之修

訂。刪除原 Spong 說明章節並新增 Bigsister 與 Cacti 說明

章節。更新附錄 A 之網路架構圖為 2009 年版本。

Updated to reflect state of AOAWS 8.1.01 version system.

Deleted section of Spong and added section of Bigsister and Cacti. Updated the network diagrams in appendix A to version 2009.

2010 年 11 月 12 日

11/12/2010

更新圖表及文字說明以反映 AOAWS 9.1.0.1 版本之修

訂。

Updated to reflect state of AOAWS 9.1.01 version system.

2011 年 11 月 21 日

11/21/2011

反映 10 版本更新之回顧及修訂版

Reviewed/Update for v10.

2012 年 11 月 24 日

11/24/2012

新增網路圖

利用 Opsview 部分功能取代 BigSister 章節

增加 SysView 影像圖

增加網頁監視系統之 screenshots 功能

iii

更新網路架構圖章節

更新疑難排解指南章節

Added new network diagrams.

Replaced BigSister section with one on Opsview.

Added SysView images.

Added screenshots from system monitoring web pages

Updated networking section

Updated troubleshooting section

2013 年 9 月 24 日

9/24/2013

增加圖表目錄

增加新 AWOS 站台資訊

更新資料章節

Added a table of figures.

Added information about new AWOS sites

Updated data section

iv

目錄 (Table of Contents) 1 引言 (Introduction) ................................................................................................................ 1

1.1 目的 (The purpose of this document) ............................................................................ 1

1.2 本文件之讀者 (The intended audience of this document) ............................................ 1

1.3 Linux 和 UNIX 作業系統參考文件 (Linux and UNIX documentation) ..................... 1

1.4 本文件架構 (Organization of this document) ............................................................... 2

2 系統概觀 (System overview) ................................................................................................ 3

2.1 AOAWS 網路架構 (The AOAWS network) ................................................................ 3

2.2 系統運作 (Running the system) .................................................................................... 4

2.3 啟動系統 (Starting the system) ..................................................................................... 5

2.4 檢查系統是否已啟動，且在正確運作中 (Checking that the system has started and is running correctly) .................................................................................................................... 6

2.5 停止系統 (Stopping the system) ................................................................................... 8

2.6 檢查執行中的 AOAWS 程序 (Checking the running processes) .............................. 9

2.7 檢查資料集 (Checking the data sets) .......................................................................... 12

2.8 備份資料 (Archiving the data) .................................................................................... 13

2.9 還原 MDS 資料 (Playback of the MDS data) ............................................................. 14

2.10 還原 WEB 資料 (Playback of the WEB data) ............................................................. 16

2.11 硬碟至ＤＶＤ之備份與錄像重播 (HD Archive DVD Backup and Playback Restore) 17

3 從網頁上監視系統 (Monitoring the system from the web) ............................................... 19

3.1 Opsview - 硬體及網路監視 (Opsview - hardware monitor) ..................................... 21

3.2 系統與網路流量監視 (System and network flow monitoring) .................................. 27

3.3 SysView – process 及資料監視 (SysView - the process and data monitor) .............. 29

3.4 開機時間 (Uptimes) .................................................................................................... 37

3.5 AOAWS 程序可用度 (AOAWS Process Availability) ............................................. 38

3.6 資料 (Data) .................................................................................................................. 40

3.7 WMDS 圖檔可用度 (WMDS Image Availability) .................................................... 43

3.8 備份 (Archive) ............................................................................................................. 45

3.9 資料傳送至 AISS FTP 伺服器 (File transfer to AISS FTP Server) .......................... 46

3.10 WRF 檔案之可用度 (WRF file Availability) ............................................................. 48

v

3.11 模式狀態摘要 (Model status summary) ..................................................................... 50

4 問題診斷及解決 (Diagnosing and solving problems) ........................................................... 51

4.1 引言 (Introduction) ....................................................................................................... 51

4.2 網路問題 (Network problems) ...................................................................................... 51

4.2.1 臺北航空氣象中心與網際網路主要連結 (Main link from TAMC to internet) 52

4.2.2 臺北航空氣象中心與北部飛航服務園區間之網路連結 (Fiber optic link from TAMC to ATSN)) ................................................................................................................. 52

4.2.3 北部飛航服務園區與中央氣象局間 FTTB 10M 專線 (FTTB 10M link from ATSN to CWB)..................................................................................................................... 52

4.2.4 臺北裝修區臺與松山航空氣象臺間光纖 (Fiber optic link from SSAFS to SS Weather Station) ................................................................................................................... 53

4.2.5 北部飛航服務園區與桃園氣象臺間微波網路 (Microwave link from ATSN to TTYWX) 54

4.2.6 桃園國際機場內網路 (Communications links at TIA airport) ........................... 55

4.2.7 北部飛航服務園區與高雄氣象臺間 ASN 專線 (Leased line: from ATSNto KHWX) 55

4.2.8 高雄國際機場內網路 (Communications links at KH international airport) ...... 56

4.2.9 連線到馬祖北竿機場(Communication link to RCMT) ...................................... 56

4.2.10 連線到金門機場(Communication link to RCBS) ............................................... 57

4.2.11 連線到蘭嶼機場(Communication link to RCLY) .............................................. 57

4.2.12 連線到綠島機場(Communication link to RCGI)................................................ 57

4.2.13 連線到豐年機場(Communication link to RCFN) ............................................... 57

4.2.14 連線到七美機場(Communication link to RCCM).............................................. 58

4.2.15 連線到望安機場(Communication link to RCWA) ............................................. 58

4.2.16 連線到馬祖南竿機場(Communication link to RCFG) ....................................... 58

4.2.17 臺北航空氣象中心內網路 (Communications problems at TAMC) .................. 58

4.3 資料可用性問題 (Data availability problems) ........................................................... 59

4.3.1 雷達資料 (CWB Radar data)............................................................................... 60

4.3.2 WRF 模式資料 (WRF model data) ......................................................................... 61

4.3.3 METAR、TAF、AIREP、ACARS 及 AMDAR 資料 (METAR, TAF, AIREP, ACARS and AMDAR data).................................................................................................. 62

4.3.4 衛星資料 (Satellite data) ..................................................................................... 63

4.3.5 WAFS 資料 (WAFS data) ....................................................................................... 64

vi

4.3.6 AWOS data ............................................................................................................... 64

4.4 電力問題 (Power problems) ........................................................................................ 66

4.5 作業系統問題 (Operating system problems) .............................................................. 66

4.5.1 電腦重新啟動不完全 (Computer will not reboot properly.) .............................. 67

4.6 電腦硬體問題 (Computer hardware problems) .......................................................... 67

5 疑難排解指南 (Troubleshooting guide).............................................................................. 69

0 附錄 A:網路架構圖 (Appendix A: Network diagrams) ..................................................... 71

vii

Table of Figures Figure 1 中央氣象局與臺北航空氣象中心網路圖(CWB-TAMC network diagram) ................ 3

Figure 2 臺北航空氣象中心網路圖(TAMC network diagram) ................................................... 4

Figure 3 執行"ppm"和"pdm"指令所輸出的文字內容 (Text output from 'ppm' and 'pdm' commands) .................................................................................................................................... 11

Figure 4 JMDS 中的時間與動畫選單(Time and animation selection in the JMDS).................. 15

Figure 5 JMDS 中的時間與動畫視窗(JMDS time and animation window) .............................. 16

Figure 6 備份和還原工具 GUI (Backup and restore utility GUI) ............................................... 17

Figure 7 系統監控頁面之快寫(Snapshot of System Monitor Page) .......................................... 19

Figure 8 Opsview 登入頁面(Opsview login page) ...................................................................... 21

Figure 9 Opsview 主機群摘要網頁(Opsview host group summary web page) .......................... 22

Figure 10 Opsview 主機網頁（Opsview host web page） ......................................................... 23

Figure 11 data1 之 Opsview 監控頁面(Opsview monitoring page for tamc-data1) .................... 25

Figure 12 data1 之 Opsview I/O 狀態圖(Opsview I/O Status graph for tamc-data1 ................... 26

Figure 13 Ｃacti 登入網頁（Cacti login web page） ............................................................... 27

Figure 14 Ｃacti 主機頁面（Cacti host page） ......................................................................... 28

Figure 15 AOAWS Sysview 圖檔首頁 (Top-level SysView diagram for AOAWS) ................ 30

Figure 16 Sysview 圖檔顯示程序和資料(Sysview diagram showing processes and datasets) . 31

Figure 17 程序狀態網頁範例(Example of Process Status web page) ......................................... 34

Figure 18 資料狀態網頁範例(Example of Dataset Status web page) ......................................... 36

Figure 19 正常運作時間網頁範例(Example of Uptimes web page). ......................................... 37

Figure 20 程序統計網頁範例(Example of Process Statistics web page). ................................... 39

Figure 21 資料統計網頁範例(Example of Dataset Statistics web page). ................................... 41

Figure 22 WMDS 統計網頁範例(Example of WMDS Statistics web page). ............................. 44

Figure 23 資料備份狀態網頁範例(Example of Archive Status web page). .............................. 45

Figure 24 AISS Ftp 狀態網頁範例（Example of the AISS Ftp Status web page）. .................. 47

Figure 25 WRF 模式統計網頁範例(Example of the WRF Model Statistics web page)............. 49

AOAWS Operators Manual 1 Introduction

1 引言 (Introduction)

1.1 目的 (The purpose of this document)

航空氣象現代化作業系統 (AOAWS) 是一套由資料、網路、軟硬體等設備所共同組成的

複雜系統。系統需要定時監控，並在發生問題時馬上解決它。

本操作手冊是受過訓練的系統作業人員的一份必備指南，主要目的是提供必需的資訊以協

助其在系統發生狀況時能夠識別問題所在，進而有效率地診斷及解決問題。

The AOAWS is a complex system comprising data, network, hardware and software elements. The system must be routinely monitored for problems, and action taken to correct those problems as they occur.

This document is intended to provide you, as a trained operator, with the information required to recognize problems as they occur, diagnose them and deal with them in an effective manner.

1.2 本文件之讀者 (The intended audience of this document)

本文件假設讀者具有下列各項知識與經驗：

This document assumes that you have knowledge and experience of the following:

• 有關 PC 電腦的硬體設備 (PC-based hardware).

• 基本的 UNIX 系統管理 (Basic UNIX system administration).

• 網路技術 (Networking technology).

1.3 Linux和UNIX作業系統參考文件 (Linux and UNIX documentation)

AOAWS 系統的所有主機均使用類 UNIX 作業系統的公開使用版本 Debian Linux 作業系統

。為了維護系統正常運作，系統作業人員本身需要熟悉 Linux 系統管理操作。目前的

Linux 系統是 64 位元之 Debian 6 版本。

All of the hosts in the AOAWS run under Debian Linux, an open source publicly-available operating system. In order to maintain the system you will need to be familiar with Linux.

The current version is 64-bit Debian 6 (Squeeze).

以下列出幾個 Linux 系統操作相關文件網站網址：

There are a number of good documentation sites available on the web:

• Linux 文件計畫網頁 (The Linux documentation project): http://www.tldp.org/

AOAWS Operators Manual 2 Introduction

• Debian Linux 文件網頁 (Debian Linux documentation): http://www.debian.org/doc/

• A Practical Guide to Linux Commands, Editors, and Shell Programming, by Mark G. Sobell

• Linux in a Nutshell, by Ellen Siever, Aaron Weber, Stephen Figgins, Robert Love

1.4 本文件架構 (Organization of this document)

本文件共分為下列幾部分：

第二章：AOAWS 系統概觀，包括網路架構及資料流程

第三章：如何從網頁監控系統

第四章：問題診斷及解決

第五章：疑難排解指南

This document is divided into the following sections:

Section 2: A system overview showing the networking and data flow.

Section 3: How to monitor the system from the web.

Section 4: Diagnosing and solving problems.

Section 5: Troubleshooting guide.

AOAWS Operators Manual 3 Monitoring the system from the web

2 系統概觀 (System overview)

2.1 AOAWS網路架構 (The AOAWS network)

AOAWS 系統是一個橫跨中央氣象局資訊中心和民用航空局北部飛航服務園區臺北航空氣

象中心的之大型的分散式計算環境。圖 1 顯示 AOAWS 系統之資料來源、網路連結和系

統主機與中央氣象局間的關聯，圖中連結點之箭頭表示系統的資料流方向。

The AOAWS is a large-scale distributed computing environment that spans computer centers at the Central Weather Bureau (CWB) and the CAA’s ANWS North ATS Park facility that holds the hosts the TAMC. Figure 1 shows the data sources, network connections and hosts related to the CWB. The arrowheads on the connectors indicate the direction the data flows in the system.

Figure 1 CWB-TAMC network diagram


圖 2 顯示在臺北航空氣象中心端 AOAWS 系統之資料來源、網路連結和系統主機關係圖。

更多關於資料處理和系統主機之詳細資訊可參考監視系統章節之說明。

Figure 2 shows data sources, network connections and hosts at the TAMC. More details about the processing and hosts can be found in the section on system monitoring.

Figure 2 TAMC network diagram

2.2 系統運作 (Running the system)

AOAWS 系統在每臺主機上均可獨立作業及管理。


要啟動以及中止系統時，系統作業人員可以分別登入每部主機，然後在各主機上執行啟動

及結束程式。

The AOAWS is managed separately on each host.

To start or stop the system, log on to each host individually. Then run the start and stop scripts locally on that host.

2.3 啟動系統 (Starting the system)

在一部主機上啟動系統時：

以 aoaws 帳號登入。

執行 start_all 指令。

在主機上執行以上的步驟，會啟動並執行所有 AOAWS 相關程序。

To start the system on a host:

Log in as: aoaws

Run the command: start_all

This will start all of the processes on that host.

start_all 指令會執行下列各程式：

start_procmap: 啟動 procmap。AOAWS 系統的所有相關程序均會定時向 procmap 註冊，讓系統知道它在執行中。

procmap_list_start:啟動所有列示在 AOAWS 程序表中的 AOAWS 相關程序。系統

作業人員可查看~/projDir/control/proc_list 檔案，以確定 AOAWS 系統有哪些程序必須

執行。

start_auto_restart:啟動 auto_restart 程式。本程式每分鐘定時查看 procmap，用來

確定所有 AOAWS 程序均在執行中，若有未執行之程序，則重新啟動該程序。

start_cron:載入 cron table。cron 為系統程式，會自動於一定時間執行事先設定之

命令。在最基本的設定下，cron table 內含 procmap 和 auto_restart，以確保這兩支

程式能一直在執行中。根據主機的不同型態，cron table 也可能會包含其他指令。

系統作業人員可執行 ‘crontab –l’ 指令來檢查主機目前的 cron table 內容。

The start_all script performs the following:

start_procmap: starts procmap. All of the processes register with procmap to notify the system that they are running.


procmap_list_start: starts all of the processes in the process list. You can check to see which processes should be running by viewing the file:

~/projDir/control/proc_list

start_auto_restart: starts the auto_restart script. This checks with procmap every minute to make sure that all of the processes are running. Any processes which are not running are restarted.

start_cron: installs the cron table. cron is a special program which runs specified commands on a time schedule. As a minimum, the cron table will contain entries to make sure that procmap and auto_restart stay running. It checks on these every minute. Depending on the host type, the cron table will contain other commands as well. You can check on the current cron table by running the command ‘crontab –l’.

2.4 檢查系統是否已啟動，且在正確運作中 (Checking that the system has started and is running correctly)

系統啟動後，系統作業人員須檢查系統運作是否一切正常，檢查方法為輸入下列指令：

pcheck

螢幕上會出現下列訊息：

0 processes down

如果有任何 AOAWS 程序沒有啟動，系統會列出報告。例如：假設 tamc-data1 已經啟動

，但其上的 Janitor 程序啟動失敗。若系統作業人員執行 pcheck 這個指令後，將會出現下

列訊息：

Process missing: Janitor primary

當上述的情形發生時，系統作業人員需判定程序沒有啟動的原因。第一個解決方法為：試

著重新啟動電腦。如果這個方法失敗，則可檢查程式記錄檔中關於這個問題的詳細訊息。

程式記錄檔的位置在：

~/projDir/logs/errors/today 目錄下

注意: ‘~’ 符號表示指家目錄，也就是 /home/aoaws 這個目錄

注意: ~/projDir/logs 也就是/d1/aoaws/data/logs

“errors” 是個會讓人誤解的目錄名稱，其實這記錄檔中有正常的及錯誤的記錄檔案。在目錄下有一檔名為 processname﹒instance﹒log 檔案，此處的 processname 為程式名稱，instance 為程序組執行代號。上述範例的記錄檔名稱應為'Janitor.primary.log'。系統作業人

員可利用 less 這個指令查看檔案內容最後一頁。若檔案裡有'Command not found'等字樣，

則表示系統並未安裝完全，系統作業人員必須重新安裝整個系統。

系統作業人員須輸入下列指令來檢查 AOAWS 系統當時的運作程序：

ppm


注意: ppm 也就是:

procmap_list_check –proc_list $PROJ_DIR/control/proc_list

系統作業人員須輸入下列指令來檢查 AOAWS 系統當時的資料集：

注意: pdm 也就是: PrintDataMap –all –relt -lreg

假如資料集指出不是最新版本，請檢查資料分布紀錄檔案，檔案位於以下目錄：

~/projDir/logs/errors/today

檔案包括 DsFileDist.log 及 DsSpdbServer.log。上游傳輸檔案的錯誤訊息可以指出接收端電

腦上的問題。

After starting the system, you need to check that it is running correctly.

Type the command:

pcheck

You should get the following message:

0 processes down

If any of the processes did not start, this will be reported. For example, suppose that you started the tamc-data1 host, and the Janitor process failed to start. When you run “pcheck”, you would see the following:

Process missing: Janitor primary

If something like this happens, you will need to determine why the process did not start. The first remedy is to try rebooting the host. If that fails, you will need to check the program log files for more information on the problem.

The program log files are found in:


Note: ‘~’ refers to the home directory, /home/aoaws.

Note: ~/projDir/logs is a symbolic link to /d1/aoaws/data/logs.

The path name “errors” is misleading: these log files contain normal log output as well as any error log output. You will see a file named processname.instance.log, where processname is the name of the program and instance is the instance of the program. In the above example, the file would be named 'Janitor.primary.log'. View this file using the less command. If the log indicates 'Command not found' the installation is incomplete and the system on that host should be reinstalled.

To check view the current AOAWS processes, you may issue:

ppm

Note: ppm is an alias for:


procmap_list_check –proc_list $PROJ_DIR/control/proc_list

To check view the current AOAWS datasets, you may issue:

pdm

Note: pdm is an alias for:

PrintDataMap –all –relt -lreg

If there is an indication that datasets are not up to date, check the data distribution log files. They are located in:


Look for errors in DsFileDist.log and DsSpdbServer.log. An upstream error transferring a file can indicate a problem on the receiving computer.

2.5 停止系統 (Stopping the system)

若要中止一部主機上的系統：

以 aoaws 帳號登入。

執行 stop_all 指令。

執行以上的步驟將會使該主機中止執行所有 AOAWS 程序。

To stop the system on a host:

Log in as: aoaws.

Run the command: stop_all.

This will stop all of the processes on that host.

stop_all 指令會執行下列幾個程式：

kill_cron: 移除 cron table。

kill_auto_restart: 停止 auto_restart 程式。

killall –q DsServerMgr: 停止管理伺服器以阻止其重新開始執行。

killall –q DsFcopyServer: 停止複製伺服器以阻止其繼續接受資料。

killall –q DsSpdbServer: 停止 SPDB 伺服器

killall_aoaws: 停止所有的 AOAWS ~/projDir/bin 程序。

kill_SysView: 停止 SysView

remove_ipcs: 移除 Linux 的共用記憶體部分及互斥信號。


ipcrm_linux: 移除 Linux 的共用記憶體部分，互斥信號及 ipc 訊息佇列。

pkill java: 停止所有必要的 AOAWS java 程序。

The stop_all script runs the following:

kill_cron: removes the cron table

kill_auto_restart: kills the auto_restart script

killall –q DsServerMgr: kills the server manager so it does not restart services

killall –q DsFcopyServer kills the file copy server so new data is not accepted

killall –q DsSpdbServer: kills the SPDB server

killall_aoaws: kills all processes running out of ~/projDir/bin

kill_SysView: stops SysView

remove_ipcs: removes Linux interprocess memory segments and semaphores

ipcrm_linux: removes Linux interprocess memory segments, semaphores, and ipc message queues.

pkill java: kills all AOAWS java processes.

2.6 檢查執行中的 AOAWS 程序 (Checking the running processes)

print_procmap 命令是用來檢查主機上目前有哪些 AOAWS 程序在執行中，系統作業人員

可用 ppm (簡稱) 來得到相同的效果。

圖 3 顯示 tamc-data1 執行此 ppm 命令後的的輸出結果的範例。Uptime 欄顯示出 procmap到目前為止已經執行的時間。下面為圖中各欄的詳細說明：

• Name: 程序名稱。

• Instance: 程序組執行代號，同程序組的程序會有特定的代號。

• Host: 主機名稱。

• User: 執行本程序的使用者帳號。

• PID: 程序 id。

• Heartbeat: 上一次至最近一次的註冊時間。

• Uptime: 程序已經執行的時間長度。

• Status: 程序的最新狀態訊息。

在正常狀態下執行的各個程序會定期在每個註冊時間 (heartbeat interval) 向 procmap 註冊

。在一般情況下，heartbeat interval 為一分鐘。若某程序在兩分鐘內沒有進行註冊動作，


auto_restart 程式會重新執行該程序。系統作業人員可執行下列命令來查看雙倍 heartbeat interval (maxint) 值：

ppm –maxint

系統作業人員也可執行 print_procmap 指令來檢查遠端主機上執行的程序狀況。以下的

指令可用來查看遠端主機 tamc-webcontent 上程序是否運作正常。

ppm -host tamc-webcontent

The print_procmap program is used to check the processes, which are running on a host. There is a short-cut alias to this program, called ppm.

As an example, Figure 3, below, shows the output from running ppm on the tamc-data1 host.

The Uptime line indicates how long procmap itself has been running.

The columns in the table show the following for each process:

• Name: the process name.

• Instance: the process instance, which is a unique label attached to each process.

• Host: the hostname.

• User: the user running the process.

• PID: the process id.

• Heartbeat: the time since the latest heartbeat.

• Uptime: the length of time the process has been running.

• Status: the latest status message from the process.

Processes which are running properly will register with procmap regularly, at the ‘heartbeat interval’. Normally the heartbeat interval is one minute. If a process does not register within two minutes, the process will be restarted by the auto_restart script. The value of twice the heartbeat interval (maxint) may be printed out by running the following command:

ppm –maxint

You can use print_procmap to check the processes running on a remote host. For example, the following command will check the processes on the tamc-webcontent host:

ppm -host tamc-webcontent


Figure 3 Text output from 'ppm' and 'pdm' commands


2.7 檢查資料集 (Checking the data sets)

PrintDataMap 指令是用來檢查系統內 AOAWS 資料集狀態是否正常，系統作業人員可用

pdm 來得到相同的效果。

圖 3 也顯示 tamc-data1 執行此 pdm 命令後的的輸出結果。

以下分別說明執行 pdm 後各欄位代表之意義：

• DataType: 資料集類型，可為 ‘mdv’， ‘spdb’ ，及 ‘raw’任一種。

• Dir: 資料集目錄之相對主資料目錄，為/d1/aoaws/data。

• Hostname: 主機名稱。

• Latest: 資料最新抵達時間。

• ForecastLead: 預報前準備時間 (只有 WRF 模式資料有)。

• Last reg: 資料最新註冊時間。

• Start date: 資料開始存入硬碟之日期時間。

• End date: 資料結束存入硬碟之日期時間。

• nFiles: 資料存於硬碟裡之所有檔案數。

• nBytes: 資料存於硬碟裡所佔的空間。

系統作業人員可由 nFiles 及 nBytes 這兩行總數來得到硬碟資料量佔硬碟空間之多寡。

系統作業人員也可以利用 pdm 來檢查遠端主機的資料。例如：用下列指令來檢查遠端主

機 tamc-data1 的資料集狀態，

pdm -host tamc-data1

The PrintDataMap program is used to check the data sets on a given host. There is a short-cut alias to this program called pdm.

As an example, Figure 3 also shows the output from running pdm on the tamc-data1 host.

The following information is listed for each data set:

• DataType: the data set type, ‘mdv’, ‘spdb’ or ‘raw’.

• Dir: the data set directory relative to the top level data directory: /d1/aoaws/data.

• Hostname: the name of the host on which the data set resides.

• Latest: the time of the latest data in the set.

• ForecastLead: the forecast lead time (only applicable to model data).

• Last reg: the last time at which the data set registered with DataMapper.

• Start date: the start date for the data on the disk.


• End date: the end date for the data on the disk.

• nFiles: the total number of files on the disk.

• nBytes: the total number of bytes on the disk.

The nFiles and nBytes columns are summed, to provide total numbers for all of the data sets on the disk.

You can use pdm to check the data sets on a remote host. For example, the following command will check the data sets on the tamc-data1 host:

pdm -host tamc-data1

2.8 備份資料 (Archiving the data)

本系統使用一部硬碟，有能力儲存一百天份的資料以供備份之用。使用下列主機來備份從

系統傳來的重要資料：

• tamc-archive1

• tamc-archive2

The system uses a hard drive capable of storing a hundred days of files to archive data. The following hosts are used for archiving important data from the system:

• tamc-archive1

• tamc-archive2

本系統備份下列二個主要資料集：

• MDS data (來自 MDS)

• WEB data (來自 wmds)

There are 2 main data sets which are archived:

• MDS data (from MDS display hosts)

• WEB data (from wmds hosts)

資料以壓縮檔案格式存放在 /d1/aoaws/data/historic_archive 路徑下。可調校 Janitor 參數

檔來刪除任何一百天以前的舊檔案。

備份工作是由 cron 來執行的，其設定如下：

05 00 * * * csh -c "run_archive_mds_data >& /dev/null"


25 00 * * * csh -c "run_archive_web_data >& /dev/null"

系統會自動執行這些程序。

The data is stored in compressed tar files under /d1/aoaws/data/historic_archive. A Janitor parameter file is configured to delete any files that are more than one hundred days old.

The scripts to run the archive jobs are run from cron , as follows:

05 00 * * * csh -c "run_archive_mds_data >& /dev/null"

25 00 * * * csh -c "run_archive_web_data >& /dev/null"

These scripts are run automatically.

2.9 還原MDS資料 (Playback of the MDS data)

將備份之 MDS 資料還原至 archive 主機中供使用者檢視備份的 MDS 資料，操作步驟如下：

1. 點選螢幕上功能選單之“Restore from Archive” ( )按鈕執行備份存檔。請參

照 2.11 所列的 BackupRestoreUtility.py 程序。

2. 點選螢幕上功能選單之 Playback Start 按鈕（）開始使用 JMDS 檢視備份資

料。 3. 點選 JMDS 螢幕上功能選單之“Configure”，點選“Time and Animation”(參照圖 4)，

然後會跳出一視窗(參照圖 5)，預設檢視備份資料之結束時間為現在。 4. 修改結束時間，然後點選“Apply”及“OK”，即可檢視備份資料。詳細資訊請見

JMDS 使用手冊。

5. 點選螢幕上功能選單之 Playback Stop 按鈕（），可停止使用 JMDS 檢視

備份資料

To restore the backup MDS data, for user reviewing the backup MDS data. The steps are as below:

1. Click the “Restore from Archive” ( ) button on the function menu of the screen to start the Backup and Restore Utility. See section 2.11 for directions on using BackupRestoreUtility.py


2. Click the “Playback Start” ( ) button on the function menu of the screen to start the JMDS to review the backup data.

3. Select the “Configure” item from the JMDS menu bar. Under the “Configure” menu item, select “Time and Animation.” See Figure 4 for an example. A new window will appear as shown in Figure 5. The default end time of playback is now.

Figure 4 Time and animation selection in the JMDS

4. Modify the “End time:” field in the window to the backup date Then click on “Apply” and “OK.” Data restored from the historic archive will be available for viewing. For more detailed description of configuring time and animation setting, see the JMDS manual.


Figure 5 JMDS time and animation window

5. Click the “Playback Stop” ( ) button on the function menu of the screen to stop JMDS.

2.10 還原WEB資料 (Playback of the WEB data)

將備份之 WEB 資料還原至 archive 主機中供使用者檢視備份的 WEB 資料，操作步驟如下：

1. 點選螢幕上功能選單之“Restore from Archive” 按鈕( )執行備份存檔。請參

照 2.11 所列的 BackupRestoreUtility.py 程序。 2. 還原的 WEB 資料將存放於 /d1/aoaws/data/playback/www_content/archive/ 之內

To restore the backup WEB data, for user reviewing the backup WEB data. The steps are as below:

1. Click the “Restore from Archive” ( ) button on the function menu of the screen to start the Backup and Restore Utility. See section 2.11 for directions on using BackupRestoreUtility.py.

2. The backup date is stored in the folder - “/d1/aoaws/data/playback/www_content/archive/.”


2.11 硬碟至ＤＶＤ之備份與錄像重播 (HD Archive DVD Backup and Playback Restore)

BackupRestoreUtility.py 的 Python 程序提供下列的功能：

從硬碟備份中產生 MDS 與 WEB 資料的 DVD 備份。

從硬碟備份中還原 MDS 與 WEB 資料供重播 (playback)使用。還原 DVD 的 MDS 與 WEB 資料供重播使用。

此功能透過一個圖形使用者介面來控制，如圖 6：

The Python script BackupRestoreUtility.py provides the following functionality:

• Create DVD copies of MDS and WEB data from the HD archive.

• Restore MDS and WEB data from the HD archive for playback.

• Restore MDS and WEB data on DVD for playback. The utility is controlled through a GUI that is shown in Figure 6.

Figure 6 Backup and restore utility GUI

「open」與「close」按鈕分別代表在備份主機上開啟與關閉多重區段燒錄功能。從「

Devices」下拉選單可以選擇光碟機。「Write DVD」按鈕會執行將檔案燒錄至 DVD 裝置

並且自動比對原始資料與光碟資料。「Playback Restore」按鈕的功能為複製檔案至還原位

置。在要求重播檔案之前 playback 區沒有任何檔案會被刪除。「Playback Purge」按鈕可

以刪除在 playback 區裏的所有檔案。關閉視窗的功能可以從「Exit」按鈕及「File」功能

選單下的「Quit」達成。「Archive Dates」區域中文字欄位可輸入硬碟備份檔案的起始與

結束日期。「Devices」區域包含一個ＤＶＤ裝置的下拉式選單。「Data Sets」區域包含

Archive 主機中選擇檔案類型的單選按鈕，分別是 MDS 檔案，Web 檔案，或者二者都有

。「Playback Source」單選按鈕允許使用者選擇欲還原的資料，可來自硬碟備份或是

DVD。


The “open” and “close” buttons open and close the DVD drive trays on the archive hosts. The buttons on the DVD drives can still be used to control the tray. The DVD drive is chosen by the pull-down menu labeled “Devices.” The “Write DVD” button executes writing files to the DVD device and checking that files were successfully copied. The “Playback Restore” button handles copying of files to the playback location. There is no deletion of files in the playback area prior to requesting playback files. The “Playback Purge” button deletes all files in the playback location. The “Exit” buttons terminates the script. The utility can also be killed by selecting “Quit” from the “File” menu-bar item. The “Archive Dates” region contains text fields for entering start and end dates of files in the HD archive. The “Devices” region holds a pull-down menu that contains a list of DVD drives. The “Data Sets” area contains a radio button selection for the types of files to select from the archive which are MDS files, Web files, or both types of files. The “Playback Source” radio button selection allows users to pick the source of data for playback restoration, which is either the HD archive or a DVD disk.

當建立一個 DVD 複製或從硬碟備份還原檔案時，必須設定「Start date」與「End date」兩

個欄位的值。啟動本程式時，起始與結束日期欄位會以目前硬碟備份日期中最新與最舊日

期為初始值。透過「Data Sets」區域裡的單選按鈕，使用者可以選擇資料集的類型複製至 DVD 或直接 playback。如果使用者選擇之日期區間累計檔案大於 DVD 可容納空間（約

4GB），檔案將會被依序複製到 DVD 中，直到超出 DVD 可容納空間，而多餘的檔案將

不會被複製。

When creating a DVD copy or restoring files from the HD archive, the “Start date” and “End date” text fields must be set. At start up the start and end dates are initialized with the newest and oldest dates of files in the HD archive. The user can select the type of data sets to copy to DVD or restore for playback with the radio-buttons labeled “Data Sets.” If a user selects a date interval that encompasses a set of files whose cumulative size is greater than the capacity of a DVD (approximately 4 GB), files will be copied in order, until the capacity of the DVD will be exceeded. The remaining files will not be copied.

當選擇「Playback Source」單選按鈕來還原 MDS 與 WEB 資料時，如果 playback source為 DVD 時，必須選擇 DVD 裝置並且放入光碟片。DVD 上的所有檔案將會被複製到

playback 區域。如果 playback source 是硬碟備份，則必須選擇開始與結束日期以及資料集

的類型。

When restoring MDS and WEB data for playback the source is selected from the “Playback Source” radio buttons. If the playback source is a DVD, the DVD device must be selected and the DVD inserted. All files on the DVD will be copied to the playback area. If the playback source is the HD archive, the start and end dates must be selected, along with the type of data sets.


3 從網頁上監視系統 (Monitoring the system from the web) AOAWS提供六個項目來協助系統作業人員監看系統狀態，皆透過網路來完成。其主監視系

統網頁網址為：

http://aoaws.caa.gov.tw/htdocs/projects/aoaws/internal/

圖 7為網頁監視系統的快照圖。系統作業人員想要進入本網頁，必須輸入系統管理者的帳

號密碼。

There are eleven tools for monitoring the system, all of which are available via the web. The URL for the main system monitoring page is:

http://aoaws.caa.gov.tw/htdocs/projects/aoaws/internal/

Figure 7 shows a snapshot of the system monitoring web page.

If the operator wants to log in this page, she/he has to enter the user name and the password of the administrator.

Figure 7 Snapshot of System Monitor Page

本網頁包括下列各網頁的連結：


Overall System Status

- Opsview: AOAWS 系統硬體監視網頁。

- Cacti: AOAWS 系統網路流量監視網頁。

- SysView: AOAWS 程序及資料監視網頁。

- Uptimes: 主機開機時間狀態表。

- Processes: 程序統計表。

- Data: 資料集統計表。

- WMDS: WMDS 資料統計表。

- Archive: 資料備份狀態表。

- AISS FTP: 資料傳送至 AISS FTP s 伺服器狀態。

- WRF 檔案可用性: WRF 輸出資料及 RIP 影像檔案之可用性統計表。

- 模式狀態摘要表: HPC WRF 模式執行狀態摘要

每個連結都提供不同的系統狀態資料，分別於本章各小節中詳細說明。

On the page, you will find links to the following pages:

Overall System Status - Opsview: AOAWS system hardware monitor

- Cacti: AOAWS network traffic monitor

- SysView: AOAWS process and data monitor

- Uptimes: Machine uptime status.

- Processes: AOAWS process statistics

- Data: AOAWS data transfer statistics

- WMDS: WMDS data statistics

- Archive: Data archive status - AISS FTP: File transfer to AISS FTP server status - WRF file availability: WRF output and RIP image file availability

- Model Status Summary: Summary of the HPC WRF run status

Each of these links provides a separate monitoring function. These functions are detailed in the sections which follow.


3.1 Opsview - 硬體及網路監視 (Opsview - hardware monitor)

Opsview 網頁主要是用來監看系統硬體設備狀態。換言之，Opsview 主要用來查看系統的

一般作業狀態並提供趨勢圖以供分析。

The Opsview utility monitors the hardware components of the system. In other words, Opsview monitors the general health of the system infrastructure and provides trend graphs for analysis.

圖 Figure 8 為 Opsview 網頁登入畫面。操作者必須提供帳號及密碼以登入系統。

Figure 8 shows the Opsview login web page. The operator is required to supply an account and password to log in.

Figure 8 Opsview login page


Opsview 展示以主機群組分類為基礎的上層系統狀態(如圖 Figure 9)。每一個群組的主機

及服務狀態都被聚集在一起，更多的信息可以在下一層的特定分類摘要取得，如主機摘要、

檢查次數以及他們的狀態則都列在最後一列。

Opsview presents a top-level system status based on host group summary as shown in Figure 9. Host and service status is aggregated for each group. More information can be found by drilling down into a particular group summary. A summary of hosts, number of checks and their states are listed in the last row.

Figure 9 Opsview host group summary web page

click for host group


圖 10 是 AOAWS 主機之群組摘要圖，圖中顯示每個群組主機之狀態和未被處理前的警示

情形，點擊最左邊一行的主機名稱，可得到更多的資訊。

A group summary for the ‘AOAWS Hosts’ is shown in Figure 10. In this view status and unhandled conditions are presented for each host the group. Status and warnings for each host are shown. Again more information can be revealed about each host by clicking on a name in the leftmost column.

Figure 10 Opsview host web page

click for host


tamc-data1 主機之系統監視頁面如圖 Figure 11 所示。每一台電腦上許多的資源都被監視

著，點選圖中用紅圈標示的符號，可以顯示該項目的變化趨勢圖。網頁上有相關監視服務

項目的詳細說明。

The monitoring page for tamc-data1 is shown in Figure 11. Many resources are monitored on each computer. By clicking on the symbol highlighted by the red circle, a graph of the trend is presented. There are several services that are monitored which are clearly described on the page itself.


Figure 11 Opsview monitoring page for tamc-data1

圖 Figure 12 是 tamc-data1 主機之‘I/O 狀態’圖，此圖可以透過圖中標示出來的功能鍵

進行及時調整。

Figure 12 shows the ‘I/O Status’ graphs for tamc-data1. The graphs can be modified in real-time. Various changes are highlighted in the figure.

click for trend graph


Figure 12 Opsview I/O Status graph for tamc-data1

scroll right in time change time scale change axis options

scroll left in time


3.2 系統與網路流量監視 (System and network flow monitoring)

網路流量監視網頁係使用 Cacti – the complete RRD Tool-based graphing solution 系統網路

流量偵測軟體。本網頁只可在 CAA 內部作業存取。

The network monitoring page is generated using Cacti – the complete RRDTool-based graphing solution. The web page is only accessible from within the CAA.

Cacti 網頁主要用來監控系統與網路元件之流量，它能儲存所有主機的狀態資訊並將其存

放於 MySQL 資料庫，並製作主機的流量趨勢圖以供管理員分析。

Cacti monitors the flow of system and the traffic of network components. It captures all of a host’s status information and populates a MySQL database, which is used to create host flow trend graphs for analysis by administrators.

操作員必須提供使用者帳號及密碼來登入及使用 Caccti 系統，圖 Figure 13 為登入介面。

To use Cacti, an operator must provide a user name and password to login. Figure 13 shows the login web page.

Figure 13 Cacti login web page


圖 14 為 cacti 網頁。頁面左側顯示所有被監控主機的群組列表。使用者可點選’+’符號展

開樹狀選單來選取監控元件。頁面右側為時間範圍與主機趨勢圖顯示區。右側上方區域為

時間範圍選擇列表，使用者可藉由點選下拉式選單或輸入日期來選擇不同的時間範圍。右

側下方區域為主機趨勢圖顯示區，在此區域，系統將會顯示指定主機所有的趨勢圖，使用

者可藉由點選任一張趨勢圖切換至單一趨勢圖畫面。

Figure 14 shows the cacti web page. The left part displays the group list for all of monitored hosts. A user is able to click ‘+’ to open the tree menu and select the component. The right part shows the time range and the host trend graph area. The upper right area is the time range selection list. A user can select different time ranges by clicking each pull down menu or input date characters. The lower right area displays the host trend graph, in this area; the display will show all of the trend graphs for specific host. A single trend graph can be switched by clicking one of graphs in this area.

Figure 14 Cacti host page


3.3 SysView – process 及資料監視 (SysView - the process and data monitor)

系統中的每部主機都執行兩個管理程式，procmap 和 DataMapper。絕大部分的 AOAWS系統程序都會向 procmap 註冊，由 procmap 持續地追蹤程序是否正常運作或有狀況出現

。auto_restart 則會每分鐘檢查 procmap，並會重新啟動沒有正確執行的程序。SysView則從 procmap 得到 AOAWS 程序執行狀態，以供系統作業人員進行系統監看。

Each host runs two management programs, procmap and DataMapper. Most programs running on the system register with the procmap, which keeps track of which programs are running properly and which are having problems. The auto restart script auto_restart checks with procmap every minute, and restarts any programs which are not running properly. The system monitor, SysView, contacts procmap for process information.

每次將資料寫進硬碟的程序同時也會向 DataMapper 註冊。DataMapper 會儲存主機上所

有重要資料集狀態。SysView 也會透過 DataMapper 來得到資料集的狀態。SysView 於網

頁上以圖形化界面監控 AOAWS 程序與資料流之狀態(圖 15 是 AOAWS SysView 最外層

的畫面)。

Programs which write data to the disk also register with DataMapper each time data is written. DataMapper stores the status of all of the important data sets on the host. SysView contacts DataMapper for data set information. SysView graphically monitors the status of both the programs and the data flow in the AOAWS through a web-based interface. Figure 15 shows the top-level view of AOAWS in SysView.


Figure 15 Top-level SysView diagram for AOAWS

系統上每部活動的主機都用有顏色的子資料流程圖示。綠色表示該部主機上的程序執行及

資料接收狀況均正常，黃色表示該部主機上的程序執行或資料接收狀況有延遲，紅色表示

該部主機上的程序執行或資料接收出現不正常情況。

Each active host in the system is shown as a colored 'sub-diagram' icon. A green icon indicates no problems with that diagram, a yellow icon indicates a minor problem, and a red icon indicates a major problem.

subdiagram


Figure 16 SysView diagram showing processes and datasets

如圖 16，點選子資料流程圖示，會顯示子資料流程圖。在下一層的資料流程圖中會顯示

更低層的子資料流程圖或程序及資料集之圖示。方形表示資料集，橢圓形表示程序。藍色

橢圓形圖示為資料流程圖上的圖示說明，並不是主要資料流程部分。

Clicking on the sub-diagram takes you into that sub-diagram as shown in Figure 16. At the lower level you may see further sub-diagrams, or you may see process and data set icons. Sharp rectangles represent data sets, while the rounded rectangles represent processes (programs). Some diagrams include blue boxes - these are not 'active' parts of the diagram, they are there for information only.

dataset

process


如果在任何一個圖示上出現不正常狀況，例如：可能為橘色或紅色狀態，請點選此圖示，

並且可以看到此圖示的詳細資料狀態，我們可以藉由這些資料狀態中 'Last registration time' 得知程式最後向 procmap 註冊的時間，或資料最後向 DataMapper 註冊的時間。在每個

資料訊息中'Latest entry time’ 表示最近一筆資料接收時間。

在資料狀態頁中包括 ‘Troubleshooting’ 疑難排解連結，點選此連結會出現解決此問題狀

況方式的網頁。

If an icon indicates a problem (if it is yellow or red), click on it to view the status page for that icon. There is information on these status pages, which can be helpful. Find the entry labeled 'Last registration time'. That indicates the time at which the program last contacted procmap, or the data set was registered with DataMapper. For a data set you can also find the entry 'Latest entry time’. This is the time of the latest data in the data set.

The status pages may contain a link called ‘Troubleshooting’. If this is true, you can click on the link to move to a page containing information on the possible nature of the problem and advice on how to proceed.

點選程序圖示會帶出一個程序細節網頁。此網頁解說程序狀態細節。程序狀態說明頁的文

字說明相當簡單易懂，圖 Figure 17 是一個系統處理程序狀態網頁的範例。下面為說明頁

的詳細解說：

Clicking on a process icon will take you to a page, which shows the details of the process. Much of the text in the status page is self-explanatory. Figure 17 shows an example of a process status web page. The following provides further explanation on the less-obvious fields:

程序狀態可能有下列幾種狀況：

• PROCESS_STATUS_OKAY: 是指此程序運作及註冊狀況正常。

PROCESS_STATUS_OKAY: 程序已經執行，且仍在執行中。也曾在兩分鐘前向

procmap 註冊。

PROCESS_STATUS_LATE: 程序剛執行，仍列在 procmap 表單中，但是已有兩分鐘未

向 procmap 註冊。

PROCESS_STATUS_DOWN: 程序沒有向 procmap 註冊。

• PID: process ID。這個 ID 與使用 ‘ps’ 或 ‘ppm’ 命令所顯示的是相同的。

• Start time: 程序開始執行的時間。

• Last registration time: 程序最後一次向 procmap 註冊的時間。

• Status String: 指出程序最後註冊時的狀態。


• Max Register Interval: 指出應該註冊的時間間隔。如果最後的註冊時間是在最大註冊

時間間隔 (Max Register Interval)之內，圖示會顯示綠色。如果超過此時間間隔，則圖

示會顯示紅色。一直顯示紅色圖示表示程序無法被執行。

• Num registrations: 程序向 procmap 註冊的次數。

The process status will be one of the following:

• PROCESS_STATUS_OKAY: the process is running and registering normally. PROCESS_STATUS_OKAY: the process is up and running and has registered with procmap within the past 2 minutes.

PROCESS_STATUS_LATE: the process was running recently, and it still listed in the procmap list, but has not registered within the past 2 minutes.

PROCESS_STATUS_DOWN: the process is not registered with procmap.

• PID: process ID. This is the same ID as is displayed by using the ‘ps’ or ‘ppm’ commands.

• Start time: the time at which the process started.

• Last registration time: This is the last time at which the process registered with procmap.

• Status String: this indicates what the process was doing when it last registered.

• Max Register Interval: this specifies the time period within which the process should register. If the last registration time is within the max register interval, the process icon will be green. If it is after this time, it will be red. A consistently red icon indicates that a process is unable to start.

• Num registrations: the number of times the process has registered with procmap.


Figure 17 Example of Process Status web page

點選資料集圖示，會帶出一個資料集說明頁，圖 Figure 18 是一個資料狀態網頁的範例。

資料集說明頁的文字說明相當簡單易懂，下面為說明頁的詳細解說：

• Data Set Status: 資料集狀態。

資料集可能有下列幾種狀況：

DATASET_STATUS_OKAY: 正常。

DATASET_STATUS_DOWN: 資料集中沒有資料。

DATASET_STATUS_LATE_DATA: 資料接收延遲。

DATASET_STATUS_VERY_LATE_DATA: 資料接收嚴重延遲。

• Data Type: 資料種類分別為 ‘raw’ (輸入的資料)， ‘mdv’ (網格資料)，以及 ‘spdb’ (非網格資料) 或 ‘www’ (網頁資料)。

• Data dir: 資料集放置的目錄，為 /d1/aoaws/data。

• Late time: 自最近接收的一筆資料與其資料集圖示變成橘色之間隔時間，以秒為單位

。


• Very late time: 自最近接收的一筆資料與其資料集圖示變成紅色之間隔時間，以秒為

單位。這表示資料集接收嚴重延遲。

• Priority: 這是資料集接收與副結構圖示顯示狀況之相互影響的控制方式。如果是

PRIORITY_HIGH 表示當資料集嚴重延遲，其子資料結構圖示會顯示紅色，如果資料

集延遲則子資料結構圖示會顯示橘色。如果是 PRIORITY_MEDIUM，表示資料集延遲

或嚴重延遲，子資料流程圖示顯示橘色。如果是 PRIORITY_LOW，表示資料集狀態

對子資料流程圖示顏色沒有影響。

• Start date: 第一筆資料開始存入資料集的日期時間。

• End date: 資料存入資料集的結束日期時間。

• Last registration time: 資料集最後一次向 DataMapper 註冊時間。

• Latest data time: 資料最後抵達資料集的時間。

• Total number of files: 如果有資料，就會顯示這一行。

• Total number of bytes: 如果有資料，就會顯示這一行。

如果資料集接收出現不正常情況時，可以點選 ‘Troubleshooting’ 連結。使用疑難排解頁之

詳細說明問題解決方法，來將問題解決。

Clicking on a data set icon will take you to a page, which shows the detailed properties of the data set. Figure 18 shows an example of a dataset status web page.

Much of the text in the status page is self-explanatory. The following provides further explanation on the less-obvious fields:

• Data Set Status: the status of the data set.

This will be one of the following:

DATASET_STATUS_OKAY: normal

DATASET_STATUS_DOWN: no data in the data set

DATASET_STATUS_LATE_DATA: data is late in arriving

DATASET_STATUS_VERY_LATE_DATA: data is very late in arriving

• Data Type: this can be ‘raw’ (input data), ‘mdv’ (gridded), ‘spdb’ (non-gridded) or ‘www’ (web content).

• Data dir: the directory of this data set relative to /d1/aoaws/data.

• Late time: the time in seconds since the latest data after which the data set icon turns orange

• Very late time: the time in seconds since the latest data after which the data set icon turns red. This indicates a very late data set.


• Priority: This controls the way in which this data set affects the status of the sub-diagram. If PRIORITY_HIGH, a very late data set will set the sub-diagram red, and a late data set will set the sub-diagram orange. If PRIORITY_MEDIUM, both a late data set and a very late data set will turn the sub-diagram orange. If PRIORITY_LOW, the status of this data set will have no effect on the color of the sub-diagram.

• Start date: the date of the first data in the data set.

• End date: the date of the last data in the data set.

• Last registration time: the time at which the data set was last registered with DataMapper.

• Latest data time: the time of the latest data in the data set.

• Total number of files: if available.

• Total number of bytes: if available. If there is a problem with the data set, you can click on the ‘Troubleshooting’ link. This will take you to a page, which will give you detailed information on how to track down the problem.

Figure 18 Example of Dataset Status web page


3.4 開機時間 (Uptimes)

正常運作時間網頁顯示前一個小時/日主機開啟後及運作的百分比，圖 Figure 19 是一個網

頁介面的範例。表格的數值顯示出百分比。若您點選百分比，將會連結至所監控主機每分

鐘負載程度的網頁。

The uptimes page shows the percentage of the previous hour/day that the host has been up and operational. Figure 19 shows an example of the web page. The values in the table show the percentage. If you click on the percentage value, you will reach a page which shows the load on the host for each minute of the period being monitored.

Figure 19 Example of Uptimes web page.


3.5 AOAWS 程序可用度 (AOAWS Process Availability)

AOAWS 程序可用度以表格方式顯示在網頁上，該網址為

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/processes_stats.html

圖 Figure 20 顯示一個網頁介面的範例。

AOAWS Process Availability is shown as table format on the web, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/processes_stats.html.

An example of the web page is shown in Figure 20.

本表使用法：請點選紅色方格 (若可用度小於 99%)，即可查看運作不正常的程序。系統

作業人員可從程序重新執行表中，獲得有關程序及主機/資料損壞時間的更多說明。請注

意：不論程序是否正在處理資料，它都有可能被視為運作中。有關資料部份，請參考資料

集可用度表中的詳細說明。

To use this table: click on the red boxes (availability < 99%) and check which process(es) are being warned on. For more details on the process(es) and the impaired times for a host/date see the process restarts table. Note that a process may be considered "up" whether or not it is processing data. See the dataset availability table for details on the data.




Figure 20 Example of Process Statistics web page.

程序可用度資料是由 status_monitor.pl 程式依據表上日期檢查表上所列各主機的警告訊息

決定的，統計時間為表中列出的 UTC 日期 (凌晨到半夜)。

The processes table shows the process availability on each of the listed hosts. The availability is determined from warnings generated by status_monitor.pl, which checked each of the listed hosts on a regular basis over the listed day from midnight to midnight UTC.


本表列出 AOAWS 系統中各主機及 UTC 日期 (從凌晨到半夜) 的執行程序可靠度統計結

果。想要了解詳細的程序重新執行說明，只要點選表中任何一個可靠度數值連結即可。

This table shows the AOAWS process reliability on each AOAWS host over the listed day from midnight to midnight UTC. To see details on the process restarts, click on the percent reliability entry for the day and machine you are interested in.

本表使用法：請點選紅色方格 (若可靠度小於 99%)，即可檢查哪些程序有重新執行。如

果某個程序連續幾天都會重新執行，該程序可能有問題。若某部主機的資料顯示為

"Unavailable"，表示該部主機無法將重新執行的記錄檔案傳給網頁伺服器。這可能是因為

網路間傳輸的問題。請注意：不論程序是否正在處理資料，它都有可能被視為運作中。有

關資料部份，請參考資料集可靠度表中的詳細說明。

To use this table: click on the red boxes (reliability < 99%) and check which process(es) are restarting. If the same process is restarting for several days, there is likely a problem with that process. If a host/date is listed as "Unavailable" the host was unable to send the log with the restart details to the web server. This could indicate a data communications problem. Note that a process may be considered "up" whether or not it is processing data. See the dataset availability table for details on the data status.

3.6 資料 (Data)

資料可用度統計表及資料傳送表以表格方式顯示在網頁上，該網址為

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/data_stats.html。


Dataset availability table and Data Communication table are shown as table format on the web, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/data_stats.html.


http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/data_stats.html

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/data_stats.html


Figure 21 Example of Dataset Statistics web page.

3.6.1 資料可用度統計表 (Dataset availability table)

可用度資料是由 status_monitor.pl 程式依據表上的 UTC 日期 (凌晨至半夜) 檢查各主機的

警告訊息所決定的。


This table shows the dataset availability on each of the listed hosts. The availability is determined from warnings generated by status_monitor.pl which checked each of the listed hosts on a regular basis over the listed day from midnight to midnight UTC.

本表使用法：請點選紅色方格 (若可用度小於 99%)，即可查看運作不正常的資料集。資

料集可用度會受到資料傳送的影響。另外，資料集可用度亦會受到處理資料集程序影響。

To use this table: click on the red boxes (availability < 99%) and check which dataset(s) are being warned on. Dataset availability can be affected by data communications, see the tables below detailing the reliability of sending and receiving data. Dataset availability can also be affected by processes which write the datasets. See the process availability table for details.

3.6.2 資料傳送表 (Data Communication table)

本表為系統中傳送資料主機與接收資料主機，依表中列出的 UTC 日期 (從凌晨到半夜) 的資料傳送可靠度統計值。請注意：表中只列出執行資料傳送工作的主機。系統作業人員

可選取主機及日期上的可靠度數值連結，來查看更詳細的資料。資料傳送可靠度共分為兩

個表格，一個顯示傳送整體檔案的 DsFileDist 統計資料；另一個顯示傳送 SPDB 資料庫資

料的 DsSpdbServer 統計資料。

This table shows the data transfer reliability from the listed sending host to its receiving hosts over the listed day from midnight to midnight UTC. Note that only hosts which perform data transfer operations are included in the table. For details, click on the percent reliability for the machine and date you are interested in. There are two separate tables, one for DsFileDist, which distributes entire files, and one for DsSpdbServer, which distributes the SPDB data base data.

本表使用法：請點選紅色方格(若可靠度小於 99%)，即可查看傳送主機(表中左列主機名

稱)及接收主機(詳細說明頁中列示)是否有任何問題。查看此表格中傳送資料兩端的主機，若傳送表格中顯示為紅色，但是接收表格中顯示為綠色，問題可能發生在負責接收資料的

主機。如果顯示為"Unavailable"表示主機資料未將記錄傳送至網頁伺服器。請注意：即使

沒有資料傳送，資料傳送統計表中仍會顯示"up"。有關資料部份，請參考資料集可靠度中

的詳細說明。

請注意：在表格中有些資料為系統檔案，並不是資料流程主要部分。這些資料的傳送過程

並不會顯示在 SysView 資料流程圖上。

To use this table: click on the red boxes (reliability < 99%) and see which combination of sending host (on the left column of this table) and receiving host (listed in the detailed page) are having problems. Check the data communications receiving reliability table for the same pair of hosts. If the sending table is red, but the receiving table is green for the same pair of hosts, then


the problem likely is with the receiving host. If a host/date is listed as "Unavailable" the host was unable to send the log with the details to the web server. Note that data communications may be considered "up" even if no data is available to transfer. See the dataset availability table for details on the data.

Note that some of the data transfers shown here are for small system files which are not part of the main data flow. These transfers will not appear on the SysView data flow diagrams.

3.7 WMDS 圖檔可用度 (WMDS Image Availability)

此網頁顯示在 wmds 上圖檔之可用度，該網址為

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/wmds_files_stats.html。

圖 Figure 22 是一個 WMDS 圖檔可用性統計網頁介面的範例。

This page shows the availability of image files on the wmds servers, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/wmds_files_stats.html.

An example of the WMDS Image Files Availability Data web page is shown in Figure 22.

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/wmds_files_stats.html

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/wmds_files_stats.html


Figure 22 Example of WMDS Statistics web page.

圖中表格顯示 WMDS 網頁內容備援主機之影像檔案的比例，此統計資料是由網頁內容主

機之程序 webcontent_monitor.pl 產製，點選這些數字可產生一個網頁顯示檔案的損壞個數。

This table shows the completeness of image files created for the WMDS on the webcontent hosts that are stored on the archive hosts. The statistics are generated by the script webcontent_monitor.pl. Clicking on one of the values bring up a web page showing the breakdown of the file counts.


3.8 備份 (Archive)

備份狀態以表格方式顯示在網頁上，該網址為

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/archive_stats.html。


Archive status is shown as table format on the web, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/archive_stats.html.


Figure 23 Example of Archive Status web page.

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/archive_stats.html

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/archive_stats.html


如果 tamc-archive1 及 tamc-archive2，二部主機上資料備份狀態顯示結果不是 “SUCCESS”，表示該星期的備份工作失敗，需於隔天再次執行備份工作。

一般情況下，備份程式每天以 cron 自動執行 (可參考 2.8 節)

若需再次執行資料備份工作，請依照下列步驟：

• 以 aoaws 登入系統。

• 在 tamc-archive1 及 tamc-archive2 主機上，依據備份失敗的資料種類，執行

“archive_mds_data” 指令或 archive_web_data.pl 程序。

執行備份工作需要花上數分鐘時間。

等備份工作完成至少一個小時後才能到網頁上查看備份狀態，此時當天的備份資料結果會

在網頁上顯示出來。

If the status of the data archive processes on the tamc-archive1 and tamc-archive2 hosts archive entries do not indicate “SUCCESS’, the archive for that day failed. It is possible to rerun the archive again the following day. If the archive does fail, an investigation into the reason for the failure should be conducted. First, check to see if there is room on the disk for the archive. A fill disk is the most likely the reason. Second, review the log file produced by the archive script. A reason for the failure should in the file. And last, check for the existence of the tar file in the archive location. A tar file might exist, but it is smaller than the minimum size, which is 0.8 GB.

Normally the backup scripts are run automatically by cron every day. (See section 2.8).

If you need to rerun the data archive, proceed as follows:

• Log on as: aoaws

• On tamc-archive1 and tamc-archive2, run the command: archive_mds_data.pl or archive_web_data.pl, depending on which archive component failed.

The archive scripts take several minutes to run.

To check the status of the archive, check the archive status web page at least one hour after the archive is complete. The entry for the day on which you ran the archive should appear some time after completion.

3.9 資料傳送至 AISS FTP伺服器 (File transfer to AISS FTP Server)

AISS Ftp 檔案傳送狀態以表格顯示於網頁上，其連結網頁如下：

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/aissFtp_stats.html


AISS Ftp file transfer status is shown as table format on the web, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/aissFtp_stats.html




An example of the web is shown in Figure 24.

tamc-data1 和 tamc-data2 傳送資料之狀態會顯示在表格中。如果是成功('SUCCESS') 之狀態，表示傳送檔案數量超過預定的門檻值。如果是失敗(' FAILURE') 之狀態，表示需

要調查失敗原因。tamc-data1 是主要的資料傳送主機，因此 tamc-data2 不會傳送任何資料，

所以它的狀態是 FAILURE。當兩部主機都失敗的情況下才需要檢查問題。失敗的原因包

括下列可能性：

• AISS FTP 伺服器停止運作。

• tamc-data1 and tamc-data2 停止運作。

• 預期的資料未被傳送至 AOAWS。

The status of the file transfers processes on tamc-data1 and tamc-data2 are shown in the tables. If the status is 'SUCCESS,' then number of file transfers is above a set threshold. If the status is 'FAILURE,' then the cause of the failure should be investigated. tamc-data1 is the primary host for the file transfers, As such, tamc-data2 will not transfer any files, so its status will be ‘FAILURE.’ The condition for checking on a problem is that both computers fail. The source of the failure could be:

• the AISS FTP server is down

• the processes on tamc-data1 and tamc-data2 are failing

• the expected files are not coming into the AOAWS.

Figure 24 Example of the AISS Ftp Status web page.


使用者可試著手動登入 AISS FTP 主機，檢查伺服器是否運作正常。該伺服器之登入資訊

如下：

To find out if the AISS FTP server is up, try to log in to the server manually. The ftp server information is:

Server IP login password Note

1 10.10.72.102 atmftp1 fu4vu;4 Online (for ATMS System)

2 10.10.72.103 atmftp1 fu4vu;4 Backup/Research (for ATMS System and IMC research)

3 10.10.73.9 atmftp1 fu4vu;4 For FIS ftp Server

使用者可利用 SysView 來檢查在 AOAWS 系統中的處理程序及資料集狀態。為了進一步

調查，檢查資料處理程序及資料集可用度網頁如 AOAWS 程序統計訊息。

To check on processes and datasets on the AOAWS use SysView. To further investigate check the process and dataset availability web pages, such as the AOAWS process statistics.

3.10 WRF檔案之可用度 (WRF file Availability)

WRF 檔案之可用度狀態以表格顯示於網頁上，其連結網頁如下：

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/model_filelist_stats.html.


WRF file availability status is shown as table format on the web, the hyperlink is http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/model_filelist_stats.html.

An example of the web is shown in Figure 25.

此網頁顯示 AOAWS 使用的不同型式的 WRF 檔案。

This page shows the availability of several file types in the AOAWS system:

• WRF files

• WRF-ITFA files

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/model_filelist_stats.html

http://aoaws.caa.gov.tw/data/www_content/realtime_links/stats/model_filelist_stats.html


• RIP CGM files

• PNG image files

Figure 25 Example of the WRF Model Statistics web page.

參照 SysView 的圖示可顯示資料流如何從 model 主機傳送至 web 主機。

下列為基本步驟流程及在本表中這些步驟監控的結果：

• WRF 資料從 HPC 複製到 modelserver1/2。

• 在 modelserver1/2 上，由 WRF 資料產生亂流產品(ITFA)。


• WRF 資料傳送到 caasv1/2。

• RIP 在 caasv1/2 上執行以產生 CGM 檔案。

• 將 CGM 檔案轉成 PNG 圖形檔。

• 將多個網頁 PNG 圖形檔包在單一 tar 檔案中。

• 將 PNG tar 檔案透過 data1/2 傳送至 archive1/2、wmds1/2 和 wmdsi1/2。

• 在 archive1/2、wmds1/2 和 wmdsi1/2 上，PNG tar 檔案被拆解成各單一的 png 圖檔，

並放置適當的目錄下。

Refer to SysView for a graphical description of how the data flows from the modelservers to the web servers.

The following basic steps occur, and the results of these steps are monitored in this table:

• WRF data is copied from the HPC to modelserver1/2

• On modelserver1/2, the turbulence product (ITFA) is created from the WRF data

• WRF data is sent to caasv1/2

• RIP is run on caasv1/2, creating the CGM files.

• CGM files are converted into PNG image files.

• PNG files are collected into a single tar file of web images.

• The PNG tar files are sent to archive1/2 , wmds1/2 and wmdsi1/2, via data1/2

• On archive1/2, wmds1/2 and wmdsi1/2, the PNG tar files are unpacked into appropriate directories.

3.11 模式狀態摘要 (Model status summary)

此網頁顯示 WRF 在 HPC 上執行的狀態。詳細內容可參照其網頁，網址為

http://aoaws.caa.gov.tw/htdocs/projects/aoaws_modeldisplay/index.html。

This page shows the status of the current WRF model runs on the HPC. More details are available on the CWB web site, http://aoaws.caa.gov.tw/htdocs/projects/aoaws_modeldisplay/index.html.

http://aoaws.caa.gov.tw/htdocs/projects/aoaws_modeldisplay/index.html


AOAWS Operators Manual 51 Diagnosing and solving problems

4 問題診斷及解決 (Diagnosing and solving problems)

4.1 引言 (Introduction)

本節中主要介紹 AOAWS 系統上會發生的幾類問題，並提出解決問題的詳細說明。

問題包括下列幾大類：

• 網路問題。

• 資料接收問題。

• 電源問題。

• 作業系統問題。

• 電腦硬體問題。

• AOAWS 軟體問題。

•

This section introduces you to the various categories of problem that can occur in the AOAWS, and presents methods for dealing with them.

The problems fall into the following categories:

• Network problems.

• Data availability problems.

• Power problems.

• Operating system problems.

• Computer hardware problems.

4.2 網路問題 (Network problems)

AOAWS 系統是一套分散式架構系統 – 請參考第二章之圖 1。在臺北航空氣象中心

(TAMC) 內所有主機是透過快速穩定的區域網路(LAN)相連結。中心外的廣域網路(WAN)

的連結是透過光纖、微波及專線。

The AOAWS is a system with a distributed architecture – see Figure 1and Figure 2. The tasks are spread across the various hosts in the system. At the TAMC the hosts are connected via a high-speed local area switched network (LAN), which is very reliable, and tends to cause few problems. The wide-area network (WAN) connections to hosts outside the TAMC vary in type, including fiber-optic, microwave and leased line technology.


4.2.1 臺北航空氣象中心與網際網路主要連結 (Main link from TAMC to internet)

臺北航空氣象中心與網際網路主要透過北部飛航服務園區網路專線連結。

如果網路斷線，用戶將無法連結 AOAWS 系統網站伺服器 aoaws.caa.gov.tw 網站，且臺北航

空氣象中心工作人員無法連上網際網路。

當網路斷線情況出現，並且確認為專線問題，請聯絡資訊管理中心-網路設備臺值班人員，

電話號碼：03-3841370。

The TAMC is connected to the internet via an ATSN designated line. If this link goes down, users will be unable to access wmds.aoaws.caa.gov.tw, which is the web server for the AOAWS. Also, personnel at the TAMC will not be able to connect to the internet.

If the link goes down, you should contact the MIS Center 24-hour support with phone number 03-3841370.

4.2.2 臺北航空氣象中心與北部飛航服務園區間之網路連結 (Fiber optic link from TAMC to ATSN))

臺北航空氣象中心與位於北部飛航服務園區的網路中心間網路是藉由區域網路(LAN)連結

，所有系統的資料均透過此一可靠的區域網路連結至中央氣象局 (CWB)、區管中心 (TACC)、桃園國際國際機場 (TIA)，以及高雄國際機場 (KH)。

如果這一段網路斷線，請聯絡資訊管理中心-網路設備臺值班人員，電話號碼：03-3841370。

The network from the TAMC to the network center at ATSN, ATSN uses fiber-optic technology, which is a reliable LAN technology. All the data to CWB, TACC, TIA and KH go over this line.

If this link goes down, you should contact the 24-hour support to check where the problem is with phone number 03-3841370.

4.2.3 北部飛航服務園區與中央氣象局間 FTTB 10M 專線 (FTTB 10M link from ATSN to CWB)

北部飛航服務園區與中央氣象局間網路透過 FTTB 10M 專線連結。WRF 模式資料以及雷

達資料均透過此線路傳送至臺北航空氣象中心。

下列資料來自中央氣象局：

• WRF MDV 檔案

• GTS raw 檔案

• 中央氣象局雷達檔案


• CDF 檔案

• 中央氣象局衛星檔案

• 中央氣象局轉送的空軍氣象資料

雷達資料傳送間隔為每 30 分鐘一次，WRF 資料為每 6 小時。如果 FTTB 10M 線路中斷

，首先受到影響的可能是雷達資料傳送，接著是 WRF 模式資料。

如果這一段 FTTB 10M 線路斷線，請聯絡資訊管理中心-網路設備臺值班人員，電話號碼：

03-3841370。

The ATSN is connected to the CWB via a FTTB 10M line. The WRF model data and radar data flow to the TAMC over this line.

The following data arrives from CWB:

• WRF MDV files

• GTS raw files

• CWB radar files

• CDF files

• CWB-sat files

• CWB caf files Therefore, if the link goes down, these data sets will be affected.

If this link goes down, you should use the 24-hour support with phone number 02-87702189 to contact the MIS Center 24-hour support with phone number 03-3841370.

4.2.4 臺北裝修區臺與松山航空氣象臺間光纖 (Fiber optic link from SSAFS to SS Weather Station)

臺北裝修區臺與松山航空氣象臺間網路是由光纖連結。

如果這一段光纖中斷，資料便無法從臺北航空氣象中心傳送到松山航空氣象臺，SysView無法監視裝置在松山航空氣象臺的 MDS 主機。從 SysView 上看到 sswx-mds1 的圖像均為

紅色。

光纖硬體設備裝置在臺北裝修區臺。

如果這一段光纖斷線，請聯絡臺北莊修區臺值班人員，電話號碼：02-87702189。

臺北裝修區臺有放置一部 MOXA，用以接收松山機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡臺北裝修區臺(電話號碼：02-87702189)值班人員以確認松山

機場 ASOS/AWOS 及 MOXA 的運作狀況。


The network from the SSAFS to the weather station at SS uses fiber-optic technology, which is a reliable LAN technology.

If the link goes down, data will not flow from the TAMC to SSWX, and SysView at the TAMC will not be able to monitor the MDS at SSWX. On SysView all of the icons on the SSWX page will appear in red.

The hardware for the link is located in SSAFS.

If the link goes down, you should contact the 24-hour support to check where the problem is with phone number 02-87702189.

There is one MOXA in SSAFS for ingesting RCSS ASOS/AWOS data from SongShan airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 02-87702189) to check the status of RCSS ASOS/AWOS data and MOXA.

4.2.5 北部飛航服務園區與桃園氣象臺間微波網路 (Microwave link from ATSN to TTYWX)

北部飛航服務園區與桃園氣象臺間網路是藉由微波技術連結。

如果北部飛航服務園區與桃園氣象臺間微波中斷，資料便無法從臺北航空氣象中心傳送至

桃園氣象臺，SysView 無法監視裝置在桃園國際機場所有 MDS 主機。從 SysView 上看到

桃園國際機場所有 MDS 主機的圖像均顯示為紅色。

除此之外，從桃園國際機場傳送至臺北航空氣象中心的雷達資料也是透過微波。若微波網

路斷線，將會影響雷達資料的傳輸。

微波硬體設備裝置在北部飛航服務園區。

如果這一段微波斷線，請聯絡資訊管理中心-設備維護臺值班人員，電話號碼：03-3841370。

桃園氣象臺有放置一部 MOXA，用以接收桃園機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡桃園裝修區臺(電話號碼：03-3982565)值班人員，確認桃園


The network from the ATSN to the TTYWX uses microwave technology.

If the link from the ATSN to TIAWX goes down, data will not flow from the TAMC to TTYWX, and SysView at the TAMC will not be able to monitor any of the MDS hosts at TIA. On SysView all of the icons on all of the TIA hosts will appear in red.

Also, radar data from TIA flows back to the TAMC over this link. If the link is down, TIA radar data will be affected.

The hardware for the link is located in ATSN

If the link goes down, you should contact the 24-hour support to check where the problem is with phone number 03-3841370.


There is one MOXA in TTYWX for ingesting RCTP ASOS/AWOS data from Taoyuan airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 03-3982565) to check the status of RCTP ASOS/AWOS data and MOXA.

4.2.6 桃園國際機場內網路 (Communications links at TIA airport)

桃園國際機場內網路是透過光纖連結–請參考附錄 A 網路架構圖。如果這之間有任何網路

中斷，主機將無法與臺北航空氣象中心連結，SysView 無法監視裝置在桃園國際機場內所

有 MDS 主機。從 SysView 上看到桃園國際機場內所有 MDS 主機的圖像均顯示為紅色。

桃園國際機場內網路傳輸硬體設備裝置在：

桃園航空氣象臺辦公室

桃園航空氣象觀測室。

如果有任何一段網路斷線，請聯絡桃園裝修區臺值班人員(電話號碼：03-3982565)，以確

認問題所在。

At TIA itself, communications between the hosts use a combination of fiber-optic–see Appendix A. If any of the links to any host is down, that host will not be reachable, and SysView at TAMC will not be able to monitor the host. On SysView all of the icons on all of the TIA hosts will appear in red.

The locations of the communications hardware at TIA are:

TIA Weather station office

TIA Weather observation room

If any link goes down, you should contact the TIA 24-hour support to check where the problem is with the phone number 03-3982565.

4.2.7 北部飛航服務園區與高雄氣象臺間 ASN 專線 (Leased line: from ATSN to KHWX)

北部飛航服務園區與高雄氣象臺間網路是透過 ASN 專線相連結。

如果北部飛航服務園區與高雄氣象臺間 ASN 專線中斷，資料便無法從臺北航空氣象中心

傳送至高雄氣象臺，SysView 無法監視裝置在高雄國際機場所有 MDS 主機。從 SysView上看到高雄國際機場所有 MDS 主機的圖像均顯示為紅色。

專線硬體設備裝置在北部飛航服務園區。

如果確定為 ASN 專線斷線，請聯絡資訊管理中心-網路設備臺值班人員，電話號碼：03-3841370。

高雄氣象臺有放置一部 MOXA，用以接收高雄機場的 ASOS/AWOS 資料。


若資料流有任何問題，請聯絡高雄裝修區臺值班人員(電話號碼：07-8057732)，確認高雄


The network from the ATSN to KHWX host uses a leased line.

If the link from the ATSN to KHWX goes down, data will not flow from the TAMC to KHWX, and SysView at the TAMC will not be able to monitor any of the MDS hosts at KH. The icons for all KH hosts will appear in red on SysView.

The hardware for the link is located in ATSN.

If the link goes down, you should contact the 24-hour support with phone number 03-3841370.

There is one MOXA in KHWX for ingesting RCKH ASOS/AWOS data from Kaohsiung airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 07-8057732) to check on the status of RCKH ASOS/AWOS data and MOXA.

.

4.2.8 高雄國際機場內網路 (Communications links at KH international airport)

高雄國際機場內網路是透過光纖連結–請參考附錄 A 網路架構圖。如果這之間有任何網路

中斷，主機將無法與臺北航空氣象中心連結，SysView 無法監視裝置在高雄國際機場所有

MDS 主機。從 SysView 上看到高雄國際機場所有 MDS 主機的圖像均顯示為紅色。

KH 網路傳輸硬體設備裝置在：南部飛航服務園區。

如果有任何一段網路斷線，請聯絡高雄裝修區臺值班人員，電話號碼：07-8057732。

At KH itself, communications between the hosts use a combination of fiber-optic–see Appendix A. If any of the links to any host is down, that host will not be reachable, and SysView at TAMC will not be able to monitor the host. All of the icons on the SysView page for that host will be red.

The location of the communications hardware at KH is at ANWS North ATS Park

If any link goes down, you should contact the 24-hour support to check where the problem is with phone number 07-8057732.

4.2.9 連線到馬祖北竿機場(Communication link to RCMT)

馬祖氣象臺有放置一部 MOXA，用以接收金門機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡馬祖北竿助航臺值班人員(電話號碼：0836-55065)，確認高

雄機場 ASOS/AWOS 及 MOXA 的運作狀況。

There is one MOXA in MTWX for ingesting RCMT ASOS/AWOS data from Matsu Beigan airport.


If there is any problem with the data flow, please contact the 24-hour support (phone number 0836-55065) to check on the status of RCMT ASOS/AWOS data and MOXA.

4.2.10 連線到金門機場(Communication link to RCBS)

金門氣象臺有放置一部 MOXA，用以接收金門機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡金門助航臺值班人員(電話號碼：082-313892)，確認高雄機

場 ASOS/AWOS 及 MOXA 的運作狀況。

There is one MOXA in BSWX for ingesting RCBS ASOS/AWOS data from Kinmen airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 082-313892) to check on the status of RCBS ASOS/AWOS data and MOXA.

4.2.11 連線到蘭嶼機場(Communication link to RCLY)

蘭嶼氣象臺有放置一部 MOXA，用以接收蘭嶼機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡蘭嶼助航臺值班人員(電話號碼：089-732059)，確認蘭嶼機


There is one MOXA in LYWX for ingesting RCLY ASOS/AWOS data from Lanyu airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 089-732059) to check on the status of RCLY ASOS/AWOS data and MOXA.

4.2.12 連線到綠島機場(Communication link to RCGI)

綠島氣象臺有放置一部 MOXA，用以接收綠島機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡綠島助航臺值班人員(電話號碼：089-671503)，確認綠島機


There is one MOXA in GIWX for ingesting RCGI ASOS/AWOS data from Lyudao airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 089-671503) to check on the status of RCGI ASOS/AWOS data and MOXA.

4.2.13 連線到豐年機場(Communication link to RCFN)

豐年氣象臺有放置一部 MOXA，用以接收豐年機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡臺東裝修區臺值班人員(電話號碼：089-362582)，確認豐年



There is one MOXA in FNWX for ingesting RCFN ASOS/AWOS data from Taitung airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 089-362582) to check on the status of RCFN ASOS/AWOS data and MOXA.

4.2.14 連線到七美機場(Communication link to RCCM)

七美機場有放置一部 MOXA，用以接收七美機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡馬公助航臺值班人員(電話號碼：06-9218455)，確認七美機


There is one MOXA in Qimei airport for ingesting RCCM ASOS/AWOS data from Qimei airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 06-9218455) to check on the status of RCCM ASOS/AWOS data and MOXA.

4.2.15 連線到望安機場(Communication link to RCWA)

望安機場有放置一部 MOXA，用以接收望安機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡馬公助航臺值班人員(電話號碼：06-9218455)，確認望安機


There is one MOXA in Wang-An airport for ingesting RCWA ASOS/AWOS data from Wang-An airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 06-9218455) to check on the status of RCWA ASOS/AWOS data and MOXA.

4.2.16 連線到馬祖南竿機場(Communication link to RCFG)

馬祖南竿氣象臺有放置一部 MOXA，用以接收馬祖南竿機場的 ASOS/AWOS 資料。

若資料流有任何問題，請聯絡馬祖南竿助航臺值班人員(電話號碼：0836-26315)，確認馬

祖南竿機場 ASOS/AWOS 及 MOXA 的運作狀況。

There is one MOXA in FGWX for ingesting RCFG ASOS/AWOS data from Matsu/Nagan airport.

If there is any problem with the data flow, please contact the 24-hour support (phone number 0836-26315) to check on the status of RCFG ASOS/AWOS data and MOXA.

4.2.17 臺北航空氣象中心內網路 (Communications problems at TAMC)

在臺北航空氣象中心內區域網路是透過交換器連結。


如果發生網路中斷，資料傳送也會因此中斷，也會在 SysView 上反映出來。

網路硬體設備放置在：臺北航空氣象中心發展測試平臺以及臺北航空氣象中心電腦室。

如果網路中斷，請與資拓宏宇國際股份有限公司工作人員連絡，電話號碼：03-3841466。

Within the TAMC the LAN is managed via network switches.

If a problem with the network occurs, it is likely that much of the AOAWS data flow will be disrupted, and SysView will reflect many problems.

The Locations of the communications hardware are at TAMC AOAWS Lab and TAMC computer room.

If any link goes down, you should contact IISI with phone number 03-3841466.

4.3 資料可用性問題 (Data availability problems)

AOAWS 系統外部資料接收來源：

• 來自 CAF, AFTN 專線的 METARs、TAFs、ACARs、AIREPS 等資料，這些資料

直接連至 data1/2 主機之網路上。

• 來自中央氣象局的資料(參考 4.2.3 小節)：WRF、中央氣象局雷達、GTS 、CDF、中央氣象局衛星檔案及中央氣象局轉送的空軍氣象資料。

• 來自桃園國際機場的雷達資料，透過微波傳送至臺北航空氣象中心。

• 來自日本氣象協會(JWA) FTP 站的 MTSAT 日本衛星資料和歐洲 EUMETSAT 衛星

資料。

• 來自美國航空氣象中心的世界區域預報系統網際網路服務(WIFS)的 WAFS 資料。

• 來自金門、高雄、馬祖北竿、台北松山、桃園、蘭嶼、綠島、豐年、七美、望安及

馬祖南竿等機場之 ASOS/AWOS 資料。這些資料源透過 serial-to-tcp 轉換器由

data1/2 主機接收。資料網路流程如前所述。

在 AOAWS 系統中常見的問題與從外部資料來源相關。

如果某個資料停止傳送至 AOAWS 系統，這表示系統上的某些資料將會延遲。SysView內有關延遲的定義，對每個資料集不同。當資料集為延遲狀態時，SysView 上圖示顏色會

由綠色轉變為黃色。如果資料集為嚴重延遲時，圖示顏色會由黃色轉變為紅色。

SysView 能清楚地顯示系統資料流程。當有狀況產生，只要跟著資料流程圖 (從圖左至右

)便可判別主要問題所在。

系統作業人員也可從 SysView 上得到疑難排解訊息。只要按下資料集圖示，可以看到有

關這個資料集的訊息畫面，在畫面上亦有一個“Troubleshooting”按鈕，只要按下本按鈕，

就會出現有關這個問題的相關疑難排解方式。


The AOAWS receives external data from the following sources:

• CAF and AFTN serial data for METARs, TAFs, ACARs, AIREPS etc. These are connected directly to serial ports on data1/2.

• Data from the CWB (see section 4.2.3): WRF, CWB radar, GTS, CDF, CWB-sat and CWB-caf.

• TIA radar data, which is transmitted to the TAMC over the microwave link.

• GLOBAL Composite, GOES-EAST, GOES-WEST, MTSAT and EUMETSAT satellite data from JWA FTP server.

• WAFS data from the WAFS Internet File Service (WIFS) from the NWS Aviation Weather Center.

• ASOS/AWOS data from RCBS, RCKH, RCMT, RCSS, RCTP, RCLY, RCGI, RCFN, RCCM, RCWA and RCFG. These sources are connected by serial-to-tcp converters and received by data1/2. The data passes through the network topologies described above.

The most frequent problems with the AOAWS are related to the delivery of data from these external sources.

If a certain type of data stops flowing to the AOAWS, this will mean that some of the data on the system will become ‘late’. The exact definition of ‘late’ varies from one data set to another, and is set by SysView. When a data set is late, the SysView icon for that data set will change color from green to yellow. If the data set is ‘very late’, the icon color will change from yellow to red.

SysView graphically shows you the data flow within the system. When a problem occurs, you should follow the data flow up-stream (from right to left on the diagram) to determine the origin of the problem.

You can also obtain troubleshooting information from SysView. If you click on the data set icon you will move to a page which contains the data set information. That page may also have a button marked ‘Troubleshooting’. If so, click on that button and you will move to the troubleshooting page, which will give you the latest available information on how to diagnose and correct the problem. The advantage of this approach, rather than putting all of that information in this document, is that the information can be updated as necessary without making the documentation out of date.

4.3.1 雷達資料 (CWB Radar data)

AOAWS 系統有三種雷達資料是由中央氣象局產生，經傳送到 cwb-caasv1 和 cwb-caasv2後再由 AOAWS 軟體從 cwb-caasv1 和 cwb-caasv2 將資料傳送到臺北航空氣象中心的

tamc-data1 和 tamc-data2.主機。這三種資料包含：

由 4 顆雷達資料合成之二維合成回波資料，

來自 4 顆雷達之三維合成回波資料，


• 來自台南七股(RCCG)、墾丁(RCKT)、花蓮(RCHD)及五分山(RCWF)各自雷達之體

積掃描資料。

如果雷達資料延遲，有可能是下列原因導致：

• 問題來自中央氣象局與臺北航空氣象中心間 FTTB 10M 專線故障。

• 問題來自 tamc-data1 或 tamc-data2 主機。

• 問題來自中央氣象局資料傳輸軟體。

• 問題來自中央氣象局雷達。

如果問題不在臺北航空氣象中心及 tamc-data1 或 tamc-data2 間，另外臺北航空氣象中心

與中央氣象局間網路仍正常，問題可能發生在中央氣象局。在這個情況下，請與中央氣象

局相關人員聯繫。

There are three types radar data created at the CWB, and copied to tamc-data1, tamc-data2 from cwb-caasv1, cwb-caasv2. They are

• 2-D composite data from a four radar mosaic, • 3-D data from a four radar mosaic, • Individual volume data from RCCG, RCKT, RCHD and RCWF.

If the radar data is late, the following are possible causes:

• Problems with the FTTB 10M connection from CWB to TAMC.

• Problems with tamc-data1, tamc-data2.

• Problems with the CWB software.

• Problems with the CWB radars. If the problem cannot be solved at the TAMC or tamc-data1 or tamc-data2, and the TAMC link to CWB is up, the problem is likely to be at CWB. In this case you should contact CWB.

4.3.2 WRF 模式資料 (WRF model data)

WRF 模式在 HPC 上執行，HPC 放置在中央氣象局。資料先傳送到 cwb-modelserver，再

從 cwb-modelserver 穿過 VPP 防火牆到 cwb-caasv1 和 cwb-caasv2，最後再傳送到臺北航空

氣象中心。

如果 WRF 資料延遲，有可能是下列原因導致：

• 問題來自中央氣象局與臺北航空氣象中心間 FTTB 10M 專線故障。

• 問題來自 cwb-modelserver1 或 cwb-modelserver2 主機。

• 問題來自 cwb-caasv1 或 cwb-caasv2 主機。

• 問題來自 WRF 模式。


• 問題來自 HPC。

首先請檢查臺北航空氣象中心與中央氣象局間網路狀況及 cwb-modelserver1、cwb-modelserver2、cwb-caasv1 和 cwb-caasv2 主機狀況。

如果失敗就必須檢查 WRF 模式狀況。可以從網頁上查看 WRF 模式狀態，網址為：


如果 WRF 模式執行發生錯誤，系統將會自動將錯誤訊息顯示在狀態訊息上。

如果仍舊不確定問題自何處發生，請與中央氣象局聯絡。

The WRF model is run on the HPC machine at the CWB. The data is copied from the HPC to the cwb-modelserver1,2 hosts. The AOAWS software on the cwb-modelserver1,2 copies the data across the HPC firewall to cwb-caasv1,2, which then copies it to the TAMC.

If the WRF data is late, the following are possible causes:

• Problems with the FTTB 10M connection from CWB to TAMC.

• Problems with cwb-modelserver1, cwb-modelserver2

• Problems with cwb-caasv1, cwb-caasv2

• Problems with the WRF model.

• Problems with the HPC. First check the connection to the CWB and the status of cwb-modelserver1, cwb-modelserver2, cwb-caasv1, and cwb-caasv2.

If this is not successful, you will need to check on the status of the WRF model. You can check on the status of the WRF model by going to the status web page:


and clicking the “Model Status Summary” link.

If there is a problem with the WRF model, the operators may put that information on the status message.

If you are still unsure of what the problem is, you should contact CWB.

4.3.3 METAR、TAF、AIREP、ACARS 及 AMDAR 資料 (METAR, TAF, AIREP, ACARS and AMDAR data)

這些文字產品來自(a)連結至 tamc-data1 and tamc-data2 主機的 CAF 和 AFTN 專線及(b)來自中央氣象局 FTTB 10M 專線的 GTS 資料。

可能出現的問題有：

• CAF METARs 或 TAFs 資料延遲 – 問題來自 CAF 專線





• 國際間 METARs 或 TAFs 資料延遲 – 問題來自 AFTN 專線或 FTTB 10M 的 GTS資料

• AIREPs 資料延遲 – 問題來自 AFTN 專線

• ACARS 資料延遲 – 問題來自 AFTN 專線

AMDAR 資料延遲 – 問題來自 GTS 專線

如果推測資料延遲接收的問題來自專線，請與臺北航空氣象中心值班人員聯繫，電話號碼

：03-3841465。

The data for these text products is read from (a) the CAF and AFTN serial connections into the tamc-data1 and tamc-data2 hosts and (b) GTS data on the FTTB 10M link from CWB..

The likely problems are as follows:

• CAF METARs or TAFs late – problems with CAF serial connection

• International METARs late – problems with AFTN or GTS data on the FTTB 10M link

• AIREPs late – problems with AFTN

• ACARS late – problems with AFTN

• AMDAR late – Problems with GTS

If you suspect that there are problems with the serial data connections, you should contact the 24-hour support in TAMC with phone number 03-3841465.

4.3.4 衛星資料 (Satellite data)

衛星資料由 tamc-gateway1 與 tamc-gateway2 從 JWA FTP 站下載。

可能出現的問題有：

• tamc-gateway1 或 tamc-gateway2 對外連線有誤。檢查對外連線

• 問題來自 tamc-gateway1 或 tamc-gateway2 主機。視狀況，重新開機

若您無法連線至 JWA FTP 站或無法解決問題，請以 email 與 JWA 連繫。

The satellite data on tamc-gateway1 and tamc-gateway2 are from JWA FTP server.

The likely problems are as follows:

• The network of tamc-gateway1 or tamc-gateway2 can not connect to outside. Check the network.

• Problems on tamc-gateway1 or tamc-gateway2. Reboot as required.


If you cannot connect to JWA FTP server or are not able to solve the problem, you should contact JWA with email .

4.3.5 WAFS 資料 (WAFS data)

主要來源 (Primary source - HTTP)：

WAFS 資料由 tamc-gateway1 與 tamc-gateway2 從美國民航局(NWS) WIFS 伺服器來的。可能出現的問題有：

• tamc-gateway1 或 tamc-gateway2 對外連線有誤。檢查對外連線

• WIFS 伺服器之連線問題

• 伺服器位置為 www.avaitionweather.gov/wifs/data

• 登入之帳號與密碼可至 projDir/wifs_ingest/params/wifs_wget.auth 查詢

• 問題來自 tamc-gateway1 或 tamc-gateway2 主機。視狀況，重新開機

若您無法連線至 NOAA HTTP 站或無法解決問題，請與 NOAA 連繫(連絡電話: +1(877)280-2811，電子郵件：[email protected])。

The WAFS data on tamc-gateway1 and tamc-gateway2 are from NWS WIFS server . The likely problems are as follows:

• The network from tamc-gateway1 or tamc-gateway2 cannot connect to the outside. Check the network.

• Problems connecting to the WIFS server

• The server location is www.avaitionweather.gov/wifs/data

• The login and password can be found in the projDir/wifs_ingest/params/wifs_wget.auth authorization file

• Problems on tamc-gateway1 or tamc-gateway2. Reboot as required. If you cannot connect to NOAA HTTP server or are not able to solve the problem, you should contact NOAA (Phone number +1(877)280-2811, Email: [email protected]).

4.3.6 AWOS data

AWOS 資料是由 tamc-data1 和 tamc-data2 兩台主機透過 TCP/IP 連結接收到 AOAWS 系統

中的，各 AWOS 站相關設備的 IP 及連接 PORT 號碼條列如下表：

The AWOS data is read by the AOAWS through tcp/ip connections on tamc-data1 and tamc-data2. 表一：AWOS 站列表及相關 IP 地址與 PORT 號碼。

Table 1 lists the AWOS site and the associated ip address and port numbers.

http://www.avaition.weather.gov/


Site IP address Port number

RCBS 10.26.72.61 4001

RCKH 10.30.72.20 4001

RCMT 10.23.72.61 13020

RCSS 10.20.72.20 4016

RCTP 10.40.72.20 4001

RCLY 10.52.72.61 5001

RCGI 10.53.72.61 5001

RCFN 10.50.72.61 5001

RCCM 10.33.72.101 4002

RCWA 10.33.72.101 4001

RCFG 10.22.72.61 13020

表一：AWOS 站列表及相關 IP 地址與 PORT 號碼。

Table 1 : List of sites, ip addresses and port numbers.

檢測資料流，請使用”telnet”連線到資料傳輸 PORT. 以松山機場為例：

請於 tamc-data1 主機上執行下列指令：

telnet 10.26.72.61 4001 | od –c

如果成功，螢幕上會顯示一連串的文字數據串，且幾乎每間隔一秒鐘會更新一筆資料。

To test that data is coming in over the ports, use telnet to examine stream form port. Try the following the command line on tamc-data1 to test RCSS:

telnet 10.26.72.61 4001 | od –c

If successful, a stream of lines of text will appear on the display, updating at approximately one-second intervals.


4.4 電力問題 (Power problems)

如果 AOAWS 系統任何一站發生電力中斷，也可能導致其他問題發生。雖然大部分的機

器都已經接上 UPS 不斷電系統，不斷電系統也只能提供短時間電力提供，若電力中斷時

間過長，部分機器可能也會被迫關機。

如果電力中斷，SysView 也無法監看到系統主機，因電力中斷無法監看到的主機將會在圖

示上出現紅色狀態。

恢復供電後，主機通常會自動開始運作。然而有時會需要人為協助來將系統恢復為正常的

作業環境，解決這類因電力中斷後機器無法正常重新啟動的常見狀況，請參考 ’作業系統

問題’ 及 ’電腦硬體問題’章節中對於這類問題的詳細說明。

If power is lost at any of the AOAWS sites, it is possible that some problems will result. Although most of the machines are protected by UPS (Uninterruptible Power Supply) units, these can only handle the load for a limited period and if the power is out for an extended period some of the machines may power down.

If power is lost to part of the system SysView will likely not be able to monitor that part of the system and all the icons for the affected area will be red.

When power is restored, machines will generally come up again automatically. However, sometimes operator intervention is required to restore the system to a fully operational state. The most likely problem to be dealt with after a power failure is that a host will not reboot properly. See the following sections ‘Operating system problems’ and ‘Computer hardware problems’, for details on how to handle this situation.

4.5 作業系統問題 (Operating system problems)

AOAWS 系統所有主機均安裝執行 Linux 版本的 UNIX 作業系統。這是一套健全且穩定的

作業系統，在許多程式發生執行錯誤狀況時，系統不會因此當機。但偶而作業系統仍會有

當機情況。若作業系統發生當機時，系統通常會重新開機。若系統當掉卻無自動重開機，

有可能電腦會維持在當機的狀態，直到管理者將之重新啟動。

All of the computers in the AOAWS run the Linux version of the UNIX operating system (OS). This OS is very robust and reliable, and is capable of handling many types of program error without crashing. Nevertheless, occasionally the OS will hang or crash. If a crash occurs the system will usually reboot cleanly. If the OS hangs without crashing, this is potentially more disruptive because the computer will stay in that state until it is manually rebooted.


4.5.1 電腦重新啟動不完全 (Computer will not reboot properly.)

電力中斷 (如上述) 可能導致機器重新啟動不完全，這是由於檔案系統不正確所導致。在

這樣的情況下，螢幕上會顯示一列訊息： ‘run fsck manually’

在這樣的情況下。加入 –y 參數在上列指令中，作業系統即會進行修補檔案系統。

此指令必須以 root 帳號才能執行。

執行下列指令： fsck –y diskname

diskname 為 ‘run fsck manually’ 錯誤訊息上指出的硬碟分割區。

在 fsck 完成後，按下 Ctrl-D 繼續開機。

如果系統仍舊無法重新開機，或另有其他問題發生，請洽系統維護承包商資拓宏宇公司協

助解決，電話號碼：03-3841466。

Power failures (as mentioned above) can also lead to situations in which a machine does not reboot cleanly because of a corrupted file system, and manual intervention is required. In this case, you will see a message on the console indicating that you will have to:

‘run fsck manually’.

In this case, run fsck with the –y option, so that the operating system will repair the file system.

You will need to be root to do this.

Run the command: fsck –y diskname

where diskname is specified in the ‘run fsck manually’ error message.

After fsck completes, hit Ctrl-D to continue booting.

If the system will still not reboot, or some other problem occurs, you will need to request help from the maintenance contractor. In the case, you should contact IISI with phone number 03-3841466.

4.6 電腦硬體問題 (Computer hardware problems)

硬體會不定時發生故障。常見故障可能為突然間或漸進式的硬碟故障，如果故障突然發生

會導致電腦當機。如果故障是漸進式有可能是硬碟故障，如果懷疑是硬碟故障，可查看記

錄檔： /var/log/syslog

尋找錯誤訊息。


如果懷疑問題來自電腦內硬體，請洽系統維護承包商資拓科技協助解決，電話號碼：03-3841466。

Hardware failures will occur from time to time. The most common failure is a sudden or progressive disk failure. If the failure is sudden, the computer will crash. If the failure is progressive, some errors will probably result. If you suspect a bad disk, you can check the log file:

/var/log/syslog

for errors.

If you suspect the failure of the hardware in a computer, you will need to request help from the maintenance contractor. In the case, you should contact IISI with phone number 03-3841466.

AOAWS Operators Manual 69 Network diagrams

5 疑難排解指南 (Troubleshooting guide)

症狀可能原因參考章節:

無法連上 wmds

WMDS 網頁無法檢

視

• CAA 網際網路連線中斷

• wmds1/2 主機當機

4.2.1

4.5, 4.6

主機上所有圖示在 SysView 為紅色狀態

• 系統沒有啟動 – 啟動系統

• 主機與網路斷線 – 修理網路

• 機器當機 – 修理機器

2.3

4.2

4.5

Data set 在 SysView顯示狀態為紅色

• 資料沒有接收到 – 點選資料集, 點選

'Troubleshooting'連結 , 參考建議

4.3

機器電源供應正常，

但是無法登入主機 • 機器當掉 – 重新開機 4.5

主機顯示不正常的高

負載運作 • 下游電腦關機或無法正常接收檔案。

在~/projDir/logs/distrib/today 檢查 logs 檔案之錯誤

訊息。將下游電腦自主機上的傳輸列表中移除，並重新啟

動 AOAWS 系統。

2.4

SysView 上程序圖示

為紅色 • 程序沒有啟動 – 試著重新啟動 AOAWS 程序。如

果失敗，重新開機。若還是失敗，重新安裝

AOAWS 軟體。

4.5

Symptom Probable cause See Section:

wmds1/2 unreachable

wmds pages not available

• CAA internet connection down

• wmds1/2 down

4.2.1

4.5, 4.6

All SysView entries on a host red • System has not been started - start system

• network to host is down - fix network

• host is down - fix host

2.3

4.2

4.6


Symptom Probable cause See Section:

Data set is red on SysView • Data not arriving - click on data set, click on 'Troubleshooting' link, follow suggestions

4.3

Host has power but you cannot log in • Host is hung - reboot or reset 4.5

Host gives disk errors on startup • File system is corrupted - run fsck. If fsck fails, reinstall system.

4.6

Host has unexpected high loads • Downstream computer is down or unable to receive files. Check log files under ~/projDir/logs/distrib/today for errors. Remove down computer dist host list file. Restart AOAWS.

2.4

Process icon is red on SysView • Process is not registering heartbeat - Attempt to restart process. If this fails, reboot. If that fails, reinstall AOAWS software.

4.5


0 附錄 A:網路架構圖 (Appendix A: Network diagrams)









Documents

The Advanced Operational Aviation Weather Systemaoaws.caa.gov.tw/htdocs/projects/aoaws/doc/pdf/ops_manual.pdf · Replaced BigSister section with one on Opsview. Added SysView images