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 的大量远程服务器 
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。

原因部分的原始表内容 
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)         

运行 delete 命令以删除除 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，以便我们可以识别 servlet 何时重新启动，并以 root 用户身份获取该问题的最新日志 
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
从其他戴尔用户那里查找问题的答案
支持服务
检查您的设备是否在支持服务涵盖的范围内。