Avamar：由於主機名稱組態問題，無法啟動 MCS

Summary: 本文說明如何解決 Avamar 上現有的主機名稱組態問題，以啟動管理主控台伺服器 （MCS）。

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

嘗試啟動管理主控台伺服器 （MCS） 服務會導致下列錯誤：

admin@<incorrect-hostname>: mcserver.sh --start
Starting the database server.
Waiting for postmaster to start ..Started
Start MCDB: processing time = 2 s.
Check MCS: processing time = 8 s.
INFO: Starting messaging service.
INFO: Started messaging service.
Start Message Broker: processing time = 12 s.
=== BEGIN === check.mcs (prestart)
ERROR: check.mcs: [<incorrect-hostname>] checking if entry for <incorrect-hostname> is correctly defined in /etc/hosts CHECK FAILED: <incorrect-hostname> entry in /etc/hosts not found or incorrect
check.mcs                        failed
*** FAIL *** check.mcs FAILED OVERALL (prestart)
Starting Administrator Server at Fri May 26 04:54:25 JST 2023 ...
Upgrade MCS Preference: processing time = 286ms
Upgrade MCDB: processing time = 1634ms
Check node list: processing time = 1064ms
Prepare MC SSL Properties: processing time = 1ms
java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Name or service not known
        at java.net.InetAddress.getLocalHost(Unknown Source)
        at com.avamar.asn.Node.setPrefs(Node.java:345)
        at com.avamar.asn.Node.init(Node.java:209)
        at com.avamar.asn.Node.<init>(Node.java:89)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:110)
        at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1097)
        at com.avamar.mc.util.MCSpringUtil.getBean(MCSpringUtil.java:96)
        at com.avamar.mc.CLI.start(CLI.java:355)
        at com.avamar.mc.CLI.process(CLI.java:133)
        at com.avamar.mc.CLI.main(CLI.java:104)
Caused by: java.net.UnknownHostException: <incorrect-hostname>: Name or service not known
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
        at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
        ... 24 more
java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Temporary failure in name resolution
        at java.net.InetAddress.getLocalHost(Unknown Source)
        at com.avamar.asn.Node.setPrefs(Node.java:345)
        at com.avamar.asn.Node.init(Node.java:209)
        at com.avamar.asn.Node.<init>(Node.java:89)
        at com.avamar.mc.CLI.start(CLI.java:357)
        at com.avamar.mc.CLI.process(CLI.java:133)
        at com.avamar.mc.CLI.main(CLI.java:104)
Caused by: java.net.UnknownHostException: <incorrect-hostname>: Temporary failure in name resolution
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
        at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
        ... 7 more
Administrator Server startup failed at Fri May 26 04:54:36 JST 2023: Closing all connections to database. Node initialization failed.
Starting REST API Service.....
REST API Service startup failed.
Start MC Rest: processing time = 11 s.
=== Start Avamar Certificate Service ===
Avamar Certificate Service started.

Cause

根據上述輸出，故障發生在名稱解析中，導致未知主機例外：

java.net.UnknownHostException: <incorrect-hostname>: <incorrect-hostname>: Name or service not known
 

當 Java 程式碼嘗試取得本機主機名稱資訊時，會因主機名稱組態問題而失敗：

範例：

hostname
<incorrect-hostname>
  
hostname -f 
hostname: Temporary failure in name resolution
  
hostname -i
hostname: Name or service not known

Resolution

1.執行下列命令以更新主機名稱：

hostname <correct-hostname>
 

例如：若要將主機名稱設定為 avamar-prod-fs1：

hostname avamar-prod-fs1
 

2.確認主機名稱值 （使用相同的範例）

hostname
avamar-prod-fs1
  
hostname -f 
avamar-prod-fs1.company.com
  
hostname -i
10.1.2.3
 

3.啟動 MCS 並繼續備份排程器：

mcserver.sh --start
dpnctl start sched
 

如需有關啟動 MCS 的詳細資訊，請參閱下列文章：Avamar：如何重新啟動管理主控台伺服器

Affected Products

Avamar
Article Properties
Article Number: 000214258
Article Type: Solution
Last Modified: 12 Dec 2025
Version:  8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.