OpManager ナレッジベース

ManageEngine > サポート > OpManager ナレッジベース > 機能仕様 > OpManager の 起動の正常性を確認したい
戻る

OpManager の 起動の正常性を確認したい

  • 作成日：2014年4月24日 | 更新日：2025年3月13日

概要

OpManager の 起動の正常性を確認したい。

確認方法

[1] OpManagerが正常に起動しているかどうかログを確認します。

確認場所
  • Windows OSのサービスからOpManagerサービスを起動している場合、OpManager\logs\wrapper.logを参照。
  • 以下を実行して起動している場合は、端末画面を参照。
    WindowsOS : OpManager\bin\StartOpManagerServer.bat
    Linux OS : OpManager\bin\StartOpManagerServer.sh

以下の通りOpManagerのプロセスが起動していることを確認します。
起動している場合は「Started」
起動していない場合は「Failed」 と表示されます。

・バージョンによっては、以下の通り表示されるプロセスに含まれていないものや別のプロセスが含まれている場合がございます。
・SNMPトラップのポート162番がすでに別のアプリケーションで使用されている場合には以下のログが出力されます。

INFO   | jvm 1    | 2014/04/23 08:37:10 | WARNING : Traps cannot be received on port : 162※その場合OpManagerでは、SNMPトラップを監視することができませんが、それ以外の監視に影響はございません。

【バージョン12.8以降の場合】

WebService[ STARTED ]

StartupController[ LOADED ]
ModulePreStartProcess :: Persistence::DBAUDIT[ STARTED ]
Persistence[ LOADED ]
ModulePostStartProcess:: Persistence::DBAUDIT[ STARTED ]
Audit[ LOADED ]
Authentication[ LOADED ]
Authorization[ LOADED ]
CustomView[ LOADED ]
TaskEngine[ LOADED ]
ITOMFrameworkService[ LOADED ]
ITOMEnterpriseService[ LOADED ]
ModulePreStartProcess :: OpManager::FreshStartUpdater[ STARTED ]
OpManager[ LOADED ]
ModulePostStartProcess:: OpManager::FreshStartUpdater[ STARTED ]
jca[ LOADED ]
snmp[ LOADED ]
cli[ LOADED ]
tftp[ LOADED ]
topology[ LOADED ]
discovery[ LOADED ]
ncm[ LOADED ]
netflow[ LOADED ]
nba[ LOADED ]
Oputils[ LOADED ]
CustomField[ LOADED ]
LogAnalyzer[ LOADED ]
FirewallAnalyzer[ LOADED ]
TPI[ LOADED ]
adsf[ LOADED ]
RMM[ LOADED ]
Tomcat[ LOADED ]
Creating Services
StartupControllerService[ CREATED ]
CacheService[ CREATED ]
PatchUpdaterService[ CREATED ]
AuthenticationService[ CREATED ]
AuthorizationService[ CREATED ]
TaskEngineService[ CREATED ]
ITOMFrameworkService[ CREATED ]
ITOMEnterpriseService[ CREATED ]
OpManager[ CREATED ]
SnmpService[ CREATED ]
CliService[ CREATED ]
TftpService[ CREATED ]
TftpRAService[ CREATED ]
DiscoveryService[ CREATED ]
SysLogMonitoringService[ CREATED ]
ServerStartupNotify[ CREATED ]
NCM SSHD[ CREATED ]
NetFlowAnalyzer[ CREATED ]
OpUtilsService[ CREATED ]
DService[ CREATED ]
DataManagement[ CREATED ]
TPIService[ CREATED ]
ADSFService[ CREATED ]
ADSService[ CREATED ]
WebService[ CREATED ]
Starting Services
StartupControllerService[ STARTED ]
CacheService[ STARTED ]
PatchUpdaterService[ STARTED ]
AuthenticationService[ STARTED ]
AuthorizationService[ STARTED ]
TaskEngineService[ STARTED ]
ITOMFrameworkService[ STARTED ]
ITOMEnterpriseService[ STARTED ]
OpManager[ STARTED ]
SnmpService[ STARTED ]
CliService[ STARTED ]
TftpService[ STARTED ]
TftpRAService[ STARTED ]
DiscoveryService[ STARTED ]
SysLogMonitoringService[ STARTED ]
ServerStartupNotify[ STARTED ]
NCM SSHD[ STARTED ]
NetFlowAnalyzer[ STARTED ]
OpUtilsService[ STARTED ]
DService[ STARTED ]
DataManagement[ STARTED ]
TPIService[ STARTED ]
ADSFService[ STARTED ]
ADSService[ STARTED ]

Server started in :: [54076 ms]

Connect to: [ https://dnms:443 ]

---------------------------------------------------------------

【バージョン12.7以前の場合】

Persistence[ LOADED ]
SQNS[ LOADED ]
Audit[ LOADED ]
Authentication[ LOADED ]
Authorization[ LOADED ]
CustomView[ LOADED ]
TaskEngine[ LOADED ]
OpManager[ LOADED ]
WorkEngine[ LOADED ]
ClientFramework[ LOADED ]
ClientComponents[ LOADED ]
jca[ LOADED ]
snmp[ LOADED ]
cli[ LOADED ]
tftp[ LOADED ]
topology[ LOADED ]
discovery[ LOADED ]
ncm[ LOADED ]
netflow[ LOADED ]
nba[ LOADED ]
Oputils[ LOADED ]
CustomField[ LOADED ]
LogAnalyzer[ LOADED ]
FirewallAnalyzer[ LOADED ]
fwasshd[ LOADED ]
Tomcat[ LOADED ]
Creating Services
CacheService[ CREATED ]
AuthenticationService[ CREATED ]
AuthorizationService[ CREATED ]
TaskEngineService[ CREATED ]
OpManagerService[ CREATED ]
WorkEngineService[ CREATED ]
ClientFrameworkService[ CREATED ]
TemplateTablePopulator[ CREATED ]
TplTablePopulator[ CREATED ]
SnmpService[ CREATED ]
CliService[ CREATED ]
TftpRAService[ CREATED ]
TftpService[ CREATED ]
MafService[ CREATED ]
StatusPropagationService[ CREATED ]
DiscoveryService[ CREATED ]
NCMSSHDService[ CREATED ]
SysLogMonitoringService[ CREATED ]
ServerStartupNotify[ CREATED ]
NetFlowService[ CREATED ]
OpUtilsService[ CREATED ]
DService[ CREATED ]
DataManagement[ CREATED ]
LeaService[ CREATED ]
FWASSHDService[ CREATED ]
WebService[ CREATED ]
Starting Services
CacheService[ STARTED ]
AuthenticationService[ STARTED ]
AuthorizationService[ STARTED ]
TaskEngineService[ STARTED ]
OpManagerService[ STARTED ]
WorkEngineService[ STARTED ]
ClientFrameworkService[ STARTED ]
TemplateTablePopulator[ STARTED ]
TplTablePopulator[ STARTED ]
SnmpService[ STARTED ]
CliService[ STARTED ]
TftpRAService[ STARTED ]
TftpService[ STARTED ]
MafService[ STARTED ]
StatusPropagationService[ STARTED ]
DiscoveryService[ STARTED ]
NCMSSHDService[ STARTED ]
SysLogMonitoringService[ STARTED ]
ServerStartupNotify[ STARTED ]
NetFlowService[ STARTED ]
OpUtilsService[ STARTED ]
DService[ STARTED ]
DataManagement[ STARTED ]
LeaService[ STARTED ]
FWASSHDService[ STARTED ]
WebService[ STARTED ]

Server started in :: [101544 ms]

Connect to: [ http://localhost:80 ]

---------------------------------------------------------------

【バージョン11以前の場合】

CmdbandChangesProcess[Started]
OpManagerStatusProcess[Started]
AuthMgr[Started]
NetFlowProcess[Started]
DataMgmtRPI[Started]
NCMProcess[Started]
NmsPolicyMgr[Started]
DataCollectionRate[Started]
AppManagerProcess[Started]
NmsAuthManager[Started]
UserConfigProcess[Started]
DBServer[Started]
NmsAuthenticationManager[Started]
CLIFactoryBinder[Started]
MapServerBE[Started]
OpUtilsProcess[Started]
BenchMarkdata[Started]
RunJSPModule[Started]
LocaleDBModification[Started]
EventMgr[Started]
StartTelnetClient[Started]
Collector[Started]
OpManagerProcess[Started]
EventFE[Started]
AlertFE[Started]
MapFE[Started]
NmsMaE[Started]
TopoFE[Started]

Verifyingconnectionwithwebserver...verified

OpManagerサーバを起動しました。

Please connect your client to the web server on port: 80 as http://localhost:80

[2] OpManager正常起動時に動作するプロセス。

Windows の場合
java.exe, wrapper.exe, postgres.exe プロセス
タスクマネージャーにて確認可能

Linux の場合
java, postgres プロセス
ps コマンドにて確認可能

[3] ウェブクライアントにアクセス。

上記[1], [2]を確認しても問題がない場合、
実際に、OpManagerサーバーよりウェブクライアント(上記の例の場合、http://localhost:8060)にアクセスし、OpManagerにログインできるかどうかを確認します。

【対応リリース】x.x

このナレッジの総閲覧回数：7.0K

関連ナレッジ:

  1. Professional Editionの環境をEnterprise Editionのプローブサーバーに移行する方法
  2. OpManagerのアラートをChatworkの通知で受け取る
  3. OpManagerのアラートをLINE WORKSの通知で受け取る
  4. ライセンス有効期限に関する通知の仕様
  5. SSH認証情報を使用して監視しているLinux装置で「kex_exchange_identification：Connection closed by remote host」エラーが発生する