Avamar:Avamar Client Manager (/aam) 登入時載入網頁當機
摘要: Avamar:Avamar Client Manager (/aam) 載入網頁在登入時當機。登入可能永遠無法完成,或需要數十分鐘才能完成。
本文章適用於
本文章不適用於
本文無關於任何特定產品。
本文未識別所有產品版本。
症狀
Avamar:Avamar Client Manager (/aam) 載入網頁在登入時當機。
登入可能永遠無法完成,或需要數十分鐘才能完成。
頁面可能不會逾時,但會讓您等待很長的時間。
登入可能永遠無法完成,或需要數十分鐘才能完成。
頁面可能不會逾時,但會讓您等待很長的時間。
原因
此問題的原因可能分為兩種:
1.大量遠端伺服器新增至單一 Avamar Client Manager,導致 Tomcat Webserver 的負載增加。
我們可以在 tomcat 資料庫axion_server表中看到將大量遠端伺服器新增至此 Avamar
2.若為有 MCUser 密碼問題的
遠端伺服器,從上方表格輸出,Avamar Server AVAMAR300.EX.COM 發生 MCUser 密碼問題。
在 AVAMAR300.EX.COM 上,MCS 服務正在執行,而 MCUser 的登入測試在 GUI 和命令列中通過良好。
例子:
我們可以看到,雖然看起來沒問題,但 AVAMAR300.EX.COM mcserver.out 記錄的遠端伺服器上,MCUser 密碼仍有明顯問題。
1.大量遠端伺服器新增至單一 Avamar Client Manager,導致 Tomcat Webserver 的負載增加。
我們可以在 tomcat 資料庫axion_server表中看到將大量遠端伺服器新增至此 Avamar
psql -p 5556 emdb select id, lastcontact, axionsystemname from axion_server; id | lastcontact | axionsystemname ---------------+---------------------+------------------------------ 1629287858128 | 1969-12-31 19:00:00 | AVAMAR10.EX.COM 1629287980100 | 1969-12-31 19:00:00 | AVAMAR20.EX.COM 1629287647775 | 1969-12-31 19:00:00 | AVAMAR30.EX.COM 1629287949115 | 1969-12-31 19:00:00 | AVAMAR19.EX.COM 1660563561277 | 1969-12-31 19:00:00 | AVAMAR40.EX.COM 1629287597140 | 1969-12-31 19:00:00 | AVAMAR50.EX.COM 1629287775889 | 1969-12-31 19:00:00 | AVAMAR60.EX.COM 1629287812033 | 1969-12-31 19:00:00 | AVAMAR70.EX.COM 1629288006387 | 1969-12-31 19:00:00 | AVAMAR80.EX.COM 1629287515457 | 1969-12-31 19:00:00 | AVAMAR90.EX.COM 1 | 1969-12-31 19:00:00 | AVAMAR100.EX.COM 1629287732083 | 1969-12-31 19:00:00 | AVAMAR200.EX.COM 1629288102775 | 1969-12-31 19:00:00 | AVAMAR300.EX.COM 1662042283060 | 1969-12-31 19:00:00 | AVAMAR400.EX.COM 1651676768316 | 1969-12-31 19:00:00 | AVAMAR500.EX.COM (15 rows)
2.若為有 MCUser 密碼問題的
遠端伺服器,從上方表格輸出,Avamar Server AVAMAR300.EX.COM 發生 MCUser 密碼問題。
在 AVAMAR300.EX.COM 上,MCS 服務正在執行,而 MCUser 的登入測試在 GUI 和命令列中通過良好。
例子:
avmgr logn --id=MCUser --ap=MyMCUserPass 1 Request succeeded 7161 privilege level (enabled,create,read,backup,access,move,delete,maint,fullmanage,noticketrequired) 2 block type (directory)
我們可以看到,雖然看起來沒問題,但 AVAMAR300.EX.COM mcserver.out 記錄的遠端伺服器上,MCUser 密碼仍有明顯問題。
vi /usr/local/avamar/var/mc/server_data/prefs/mcserver.out === BEGIN === check.mcs (prestart) check.mcs passed === PASS === check.mcs PASSED OVERALL (prestart) Starting Administrator Server at Tue Aug 30 15:04:25 EDT 2022 ... Upgrade MCS Preference: processing time = 325ms Upgrade MCDB: processing time = 262ms Check node list: processing time = 1527ms Prepare MC SSL Properties: processing time = 2ms Init node: processing time = 420ms Install service: com.avamar.mc.prefs.MCSPreferencesService, processing time = 12ms Install service: com.avamar.mc.message.MessageEventService, processing time = 15ms Event Size: 18548 Install service: com.avamar.mc.event.EventService, processing time = 11388ms Install service: com.avamar.mc.jms.push.JmsPushService, processing time = 40ms Install service: com.avamar.mc.dpn.DPNProxyService, processing time = 2031ms Install service: com.avamar.mc.datatap.MCDataTapService, processing time = 22ms Install service: com.avamar.mc.cm.ClusterManagerService, processing time = 12ms [output shortened...] Install service: com.avamar.mc.ws.MCJettyService, processing time = 1272ms Install service: com.avamar.mc.repl.ReplicationService, processing time = 85ms Install service: com.avamar.mc.st.SessionTicketService, processing time = 1434ms Install service: com.avamar.mc.ras.McEbmsService, processing time = 2051ms Install service: com.avamar.mc.migration.MigrationService, processing time = 60ms Start service container: processing time = 51304ms log4j:WARN No appenders could be found for logger (org.apache.axiom.util.stax.dialect.StAXDialectDetector). log4j:WARN Please initialize the log4j system properly. Init crontab: processing time = 3800ms Update axion system table: processing time = 3ms Update connect emc email subject: processing time = 70ms Administrator Server started at Tue Aug 30 15:05:26 EDT 2022. Update connect emc email subject: processing time = 70ms Administrator Server started at Tue Aug 30 15:05:26 EDT 2022. MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP ERROR: Invalid AES key length MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP MCS Preference has been decrypted failed: com/avamar/mc/dpn/users/MCUSERAP
解析度
步驟
1.移除來源伺服器 以外的所有 axion 伺服器 (您要新增其他伺服器的伺服器)。您不會碰觸之來源伺服器的 ID 欄有一個 ID = 1。
原因區段的原始表格內容
5.再次登入 Client Manager (/aam) 網頁,並嘗試透過主機名稱/MCUser 認證再次新增遠端伺服器。在此範例中,我們嘗試新增傳回錯誤的 AVAMAR300.EX.COM。在 Tomcat 伺服器重新開機後,我們可以在 ACMTrace.log 中看到下列記錄,以嘗試新增AVAMAR300。EX.COM。
6.現在我們知道 AVAMAR300.EX.COM 上的 MCUser 認證發生問題,請參閱「原因 #2」一節以取得詳細資訊。如前所述,MCUser 無法解密,因此當來源 Avamar 嘗試使用其 MCUser 認證註冊遠端 Avamar 時,會失敗。
我們必須以 root 使用者身分執行 change-passwords,以在AVAMAR300上 udpate MCUser。EX.COM。
您不需要從目前的密碼變更密碼,可在指令檔中輸入相同的密碼,但必須執行指令檔,才能在所有已套用正確加密/解密金鑰的組態檔案中更新密碼。
7.在遠端伺服器上更新 MCUser 密碼後,請重新整理來源伺服器 Client Manager (/aam) 網頁 (AVAMAR100.EX.COM)。然後嘗試將 AVAMAR300.EX.COM 重新新增到來源伺服器。
1.移除來源伺服器 以外的所有 axion 伺服器 (您要新增其他伺服器的伺服器)。您不會碰觸之來源伺服器的 ID 欄有一個 ID = 1。
原因區段的原始表格內容
psql -p 5556 emdb select id, lastcontact, axionsystemname from axion_server; id | lastcontact | axionsystemname ---------------+---------------------+------------------------------ 1629287858128 | 1969-12-31 19:00:00 | AVAMAR10.EX.COM 1629287980100 | 1969-12-31 19:00:00 | AVAMAR20.EX.COM 1629287647775 | 1969-12-31 19:00:00 | AVAMAR30.EX.COM 1629287949115 | 1969-12-31 19:00:00 | AVAMAR19.EX.COM 1660563561277 | 1969-12-31 19:00:00 | AVAMAR40.EX.COM 1629287597140 | 1969-12-31 19:00:00 | AVAMAR50.EX.COM 1629287775889 | 1969-12-31 19:00:00 | AVAMAR60.EX.COM 1629287812033 | 1969-12-31 19:00:00 | AVAMAR70.EX.COM 1629288006387 | 1969-12-31 19:00:00 | AVAMAR80.EX.COM 1629287515457 | 1969-12-31 19:00:00 | AVAMAR90.EX.COM 1 | 1969-12-31 19:00:00 | AVAMAR100.EX.COM 1629287732083 | 1969-12-31 19:00:00 | AVAMAR200.EX.COM 1629288102775 | 1969-12-31 19:00:00 | AVAMAR300.EX.COM 1662042283060 | 1969-12-31 19:00:00 | AVAMAR400.EX.COM 1651676768316 | 1969-12-31 19:00:00 | AVAMAR500.EX.COM (15 rows)
執行刪除命令,刪除除 id=1 伺服器以外的每個伺服器 (AVAMAR100.EX.COM)
// connect to emdb psql -p 5556 emdb // delete each server besides source server delete from axion_server where id!='1';
2.確認其他遠端伺服器已全部刪除。
select id, lastcontact, axionsystemname from axion_server; id | lastcontact | axionsystemname ---------------+---------------------+------------------------------ 1 | 1969-12-31 19:00:00 | AVAMAR100.EX.COM
3.使用 postgresql 語法結束 emdb。
\q
4.重新開機 tomcat,以便我們能夠識別伺服器何時重新開機,並取得問題的最新記錄,作為根使用者
emwebapp.sh --restart
5.再次登入 Client Manager (/aam) 網頁,並嘗試透過主機名稱/MCUser 認證再次新增遠端伺服器。在此範例中,我們嘗試新增傳回錯誤的 AVAMAR300.EX.COM。在 Tomcat 伺服器重新開機後,我們可以在 ACMTrace.log 中看到下列記錄,以嘗試新增AVAMAR300。EX.COM。
vi /usr/local/avamar-tomcat/logs/ACMTrace.log
// latest logs post tomcat restart start with "Servlet Context Launched."
2022-09-21 16:03:57,802 INFO [localhost-startStop-1]-listeners.ContextLauncher: Servlet Context Launched.
2022-09-21 16:04:00,623 INFO [localhost-startStop-1]-sdk.ServiceConnection: Wait for task: STORAGE_INFO: Getting storage information
2022-09-21 16:04:01,625 INFO [localhost-startStop-1]-sdk.ServiceConnection: Task done: STORAGE_INFO
2022-09-21 16:04:01,660 INFO [localhost-startStop-1]-utils.ACMProperties: Cas Server Url Ssl Prefix: https://AVAMAR300.EX.COM
2022-09-21 16:04:06,669 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-filters.ImageLocaleFilter: Locale in China: false
2022-09-21 16:04:07,926 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-8]-filters.ImageLocaleFilter: Locale in China: false
2022-09-21 16:04:10,172 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:10,176 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:10,178 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:10,179 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:10,180 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-auth.AvamarAuthConfigurationUserAuth: Authentication Type: Web Restore Avamar
2022-09-21 16:04:11,037 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: MCCLI exec catch Execption: Unable to initialize MCCLI
2022-09-21 16:04:11,043 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: authenticate result out: 0,23000,CLI command completed successfully.
2022-09-21 16:04:11,310 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: MCCLI exec catch Execption: Unable to initialize MCCLI
2022-09-21 16:04:11,312 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: get privilege command output: <CLIOutput>
<Results>
<ReturnCode>0</ReturnCode>
<EventCode>23000</EventCode>
<EventSummary>CLI command completed successfully.</EventSummary>
</Results>
<Data>
<Row>
<Name>erx1mxe</Name>
<Role>Administrator</Role>
<Domain>/</Domain>
<Authenticator>Axion Authentication System</Authenticator>
<Domain>/</Domain>
<Authenticator>Axion Authentication System</Authenticator>
</Row>
</Data>
</CLIOutput>
2022-09-21 16:04:11,692 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-2]-sdk.ServiceConnection: Wait for task: STORAGE_INFO: Getting storage information
2022-09-21 16:04:12,693 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-2]-sdk.ServiceConnection: Task done: STORAGE_INFO
2022-09-21 16:04:32,272 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:32,273 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:32,273 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:32,273 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-helper.LDAPManagerUserAuth: LDAP property 'ldap.url.*' is not defined
2022-09-21 16:04:32,274 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-auth.AvamarAuthConfigurationUserAuth: Authentication Type: Web Restore Avamar
2022-09-21 16:04:32,528 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: MCCLI exec catch Execption: Unable to initialize MCCLI
2022-09-21 16:04:32,529 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: authenticate result out: 0,23000,CLI command completed successfully.
2022-09-21 16:04:32,791 WARN [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: MCCLI exec catch Execption: Unable to initialize MCCLI
2022-09-21 16:04:32,792 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-1]-cli.MCInternalCLIUserAuth: get privilege command output: <CLIOutput>
<Results>
<ReturnCode>0</ReturnCode>
<EventCode>23000</EventCode>
<EventSummary>CLI command completed successfully.</EventSummary>
</Results>
<Data>
<Row>
<Name>root</Name>
<Role>Administrator</Role>
<Domain>/</Domain>
<Authenticator>Axion Authentication System</Authenticator>
</Row>
</Data>
</CLIOutput>
2022-09-21 16:04:33,073 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-2]-sdk.ServiceConnection: Wait for task: STORAGE_INFO: Getting storage information
2022-09-21 16:04:34,074 INFO [ajp-nio-0:0:0:0:0:0:0:1-8509-exec-2]-sdk.ServiceConnection: Task done: STORAGE_INFO
6.現在我們知道 AVAMAR300.EX.COM 上的 MCUser 認證發生問題,請參閱「原因 #2」一節以取得詳細資訊。如前所述,MCUser 無法解密,因此當來源 Avamar 嘗試使用其 MCUser 認證註冊遠端 Avamar 時,會失敗。
我們必須以 root 使用者身分執行 change-passwords,以在AVAMAR300上 udpate MCUser。EX.COM。
您不需要從目前的密碼變更密碼,可在指令檔中輸入相同的密碼,但必須執行指令檔,才能在所有已套用正確加密/解密金鑰的組態檔案中更新密碼。
change-passwords
7.在遠端伺服器上更新 MCUser 密碼後,請重新整理來源伺服器 Client Manager (/aam) 網頁 (AVAMAR100.EX.COM)。然後嘗試將 AVAMAR300.EX.COM 重新新增到來源伺服器。
受影響的產品
Avamar文章屬性
文章編號: 000203605
文章類型: Solution
上次修改時間: 08 1月 2026
版本: 9
向其他 Dell 使用者尋求您問題的答案
支援服務
檢查您的裝置是否在支援服務的涵蓋範圍內。