Avamar: 호스트 이름 구성 문제로 인해 MCS를 시작할 수 없습니다.

Summary: 이 문서에서는 Avamar의 기존 호스트 이름 구성 문제를 해결하여 MCS(Management Console Server)를 시작하는 방법을 보여줍니다.

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(Management Console Server) 서비스를 시작하려고 하면 다음 오류가 발생합니다.

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: Management Console Server를 재시작하는 방법

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.